On Wed, 8 May 2019 11:22:37 -0400
Steven Rostedt wrote:
> > > > Per-Probe Event Filtering
> > > > -
> > > > diff --git a/Documentation/trace/uprobetracer.rst
> > > > b/Documentation/trace/uprobetracer.rst
> > > > index 4346e23e3ae7..de8812c932bc 100644
> > > > ---
On Wed, 8 May 2019 13:11:43 +0900
Masami Hiramatsu wrote:
> On Mon, 6 May 2019 11:52:26 -0400
> Steven Rostedt wrote:
>
> > On Mon, 18 Mar 2019 15:43:52 +0900
> > Masami Hiramatsu wrote:
> >
> > > +.. _user_mem_access:
> > > +User Memory Access
> > > +--
> > > +Kprobe
On Mon, 6 May 2019 11:52:26 -0400
Steven Rostedt wrote:
> On Mon, 18 Mar 2019 15:43:52 +0900
> Masami Hiramatsu wrote:
>
> > +.. _user_mem_access:
> > +User Memory Access
> > +--
> > +Kprobe events supports user-space memory access. For that purpose, you can
> > use
> >
On Mon, 18 Mar 2019 15:43:52 +0900
Masami Hiramatsu wrote:
> +.. _user_mem_access:
> +User Memory Access
> +--
> +Kprobe events supports user-space memory access. For that purpose, you can
> use
> +either user-space dereference syntax or 'ustring' type.
> +
> +The user-space
Support user-space dereference syntax for probe event arguments
to dereference the data-structure or array in user-space.
The syntax is just adding 'u' before an offset value.
+|-u()
e.g. +u8(%ax), +u0(+0(%si))
For example, if you probe do_sched_setscheduler(pid, policy,
param) and record
5 matches
Mail list logo