From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm-devel <kvm@vger.kernel.org>, "Yang, Sheng" <sheng.yang@intel.com>
Subject: Re: [PATCH] kvm-userspace: Cleanup user space NMI injection
Date: Wed, 26 Nov 2008 13:21:04 +0200 [thread overview]
Message-ID: <492D3120.7030902@redhat.com> (raw)
In-Reply-To: <492AC80E.8080906@siemens.com>
Jan Kiszka wrote:
> Cleanup redundant check for an open NMI window before injecting. This
> will no longer be supported by the kernel, and it was broken by design
> anyway.
>
> This change still allows to run the user space against older kernel
> modules.
>
>
Hm. For interrupts we need to check, since the interrupt might be
deasserted or masked while the window is closed.
Is there no way that this can happen for NMIs?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-26 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 15:28 [PATCH] kvm-userspace: Cleanup user space NMI injection Jan Kiszka
2008-11-26 11:21 ` Avi Kivity [this message]
2008-11-26 11:43 ` Jan Kiszka
2008-11-26 16:26 ` Avi Kivity
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=492D3120.7030902@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.com \
/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