From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [RFC][PATCH] KVM: SVM: Defer NMI injection after IRET via interrupt
Date: Mon, 15 Feb 2010 09:23:44 +0100 [thread overview]
Message-ID: <4B790490.3040001@web.de> (raw)
In-Reply-To: <20100215072055.GB19478@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4193 bytes --]
Gleb Natapov wrote:
> On Sun, Feb 14, 2010 at 06:51:15PM +0100, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Stolen from Xen: Instead if stepping over IRET, use the interrupt shadow
>> to inject the NMI on IRET while still deferring its delivery after the
>> instruction. This has the same limitation as the existing approach:
>> Exceptions raised by the IRET will trigger an early NMI injection. The
>> advantages are that we avoid one VM exit and we no longer have to fiddle
>> with TF which can conflict with other users.
>>
> Neat. I have a test case for this. I'll run it today or tomorrow and let
> you know.
Don't spend too much effort, I misunderstood the trick. It actually
still requires an interrupt window exit, and that would in fact be a
drawback when returning to an IRQ-disabled section.
Jan
>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Note: untested!
>>
>> arch/x86/kvm/svm.c | 40 +++++++++++++---------------------------
>> 1 files changed, 13 insertions(+), 27 deletions(-)
>>
>> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
>> index 52f78dd..f355dc6 100644
>> --- a/arch/x86/kvm/svm.c
>> +++ b/arch/x86/kvm/svm.c
>> @@ -107,8 +107,6 @@ struct vcpu_svm {
>> u32 *msrpm;
>>
>> struct nested_state nested;
>> -
>> - bool nmi_singlestep;
>> };
>>
>> /* enable NPT for AMD64 and X86 with PAE */
>> @@ -1075,9 +1073,6 @@ static void update_db_intercept(struct kvm_vcpu *vcpu)
>> svm->vmcb->control.intercept_exceptions &=
>> ~((1 << DB_VECTOR) | (1 << BP_VECTOR));
>>
>> - if (svm->nmi_singlestep)
>> - svm->vmcb->control.intercept_exceptions |= (1 << DB_VECTOR);
>> -
>> if (vcpu->guest_debug & KVM_GUESTDBG_ENABLE) {
>> if (vcpu->guest_debug &
>> (KVM_GUESTDBG_SINGLESTEP | KVM_GUESTDBG_USE_HW_BP))
>> @@ -1213,20 +1208,11 @@ static int db_interception(struct vcpu_svm *svm)
>> struct kvm_run *kvm_run = svm->vcpu.run;
>>
>> if (!(svm->vcpu.guest_debug &
>> - (KVM_GUESTDBG_SINGLESTEP | KVM_GUESTDBG_USE_HW_BP)) &&
>> - !svm->nmi_singlestep) {
>> + (KVM_GUESTDBG_SINGLESTEP | KVM_GUESTDBG_USE_HW_BP))) {
>> kvm_queue_exception(&svm->vcpu, DB_VECTOR);
>> return 1;
>> }
>>
>> - if (svm->nmi_singlestep) {
>> - svm->nmi_singlestep = false;
>> - if (!(svm->vcpu.guest_debug & KVM_GUESTDBG_SINGLESTEP))
>> - svm->vmcb->save.rflags &=
>> - ~(X86_EFLAGS_TF | X86_EFLAGS_RF);
>> - update_db_intercept(&svm->vcpu);
>> - }
>> -
>> if (svm->vcpu.guest_debug &
>> (KVM_GUESTDBG_SINGLESTEP | KVM_GUESTDBG_USE_HW_BP)){
>> kvm_run->exit_reason = KVM_EXIT_DEBUG;
>> @@ -2471,6 +2457,17 @@ static void svm_inject_nmi(struct kvm_vcpu *vcpu)
>> {
>> struct vcpu_svm *svm = to_svm(vcpu);
>>
>> + if (svm->vcpu.arch.hflags & HF_IRET_MASK) {
>> + /*
>> + * Inject the NMI before IRET completed, but defer delivery
>> + * by one instruction with the help of the interrupt shadow.
>> + * Works at least as long as the IRET does not trigger an
>> + * exception.
>> + */
>> + svm->vcpu.arch.hflags &= ~HF_IRET_MASK;
>> + svm->vmcb->control.int_state |= SVM_INTERRUPT_SHADOW_MASK;
>> + }
>> +
>> svm->vmcb->control.event_inj = SVM_EVTINJ_VALID | SVM_EVTINJ_TYPE_NMI;
>> vcpu->arch.hflags |= HF_NMI_MASK;
>> svm->vmcb->control.intercept |= (1UL << INTERCEPT_IRET);
>> @@ -2576,18 +2573,7 @@ static void enable_irq_window(struct kvm_vcpu *vcpu)
>>
>> static void enable_nmi_window(struct kvm_vcpu *vcpu)
>> {
>> - struct vcpu_svm *svm = to_svm(vcpu);
>> -
>> - if ((svm->vcpu.arch.hflags & (HF_NMI_MASK | HF_IRET_MASK))
>> - == HF_NMI_MASK)
>> - return; /* IRET will cause a vm exit */
>> -
>> - /* Something prevents NMI from been injected. Single step over
>> - possible problem (IRET or exception injection or interrupt
>> - shadow) */
>> - svm->nmi_singlestep = true;
>> - svm->vmcb->save.rflags |= (X86_EFLAGS_TF | X86_EFLAGS_RF);
>> - update_db_intercept(vcpu);
>> + /* VM exit on IRET was already armed on injection */
>> }
>>
>> static int svm_set_tss_addr(struct kvm *kvm, unsigned int addr)
>>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2010-02-15 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 17:51 [RFC][PATCH] KVM: SVM: Defer NMI injection after IRET via interrupt Jan Kiszka
2010-02-15 7:20 ` Gleb Natapov
2010-02-15 8:23 ` Jan Kiszka [this message]
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=4B790490.3040001@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--cc=kvm@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