From: Andi Kleen <andi@firstfloor.org>
To: jmerkey@wolfmountaingroup.com
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.26 2/25] mdb: Merkey's Kernel Debugger
Date: Wed, 6 Aug 2008 04:01:52 +0200 [thread overview]
Message-ID: <20080806020152.GA24801@one.firstfloor.org> (raw)
In-Reply-To: <44644.166.70.238.45.1217985860.squirrel@webmail.wolfmountaingroup.com>
On Tue, Aug 05, 2008 at 07:24:20PM -0600, jmerkey@wolfmountaingroup.com wrote:
>
> I'll post some patches with these changes and submit it as a module. I
> will of course need to patch the kernel to introduce the die notifiers
> where
> they are not and there's the issue of cross call NMI to stop other
> processors on SMP.
>
> That's the real issues, Andi, is the xcall stuff for IPC to control all
> the processors.
NMIs have die notifiers too. That said a cleaner way would be to generalize
the synchronization code already in kdump and reuse that.
-Andi
next prev parent reply other threads:[~2008-08-06 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 2:10 [PATCH 2.6.26 2/25] mdb: Merkey's Kernel Debugger jmerkey
2008-08-06 1:35 ` Andi Kleen
2008-08-06 1:24 ` jmerkey
2008-08-06 2:01 ` Andi Kleen [this message]
2008-08-06 1:45 ` jmerkey
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=20080806020152.GA24801@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jmerkey@wolfmountaingroup.com \
--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