From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Adrian Bunk <bunk@stusta.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] x8664_ksyms.c: unexport register_die_notifier
Date: Mon, 17 Jan 2005 12:19:28 +0100 [thread overview]
Message-ID: <1105960768.6304.69.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050117101318.GF29270@wotan.suse.de>
On Mon, 2005-01-17 at 11:13 +0100, Andi Kleen wrote:
> On Mon, Jan 17, 2005 at 10:54:18AM +0100, Arjan van de Ven wrote:
> > On Mon, 2005-01-17 at 10:26 +0100, Andi Kleen wrote:
> > > On Sun, Jan 16, 2005 at 08:46:49AM +0100, Adrian Bunk wrote:
> > > > The only user of register_die_notifier (kernel/kprobes.c) can't be
> > > > built modular. Therefore, it's the EXPORT_SYMBOL is superfluous.
> > >
> > > Please don't apply this, it was especially intended for modular debuggers.
> > > There is already a hacvked kdb around that uses it.
> >
> > eh didn't Tigran just mail lkml claiming that kdb and x86-64 really
> > don't mix ??
>
> It cannot display function arguments and uses imprecise backtrace right now
> (like normal oopses), other than that it works just fine.
does it need any other kernel patches? Because if it does it might as
well patch this export in for it's specialist use
next prev parent reply other threads:[~2005-01-17 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 7:46 Adrian Bunk
2005-01-17 9:26 ` Andi Kleen
2005-01-17 9:54 ` Arjan van de Ven
2005-01-17 10:07 ` [discuss] " Tigran Aivazian
2005-01-17 10:13 ` Andi Kleen
2005-01-17 11:19 ` Arjan van de Ven [this message]
2005-01-17 11:26 ` Andi Kleen
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=1105960768.6304.69.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ak@suse.de \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®