From: Igor Mammedov <imammedo@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
Claudio Fontana <cfontana@suse.de>
Subject: Re: [PATCH] Revert "intel_iommu: Fix irqchip / X2APIC configuration checks"
Date: Mon, 26 Sep 2022 11:33:11 +0200 [thread overview]
Message-ID: <20220926113311.417316b7@redhat.com> (raw)
In-Reply-To: <Yy5c7M10df3OINwH@x1n>
On Fri, 23 Sep 2022 21:27:08 -0400
Peter Xu <peterx@redhat.com> wrote:
> On Fri, Sep 23, 2022 at 06:03:44PM -0400, Peter Xu wrote:
> > On Fri, Sep 23, 2022 at 10:41:59AM +0200, Igor Mammedov wrote:
> > > It's worth putting history excavation with explanation what is broken and why
> > > compat stuff is being ignored in the patch.
> >
> > Makes sense, I'll amend the commit message and repost. Thanks,
>
> There's actually one way to slightly remedy this single case, mostly for
> any QEMU 7.1.0 user with -smp <=8 and the intel iommu (as 77250171bdc02 is
> merged only in 7.1.0).
>
> We can have one compact parameter x-eim-enable-kvm-x2apic, setting it "on"
> by default, "off" for 7.1, and "on" for 7.0-.
>
> I'm not very sure whether that'll worth it. Any thoughts?
How it (enabling x2apic API) would affect kvm/guests running with 8 or less CPUs
and with intel iommu + remapping?
>
next prev parent reply other threads:[~2022-09-26 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:12 [PATCH] Revert "intel_iommu: Fix irqchip / X2APIC configuration checks" Peter Xu
2022-09-22 1:32 ` Jason Wang
2022-09-22 16:49 ` Peter Xu
2022-09-22 13:46 ` Igor Mammedov
2022-09-22 16:40 ` Peter Xu
2022-09-23 8:20 ` Igor Mammedov
2022-09-23 8:41 ` Igor Mammedov
2022-09-23 22:03 ` Peter Xu
2022-09-24 1:27 ` Peter Xu
2022-09-26 9:33 ` Igor Mammedov [this message]
2022-09-26 15:17 ` Peter Xu
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=20220926113311.417316b7@redhat.com \
--to=imammedo@redhat.com \
--cc=cfontana@suse.de \
--cc=dwmw2@infradead.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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).