From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: WARN and fail kvm_set_irq() if a PIC or I/O APIC vector is invalid
Date: Fri, 19 Jun 2026 07:33:52 +0000 [thread overview]
Message-ID: <b635ef8f645f2fb59cc5ccf1b34f63ca86732570.camel@intel.com> (raw)
In-Reply-To: <20260618185213.2019937-1-seanjc@google.com>
On Thu, 2026-06-18 at 11:52 -0700, Sean Christopherson wrote:
> WARN and return an error up the stack if the PIC or I/O APIC encounters an
> invalid vector when injecting an IRQ, as there is no danger to the host and
> thus no justification for potentially panicking the kernel. Don't bug the
> VM either, as the risk of corrupting the guest is minuscule, and the guest
> might even be completely tolerant of a lost interrupt.
>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
>
Reviewed-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2026-06-19 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 18:52 Sean Christopherson
2026-06-19 7:33 ` Huang, Kai [this message]
2026-06-24 9:53 ` Paolo Bonzini
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=b635ef8f645f2fb59cc5ccf1b34f63ca86732570.camel@intel.com \
--to=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
Powered by JetHome