On Mon, 3 Jun 2019 20:52:38 +0900
Masami Hiramatsu wrote:
> Hi Anders,
>
> Sorry for replying later.
>
> On Tue, 28 May 2019 15:39:15 +0200
> Anders Roxell wrote:
>
> > On Tue, 28 May 2019 at 14:36, Steven Rostedt wrote:
> > >
> > > On Tue, 28 May 2019 14:23:43 +0200
> > > Anders Roxell wro
Hi Anders,
Sorry for replying later.
On Tue, 28 May 2019 15:39:15 +0200
Anders Roxell wrote:
> On Tue, 28 May 2019 at 14:36, Steven Rostedt wrote:
> >
> > On Tue, 28 May 2019 14:23:43 +0200
> > Anders Roxell wrote:
> >
> > > On Wed, 22 May 2019 at 10:32, Masami Hiramatsu
> > > wrote:
> > >
On Tue, 28 May 2019 at 14:36, Steven Rostedt wrote:
>
> On Tue, 28 May 2019 14:23:43 +0200
> Anders Roxell wrote:
>
> > On Wed, 22 May 2019 at 10:32, Masami Hiramatsu wrote:
> > >
> > > Add kprobe_event= boot parameter to define kprobe events
> > > at boot time.
> > > The definition syntax is si
On Tue, 28 May 2019 14:23:43 +0200
Anders Roxell wrote:
> On Wed, 22 May 2019 at 10:32, Masami Hiramatsu wrote:
> >
> > Add kprobe_event= boot parameter to define kprobe events
> > at boot time.
> > The definition syntax is similar to tracefs/kprobe_events
> > interface, but use ',' and ';' inst
On Wed, 22 May 2019 at 10:32, Masami Hiramatsu wrote:
>
> Add kprobe_event= boot parameter to define kprobe events
> at boot time.
> The definition syntax is similar to tracefs/kprobe_events
> interface, but use ',' and ';' instead of ' ' and '\n'
> respectively. e.g.
>
> kprobe_event=p,vfs_read
Add kprobe_event= boot parameter to define kprobe events
at boot time.
The definition syntax is similar to tracefs/kprobe_events
interface, but use ',' and ';' instead of ' ' and '\n'
respectively. e.g.
kprobe_event=p,vfs_read,$arg1,$arg2
This puts a probe on vfs_read with argument1 and 2, and
