Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
16 lines
447 B
Plaintext
16 lines
447 B
Plaintext
perf supports a simple JIT interface to resolve symbols for dynamic code generated
|
|
by a JIT.
|
|
|
|
The JIT has to write a /tmp/perf-%d.map (%d = pid of process) file
|
|
|
|
This is a text file.
|
|
|
|
Each line has the following format, fields separated with spaces:
|
|
|
|
START SIZE symbolname
|
|
|
|
START and SIZE are hex numbers without 0x.
|
|
symbolname is the rest of the line, so it could contain special characters.
|
|
|
|
The ownership of the file has to match the process.
|