search for: eigler

Hi - > > Does this new blacklist cover enough that the kernel now survives a > > broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms? > > That's generally the purpose of the annotations - if it doesn't then > that's a bug. AFAIK, no kernel since kprobes was introduced has ever stood up to that test. perf probe lacks the wildcarding powers of

Hi - > > Does this new blacklist cover enough that the kernel now survives a > > broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms? > > That's generally the purpose of the annotations - if it doesn't then > that's a bug. AFAIK, no kernel since kprobes was introduced has ever stood up to that test. perf probe lacks the wildcarding powers of

* Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > (2013/11/21 2:36), Frank Ch. Eigler wrote: [ ... ] > > one needs to resort to something like: > > > > # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > > perf probe $symbol > > done > > > > then wait for a few hours for that to finish. Then, or while the l...

* Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > (2013/11/21 2:36), Frank Ch. Eigler wrote: [ ... ] > > one needs to resort to something like: > > > > # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > > perf probe $symbol > > done > > > > then wait for a few hours for that to finish. Then, or while the l...

(2013/11/22 11:35), Masami Hiramatsu wrote: > (2013/11/21 16:29), Ingo Molnar wrote: >> >> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: >> >>> (2013/11/21 2:36), Frank Ch. Eigler wrote: >> >> [ ... ] >>>> one needs to resort to something like: >>>> >>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do >>>> perf probe $symbol >>>> done >>>> >>>> th...

(2013/11/22 11:35), Masami Hiramatsu wrote: > (2013/11/21 16:29), Ingo Molnar wrote: >> >> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: >> >>> (2013/11/21 2:36), Frank Ch. Eigler wrote: >> >> [ ... ] >>>> one needs to resort to something like: >>>> >>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do >>>> perf probe $symbol >>>> done >>>> >>>> th...

...chi.com> wrote: > >> (2013/11/22 11:35), Masami Hiramatsu wrote: >>> (2013/11/21 16:29), Ingo Molnar wrote: >>>> >>>> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: >>>> >>>>> (2013/11/21 2:36), Frank Ch. Eigler wrote: >>>> >>>> [ ... ] >>>>>> one needs to resort to something like: >>>>>> >>>>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do >>>>>> perf probe $symbol >>&g...

...chi.com> wrote: > >> (2013/11/22 11:35), Masami Hiramatsu wrote: >>> (2013/11/21 16:29), Ingo Molnar wrote: >>>> >>>> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: >>>> >>>>> (2013/11/21 2:36), Frank Ch. Eigler wrote: >>>> >>>> [ ... ] >>>>>> one needs to resort to something like: >>>>>> >>>>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do >>>>>> perf probe $symbol >>&g...

https://bugzilla.mindrot.org/show_bug.cgi?id=1256 Frank Ch. Eigler <fche at elastic.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fche at elastic.org -- You are receiving this mail because: You are watching t...

* Frank Ch. Eigler <fche at redhat.com> wrote: > masami.hiramatsu.pt wrote: > > > [...] This series also includes a change which prohibits probing > > on the address in .entry.text because the code is used for very > > low-level sensitive interrupt/syscall entries. Probing such code...

On Wed, 20 Nov 2013 12:36:00 -0500 "Frank Ch. Eigler" <fche at redhat.com> wrote: > Hi - > > > > Does this new blacklist cover enough that the kernel now survives a > > > broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms? > > > > That's generally the purpose of the annotations - i...

(2013/11/21 2:36), Frank Ch. Eigler wrote: > Hi - > >>> Does this new blacklist cover enough that the kernel now survives a >>> broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms? >> >> That's generally the purpose of the annotations - if it doesn't then >> that'...

(2013/11/21 16:29), Ingo Molnar wrote: > > * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >> (2013/11/21 2:36), Frank Ch. Eigler wrote: > > [ ... ] >>> one needs to resort to something like: >>> >>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do >>> perf probe $symbol >>> done >>> >>> then wait for a few hours for that to...

...ami.hiramatsu.pt at hitachi.com> wrote: > (2013/11/22 11:35), Masami Hiramatsu wrote: > > (2013/11/21 16:29), Ingo Molnar wrote: > >> > >> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >> > >>> (2013/11/21 2:36), Frank Ch. Eigler wrote: > >> > >> [ ... ] > >>>> one needs to resort to something like: > >>>> > >>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > >>>> perf probe $symbol > >>>> done &...

...>> (2013/11/22 11:35), Masami Hiramatsu wrote: > >>> (2013/11/21 16:29), Ingo Molnar wrote: > >>>> > >>>> * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >>>> > >>>>> (2013/11/21 2:36), Frank Ch. Eigler wrote: > >>>> > >>>> [ ... ] > >>>>>> one needs to resort to something like: > >>>>>> > >>>>>> # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > >>>>>>...

...g list i''m reposting here, since there is obvious interest. James Dickens uadmin.blogspot.com ---------- Forwarded message ---------- From: James Dickens <jamesd.wi at gmail.com> Date: Sep 13, 2006 1:51 PM Subject: Re: Systemtap vs Dtrace web page corrections. To: "Frank Ch. Eigler" <fche at redhat.com> Cc: systemtap at sources.redhat.com On 13 Sep 2006 09:43:36 -0400, Frank Ch. Eigler <fche at redhat.com> wrote: > > James Dickens wrote: > > > [...] > > Kernel Lock in: > > [...] Systemtap isn''t even stable enough to run a...

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

masami.hiramatsu.pt wrote: > [...] This series also includes a change which prohibits probing on > the address in .entry.text because the code is used for very > low-level sensitive interrupt/syscall entries. Probing such code may > cause unexpected result (actually most of that area is already in > the kprobe blacklist). So I've decide to prohibit probing all of > them.

masami.hiramatsu.pt wrote: > [...] This series also includes a change which prohibits probing on > the address in .entry.text because the code is used for very > low-level sensitive interrupt/syscall entries. Probing such code may > cause unexpected result (actually most of that area is already in > the kprobe blacklist). So I've decide to prohibit probing all of > them.