From: Stephen Hemminger <shemminger@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NMI notifiers for 2.5
Date: 04 Dec 2002 13:54:13 -0800 [thread overview]
Message-ID: <1039038853.20387.19.camel@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <p731y4xtulg.fsf@oldwotan.suse.de>
> For a more comprehensive variant see include/asm-x86_64/kdebug.h
> The x86-64 variant cannot be 1:1 copied because it's still incomplete
> and e.g. does not implement veto for all places where it's needed.
>
Didn't look in x86_64 code. Would it just make more sense to turn this
into an architecture independent mechanism and provide sample versions
for x86_64 and i386?
next prev parent reply other threads:[~2002-12-04 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1039027142.20387.11.camel@dell_ss3.pdx.osdl.net.suse.lists.linux.kernel>
2002-12-04 20:08 ` Andi Kleen
2002-12-04 21:54 ` Stephen Hemminger [this message]
2002-12-05 7:09 ` Andi Kleen
2002-12-04 19:20 Larry Sendlosky
2002-12-04 19:41 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2002-12-04 18:39 Stephen Hemminger
2002-12-04 19:01 ` John Levon
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=1039038853.20387.19.camel@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=ak@suse.de \
--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®