This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/12147] New: Automagically include kernel data when needed through pragma:kernel_data
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: Thu, 21 Oct 2010 12:44:37 +0000
- Subject: [Bug translator/12147] New: Automagically include kernel data when needed through pragma:kernel_data
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12147
Summary: Automagically include kernel data when needed through
pragma:kernel_data
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap@sources.redhat.com
ReportedBy: mjw@redhat.com
There should be a new embedded C pragma:kernel_data or something similar so
that functions like modname(), symname() and symdata() can indicate they need
access to it.
It could work similar to pragma:vma which slurps in the vdso data for example.
See usage of /* pragma:vma */ usage in tapset/ucontext.stp, detection in
elaborate.cc visit_embeddedcode () and usage of that information through
enable_vma_tracker () and emit_symbol_data () in translate.cxx.
This would make scripts that use symbol data translation functions work out of
the box without needing to know whether other probes (through kprobes) slurp in
the kernel data already or not.
Simplest testcase: stap -e 'probe begin { log(symdata(0xffffffff81d90ca0)) }'
(which currently doesn't work unless -d kernel is explicitly given)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.