From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 2/2] KVM: SVM: check for progress after IRET interception
Date: Thu, 03 Feb 2011 17:58:47 +0200 [thread overview]
Message-ID: <4D4AD0B7.4090809@redhat.com> (raw)
In-Reply-To: <4D4ACFD9.9000203@siemens.com>
On 02/03/2011 05:55 PM, Jan Kiszka wrote:
> >
> > What's an interrupt window without IRET interception?
>
> I don't the details, but I thought you could get something like an
> interrupt-window-open interception by (fake-)injecting an IRQ and
> intercepting on VIRQ acceptance. That will not work if returning to and
> staying in irq-disabled guest code, therefore the timeout, but it should
> be most efficient (specifically if the guest uses NMIs for things like
> perf).
>
Since NMIs are used to break out of irq-disabled regions (watchdog, NMI
IPIs during reboots) I'm wary of such a solution.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-03 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:02 [PATCH 0/2] SVM NMI fixes Avi Kivity
2011-02-03 15:02 ` [PATCH 1/2] KVM: Fix race between nmi injection and enabling nmi window Avi Kivity
2011-02-03 15:11 ` Jan Kiszka
2011-02-03 15:15 ` Avi Kivity
2011-02-03 15:02 ` [PATCH 2/2] KVM: SVM: check for progress after IRET interception Avi Kivity
2011-02-03 15:07 ` Avi Kivity
2011-02-03 15:21 ` Jan Kiszka
2011-02-03 15:30 ` Avi Kivity
2011-02-03 15:55 ` Jan Kiszka
2011-02-03 15:58 ` Avi Kivity [this message]
2011-02-03 16:14 ` Jan Kiszka
2011-02-03 16:20 ` Avi Kivity
2011-02-03 16:30 ` Jan Kiszka
2011-02-08 13:49 ` Marcelo Tosatti
2011-02-08 14:05 ` 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=4D4AD0B7.4090809@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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.