* recent kprobe work
@ 2005-06-28 21:01 David S. Miller
2005-06-28 21:40 ` Rusty Lynch
0 siblings, 1 reply; 3+ messages in thread
From: David S. Miller @ 2005-06-28 21:01 UTC (permalink / raw)
To: linux-kernel
Can the folks submitting all of the kprobe stuff at least consult me
when they can't figure out how to implement the sparc64 kprobe variant
for new features?
Currently, the sparc64 build is broken by recent kprobe
changes:
kernel/built-in.o: In function `init_kprobes':
: undefined reference to `arch_init'
Also, can we use a more namespace friendly name for this kprobe layer
specific function other than "arch_init()"?
Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: recent kprobe work
2005-06-28 21:01 recent kprobe work David S. Miller
@ 2005-06-28 21:40 ` Rusty Lynch
2005-06-29 0:50 ` Andrew Morton
0 siblings, 1 reply; 3+ messages in thread
From: Rusty Lynch @ 2005-06-28 21:40 UTC (permalink / raw)
To: David S. Miller; +Cc: linux-kernel
On Tue, Jun 28, 2005 at 02:01:36PM -0700, David S. Miller wrote:
>
> Can the folks submitting all of the kprobe stuff at least consult me
> when they can't figure out how to implement the sparc64 kprobe variant
> for new features?
>
> Currently, the sparc64 build is broken by recent kprobe
> changes:
>
> kernel/built-in.o: In function `init_kprobes':
> : undefined reference to `arch_init'
>
> Also, can we use a more namespace friendly name for this kprobe layer
> specific function other than "arch_init()"?
>
> Thanks.
Sorry, just an oversight. We have several arch_* functions, maybe we should
start using kprobes_arch_* instead.
--rusty
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: recent kprobe work
2005-06-28 21:40 ` Rusty Lynch
@ 2005-06-29 0:50 ` Andrew Morton
0 siblings, 0 replies; 3+ messages in thread
From: Andrew Morton @ 2005-06-29 0:50 UTC (permalink / raw)
To: Rusty Lynch; +Cc: davem, linux-kernel
Rusty Lynch <rusty@linux.intel.com> wrote:
>
> On Tue, Jun 28, 2005 at 02:01:36PM -0700, David S. Miller wrote:
> >
> > Can the folks submitting all of the kprobe stuff at least consult me
> > when they can't figure out how to implement the sparc64 kprobe variant
> > for new features?
> >
> > Currently, the sparc64 build is broken by recent kprobe
> > changes:
> >
> > kernel/built-in.o: In function `init_kprobes':
> > : undefined reference to `arch_init'
> >
> > Also, can we use a more namespace friendly name for this kprobe layer
> > specific function other than "arch_init()"?
> >
> > Thanks.
>
> Sorry, just an oversight. We have several arch_* functions, maybe we should
> start using kprobes_arch_* instead.
>
Absolutely - please send a patch once Dave's fix is merged up.
Dave: sorry, I would have caught the missing reference except I'm totally
averse to `make allfooconfig' on non-x86[_64] architectures because so much
stuff simply doesn't work.
But lo. It does work on sparc64.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-29 1:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-28 21:01 recent kprobe work David S. Miller
2005-06-28 21:40 ` Rusty Lynch
2005-06-29 0:50 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox