From: Peter Xu <peterx@redhat.com>
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: "Joao Martins" <joao.m.martins@oracle.com>,
"David Woodhouse" <dwmw2@infradead.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH v6 4/5] intel_iommu: allow Extended Interrupt Mode when using userspace APIC
Date: Wed, 26 Jul 2023 13:22:12 -0400 [thread overview]
Message-ID: <ZMFWRIrp0AfJisTM@x1n> (raw)
In-Reply-To: <46f648af-095e-b4ec-4fd4-cb9f413cdab2@gmail.com>
On Fri, Jul 21, 2023 at 10:35:01PM +0700, Bui Quang Minh wrote:
> On 7/21/23 03:47, Peter Xu wrote:
> > On Mon, Jul 17, 2023 at 11:29:56PM +0700, Bui Quang Minh wrote:
> > > On 7/17/23 17:47, Joao Martins wrote:
> > > > +Peter, +Jason (intel-iommu maintainer/reviewer)
> >
> > Thanks for copying me, Joan.
> >
> > > >
> > > > On 15/07/2023 16:22, Bui Quang Minh wrote:
> > > > > As userspace APIC now supports x2APIC, intel interrupt remapping
> > > > > hardware can be set to EIM mode when userspace local APIC is used.
> > > > >
> > > > > Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> > > > > Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
> > > > > ---
> > > > > hw/i386/intel_iommu.c | 11 -----------
> > > > > 1 file changed, 11 deletions(-)
> > > > >
> > > > > diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> > > > > index dcc334060c..5e576f6059 100644
> > > > > --- a/hw/i386/intel_iommu.c
> > > > > +++ b/hw/i386/intel_iommu.c
> > > > > @@ -4043,17 +4043,6 @@ static bool vtd_decide_config(IntelIOMMUState *s, Error **errp)
> > > > > && x86_iommu_ir_supported(x86_iommu) ?
> > > > > ON_OFF_AUTO_ON : ON_OFF_AUTO_OFF;
> > > > > }
> > > > > - if (s->intr_eim == ON_OFF_AUTO_ON && !s->buggy_eim) {
> > > > > - if (!kvm_irqchip_is_split()) {
> > > > > - error_setg(errp, "eim=on requires accel=kvm,kernel-irqchip=split");
> > > > > - return false;
> > > > > - }
> > > > > - if (!kvm_enable_x2apic()) {
> > > > > - error_setg(errp, "eim=on requires support on the KVM side"
> > > > > - "(X2APIC_API, first shipped in v4.7)");
> > > > > - return false;
> > > > > - }
> > > > > - }
> > > > Given commit 20ca47429e ('Revert "intel_iommu: Fix irqchip / X2APIC
> > > > configuration checks"'), won't we regress behaviour again for the accel=kvm
> > > > case by dropping the kvm_enable_x2apic() call here?
> > > >
> > > > Perhaps if we support userspace APIC with TCG the check just needs to be redone
> > > > to instead avoid always requiring kvm e.g.:
> > > >
> > > > if (kvm_irqchip_in_kernel()) {
> > > > error_setg(errp, "eim=on requires accel=kvm,kernel-irqchip=split"
> > > > "(X2APIC_API, first shipped in v4.7)");
> > > > }
> > > >
> > > > if (kvm_irqchip_is_split() && !kvm_enable_x2apic()) {
> > > > error_setg(errp, "eim=on requires support on the KVM side"
> > > > "(X2APIC_API, first shipped in v4.7)");
> > > > return false;
> > > > }
> > >
> > > Thank you for your review. I think the check for kvm_irqchip_in_kernel() is
> > > not correct, AFAIK, kvm_irqchip_is_split() == true also means
> > > kvm_irqchip_in_kernel() == true on x86. To check if kernel-irqchip = on, we
> > > need to do something like in x86_iommu_realize
> > >
> > > bool irq_all_kernel = kvm_irqchip_in_kernel() &&
> > > !kvm_irqchip_is_split();
> > >
> > > The original check for !kvm_irqchip_is_split means emulated/userspace APIC.
> > > It's because to reach that check x86_iommu_ir_supported(...) == true and
> > > x86_iommu_ir_supported(...) == true is not supported when kernel-irqchip =
> > > on (there is a check for this in x86_iommu_realize)
> > >
> > > So I think we need to change the check to
> > >
> > > if (s->intr_eim == ON_OFF_AUTO_ON && !s->buggy_eim) {
> > > if (kvm_irqchip_is_split() && !kvm_enable_x2apic()) {
> > > error_setg(errp, "eim=on requires support on the KVM side"
> > > "(X2APIC_API, first shipped in v4.7)");
> > > return false;
> > > }
> > > }
> > >
> > > Is it OK?
> >
> > Mostly to me, except that we may also want to keep failing if all irq chips
> > are in kernel?
>
> Yes, that behavior does not change after this patch. x86_iommu_realize in
> the parent type TYPE_X86_IOMMU_DEVICE fails when interrupt remapping is on
> and all irq chips are in kernel already.
>
> static void x86_iommu_realize(DeviceState *dev, Error **errp)
> {
> /* ... */
> /* Both Intel and AMD IOMMU IR only support "kernel-irqchip
> {off|split}" */
> if (x86_iommu_ir_supported(x86_iommu) && irq_all_kernel) {
> error_setg(errp, "Interrupt Remapping cannot work with "
> "kernel-irqchip=on, please use 'split|off'.");
> return;
> }
> /* ... */
> }
>
>
> So in case we reach here in with the interrupt remapping is on and decide
> whether eim is on or not, it cannot be that irq chips are all in kernel.
Ah that's okay then, thanks.
--
Peter Xu
next prev parent reply other threads:[~2023-07-26 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 15:22 [PATCH v6 0/5] Support x2APIC mode with TCG accelerator Bui Quang Minh
2023-07-15 15:22 ` [PATCH v6 1/5] i386/tcg: implement x2APIC registers MSR access Bui Quang Minh
2023-07-15 15:22 ` [PATCH v6 2/5] apic: add support for x2APIC mode Bui Quang Minh
2023-07-15 15:22 ` [PATCH v6 3/5] apic, i386/tcg: add x2apic transitions Bui Quang Minh
2023-07-15 15:22 ` [PATCH v6 4/5] intel_iommu: allow Extended Interrupt Mode when using userspace APIC Bui Quang Minh
2023-07-17 10:47 ` Joao Martins
2023-07-17 16:29 ` Bui Quang Minh
2023-07-20 20:47 ` Peter Xu
2023-07-21 15:35 ` Bui Quang Minh
2023-07-26 17:22 ` Peter Xu [this message]
2023-07-15 15:22 ` [PATCH v6 5/5] amd_iommu: report x2APIC support to the operating system Bui Quang Minh
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=ZMFWRIrp0AfJisTM@x1n \
--to=peterx@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dwmw2@infradead.org \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=minhquangbui99@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).