On Tue, Feb 23, 2016 at 01:52:44AM +0100, Luis R. Rodriguez wrote:
> On Mon, Feb 22, 2016 at 01:34:05AM +, 平松雅巳 / HIRAMATU，MASAMI wrote:
> > >From: Luis R. Rodriguez [mailto:mcg...@kernel.org]
> > >
> > >kprobe makes use of two custom sections:
> > >
> > >type name begin
On Mon, Feb 22, 2016 at 01:34:05AM +, 平松雅巳 / HIRAMATU，MASAMI wrote:
> >From: Luis R. Rodriguez [mailto:mcg...@kernel.org]
> >
> >kprobe makes use of two custom sections:
> >
> >type name beginend
> >init.data _kprobe_blacklist __start_kprobe_blacklist
>From: Luis R. Rodriguez [mailto:mcg...@kernel.org]
>
>kprobe makes use of two custom sections:
>
>type name beginend
>init.data _kprobe_blacklist __start_kprobe_blacklist __stop_kprobe_blacklist
>text .kprobes.text __kprobes_text_start_
On Fri, Feb 19, 2016 at 02:15:11PM +, Russell King - ARM Linux wrote:
> On Fri, Feb 19, 2016 at 05:45:59AM -0800, Luis R. Rodriguez wrote:
> > kprobe makes use of two custom sections:
> >
> > type name beginend
> > init.data _kprobe_blacklist __start_
On Fri, Feb 19, 2016 at 05:45:59AM -0800, Luis R. Rodriguez wrote:
> kprobe makes use of two custom sections:
>
> type name beginend
> init.data _kprobe_blacklist __start_kprobe_blacklist __stop_kprobe_blacklist
> text .kprobes.text __kprobes_te
kprobe makes use of two custom sections:
type name beginend
init.data _kprobe_blacklist __start_kprobe_blacklist__stop_kprobe_blacklist
text .kprobes.text __kprobes_text_start__kprobes_text_end
Port these to the linker table generic
