From: Olaf Hering <olh@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] kprobes needs emulate_step()
Date: Tue, 14 Feb 2006 22:26:37 +0100 [thread overview]
Message-ID: <20060214212637.GA12380@suse.de> (raw)
In-Reply-To: <20060214195442.GA21583@lst.de>
On Tue, Feb 14, Christoph Hellwig wrote:
> On Tue, Feb 14, 2006 at 02:10:50PM +0100, Olaf Hering wrote:
> >
> > KPROBES depends on XMON.
> > arch/powerpc/lib/step.c is only compiled if CONFIG_XMON is enabled.
> >
> > arch/powerpc/kernel/built-in.o:
> > In function `resume_execution':arch/powerpc/kernel/kprobes.c:331: undefined reference to
> > `.emulate_step'
>
> Please compile step.o if either CONFIG_KPROBES or CONFIG_XMON is defined
> instead of adding a depency.
(This one seems to work without warning about duplicate object files or
something.)
KPROBES needs emulate_step()
arch/powerpc/kernel/built-in.o:
In function `resume_execution':arch/powerpc/kernel/kprobes.c:331: undefined reference to
`.emulate_step'
Signed-off-by: Olaf Hering <olh@suse.de>
arch/powerpc/lib/Makefile | 1 +
1 files changed, 1 insertion(+)
Index: linux-2.6.16-rc3-olh/arch/powerpc/lib/Makefile
===================================================================
--- linux-2.6.16-rc3-olh.orig/arch/powerpc/lib/Makefile
+++ linux-2.6.16-rc3-olh/arch/powerpc/lib/Makefile
@@ -12,6 +12,7 @@ obj-$(CONFIG_PPC64) += checksum_64.o cop
memcpy_64.o usercopy_64.o mem_64.o string.o \
strcase.o
obj-$(CONFIG_PPC_ISERIES) += e2a.o
+obj-$(CONFIG_KPROBES) += sstep.o
obj-$(CONFIG_XMON) += sstep.o
ifeq ($(CONFIG_PPC64),y)
prev parent reply other threads:[~2006-02-14 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 13:10 [PATCH] kprobes depends on xmon Olaf Hering
2006-02-14 19:54 ` Christoph Hellwig
2006-02-14 21:26 ` Olaf Hering [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060214212637.GA12380@suse.de \
--to=olh@suse.de \
--cc=hch@lst.de \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).