From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Lai Jiangshan <laijs@linux.alibaba.com>,
Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 4/4] KVM/VMX: Fold handle_interrupt_nmi_irqoff() into its solo caller
Date: Fri, 30 Apr 2021 11:06:32 +0200 [thread overview]
Message-ID: <ba3f6230-8766-92e5-1189-a114c236fd48@redhat.com> (raw)
In-Reply-To: <87y2d0du02.ffs@nanos.tec.linutronix.de>
On 30/04/21 11:03, Thomas Gleixner wrote:
> Lai,
>
> On Tue, Apr 27 2021 at 07:09, Lai Jiangshan wrote:
>> u32 intr_info = vmx_get_intr_info(&vmx->vcpu);
>> @@ -6427,12 +6417,19 @@ static void handle_exception_nmi_irqoff(struct vcpu_vmx *vmx)
>> static void handle_external_interrupt_irqoff(struct kvm_vcpu *vcpu)
>> {
>> u32 intr_info = vmx_get_intr_info(vcpu);
>> + unsigned int vector;
>> + gate_desc *desc;
>>
>> if (WARN_ONCE(!is_external_intr(intr_info),
>> "KVM: unexpected VM-Exit interrupt info: 0x%x", intr_info))
>> return;
>>
>> - handle_interrupt_nmi_irqoff(vcpu, intr_info);
>> + vector = intr_info & INTR_INFO_VECTOR_MASK;
>> + desc = (gate_desc *)host_idt_base + vector;
>> +
>> + kvm_before_interrupt(vcpu);
>> + vmx_do_interrupt_nmi_irqoff(gate_offset(desc));
>> + kvm_after_interrupt(vcpu);
>
> So the previous patch does:
>
> + kvm_before_interrupt(&vmx->vcpu);
> + vmx_do_interrupt_nmi_irqoff((unsigned long)asm_noist_exc_nmi);
> + kvm_after_interrupt(&vmx->vcpu);
>
> What is this idt gate descriptor dance for in this code?
NMIs are sent through a different vmexit code (the same one as
exceptions). This one is for interrupts.
Paolo
next prev parent reply other threads:[~2021-04-30 9:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 23:09 [PATCH 0/4] x86: Don't invoke asm_exc_nmi() on the kernel stack Lai Jiangshan
2021-04-26 23:09 ` [PATCH 1/4] x86/xen/entry: Rename xenpv_exc_nmi to noist_exc_nmi Lai Jiangshan
2021-04-28 21:27 ` Steven Rostedt
2021-04-30 7:15 ` Paolo Bonzini
2021-04-30 12:05 ` Steven Rostedt
2021-05-03 19:05 ` Thomas Gleixner
2021-05-03 19:41 ` Thomas Gleixner
2021-05-10 7:59 ` Juergen Gross
2021-04-26 23:09 ` [PATCH 2/4] x86/entry: Use asm_noist_exc_nmi() for NMI in early booting stage Lai Jiangshan
2021-04-28 21:30 ` Steven Rostedt
2021-05-03 20:13 ` Thomas Gleixner
2021-05-03 20:24 ` Thomas Gleixner
2021-05-03 21:45 ` Thomas Gleixner
2021-05-04 12:43 ` Thomas Gleixner
2021-05-04 19:50 ` [PATCH] KVM/VMX: Invoke NMI non-IST entry instead of IST entry Thomas Gleixner
2021-05-04 21:05 ` Maxim Levitsky
2021-05-04 21:12 ` Paolo Bonzini
2021-05-04 21:21 ` Sean Christopherson
2021-05-04 21:23 ` Andy Lutomirski
2021-05-04 21:25 ` Paolo Bonzini
2021-05-04 21:51 ` Sean Christopherson
2021-05-04 21:56 ` Paolo Bonzini
2021-05-05 0:00 ` Thomas Gleixner
2021-05-05 15:44 ` Lai Jiangshan
2021-05-05 1:07 ` Lai Jiangshan
2021-05-05 1:11 ` Andy Lutomirski
2021-05-06 12:14 ` [tip: x86/urgent] " tip-bot2 for Lai Jiangshan
2021-04-26 23:09 ` [PATCH 3/4] " Lai Jiangshan
2021-04-30 2:46 ` Lai Jiangshan
2021-05-03 19:37 ` Thomas Gleixner
2021-05-03 20:02 ` Thomas Gleixner
2021-05-04 8:10 ` Paolo Bonzini
2021-04-26 23:09 ` [PATCH 4/4] KVM/VMX: Fold handle_interrupt_nmi_irqoff() into its solo caller Lai Jiangshan
2021-04-30 9:03 ` Thomas Gleixner
2021-04-30 9:06 ` Paolo Bonzini [this message]
2021-04-30 23:28 ` Thomas Gleixner
2021-04-30 7:14 ` [PATCH 0/4] x86: Don't invoke asm_exc_nmi() on the kernel stack Paolo Bonzini
2021-05-03 14:36 ` Thomas Gleixner
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=ba3f6230-8766-92e5-1189-a114c236fd48@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jiangshanlai@gmail.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=laijs@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).