From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, "H. Peter Anvin" <hpa@zytor.com>,
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:37:31 -0400 [thread overview]
Message-ID: <20080416153731.GA17852@Krystal> (raw)
In-Reply-To: <20080416151054.GA32456@elte.hu>
* Ingo Molnar (mingo@elte.hu) 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.?
>
Yes, I was about to email you about this.
Would it be valid to execute a popf in PARAVIRT or should be have some
special support like the normal iret does ?
And yes, initially using iret for paravirt should just work, but it
would leave the NMI iret issue for paravirt.
Mathieu
> Ingo
>
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-04-16 15:37 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
2008-04-16 15:37 ` Mathieu Desnoyers [this message]
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=20080416153731.GA17852@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=fche@redhat.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox