From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, Jeremy Fitzhardinge <jeremy@goop.org>,
Steven Rostedt <rostedt@goodmis.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86 NMI-safe INT3 and Page Fault (v2)
Date: Wed, 16 Apr 2008 11:18:20 -0400 [thread overview]
Message-ID: <480618BC.1030800@zytor.com> (raw)
In-Reply-To: <20080416151054.GA32456@elte.hu>
Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> thanks Mathieu, i've picked this up into x86.git for more testing.
>
> ... but had to drop it due to missing PARAVIRT support which broke the
> build. I guess on paravirt we could just initially define
> INTERRUPT_RETURN_NMI_SAFE to iret, etc.?
I figure that's what we'd have to do. This is exactly the fundamental
problem with paravirt - it relies on a different, an ill-defined, model
of the platform than the (generally well-defined) hardware specification
provides.
-hpa
next prev parent reply other threads:[~2008-04-16 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080414230344.GA16061@Krystal>
2008-04-14 23:05 ` [RFC PATCH] x86 NMI-safe INT3 and Page Fault (v2) Mathieu Desnoyers
2008-04-16 13:06 ` Ingo Molnar
2008-04-16 13:47 ` [TEST PATCH] Test NMI kprobe modules Mathieu Desnoyers
2008-04-16 14:34 ` Ingo Molnar
2008-04-16 14:54 ` Mathieu Desnoyers
2008-04-16 15:10 ` [RFC PATCH] x86 NMI-safe INT3 and Page Fault (v2) Ingo Molnar
2008-04-16 15:18 ` H. Peter Anvin [this message]
2008-04-16 15:37 ` Mathieu Desnoyers
2008-04-16 16:03 ` Jeremy Fitzhardinge
2008-04-18 0:48 ` Mathieu Desnoyers
2008-04-18 9:49 ` Jeremy Fitzhardinge
2008-04-16 16:28 ` [RFC PATCH] x86 NMI-safe INT3 and Page Fault (v3) Mathieu Desnoyers
2008-04-16 17:57 ` Jeremy Fitzhardinge
2008-04-17 16:29 ` Mathieu Desnoyers
2008-04-17 16:45 ` Andi Kleen
2008-04-18 0:05 ` Mathieu Desnoyers
2008-04-18 8:27 ` Andi Kleen
2008-04-19 21:18 ` Mathieu Desnoyers
2008-04-20 12:58 ` 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=480618BC.1030800@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.