From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 5/5] intel_iommu: do not allow EIM without KVM support
Date: Fri, 23 Sep 2016 18:52:37 +0800 [thread overview]
Message-ID: <20160923105237.GF29144@pxdev.xzpeter.org> (raw)
In-Reply-To: <76b2b248-d9bc-5a4e-e2fd-aa4fd665005b@redhat.com>
On Fri, Sep 23, 2016 at 12:39:19PM +0200, Paolo Bonzini wrote:
>
>
> On 23/09/2016 12:12, Peter Xu wrote:
> > On Fri, Sep 23, 2016 at 12:03:26PM +0200, Paolo Bonzini wrote:
> >>
> >>
> >> On 23/09/2016 12:02, Peter Xu wrote:
> >>> On Fri, Sep 23, 2016 at 11:27:09AM +0200, Paolo Bonzini wrote:
> >>>>> Since the whole IOMMU feature is new and somewhat experimental, I think
> >>>>> it's okay to just make EIM the default for >=2.8 machine types if KVM is
> >>>>> on (using DEFINE_PROP_ON_OFF_AUTO; auto means true if KVM is on and
> >>>>> false otherwise, and pc-2.7 would set eim=off). It means requiring
> >>>>> kernel 4.8 by default, but I don't think it's a big deal.
> >>> I think the problem is, even we have KVM support for x2apic, we are
> >>> still losing QEMU part. And guests with cluster x2apic and >8 vcpus
> >>> will not working properly on device interrupts, which can be very
> >>> confusing to people (it can boot, but some devices just don't work
> >>> properly, and they won't see useful information in guest dmesg).
> >>
> >> Yes, that's why I suggested EIM=on by default.
> >
> > I am confused. :(
> >
> > Why not we just keep people from that wrong configuration by default,
> > until we have x2apic in QEMU?
>
> Do you mean Igor's patches? I expect that they will go in pretty much
> at the same time as Radim's.
Ah! Yes we have x2apic all here... So I totally agree we should set it
on as default.
(My mistake of not noticing the truth)
Thanks,
-- peterx
next prev parent reply other threads:[~2016-09-23 10:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 21:04 [Qemu-devel] [PATCH 0/5] intel_iommu: fix EIM Radim Krčmář
2016-09-22 21:04 ` [Qemu-devel] [PATCH 1/5] apic: add global apic_get_class() Radim Krčmář
2016-09-23 9:17 ` Peter Xu
2016-09-27 13:28 ` Radim Krčmář
2016-09-22 21:04 ` [Qemu-devel] [PATCH 2/5] apic: add send_msi() to APICCommonClass Radim Krčmář
2016-09-23 9:35 ` Peter Xu
2016-09-26 12:38 ` Igor Mammedov
2016-09-27 13:55 ` Radim Krčmář
2016-09-22 21:04 ` [Qemu-devel] [PATCH 3/5] intel_iommu: pass whole remapped addresses to apic Radim Krčmář
2016-09-23 9:41 ` Peter Xu
2016-09-27 13:56 ` Radim Krčmář
2016-09-27 13:57 ` Igor Mammedov
2016-09-22 21:04 ` [Qemu-devel] [PATCH 4/5] intel_iommu: add "eim" property Radim Krčmář
2016-09-22 21:04 ` [Qemu-devel] [PATCH 5/5] intel_iommu: do not allow EIM without KVM support Radim Krčmář
2016-09-23 9:27 ` Paolo Bonzini
2016-09-23 10:02 ` Peter Xu
2016-09-23 10:03 ` Paolo Bonzini
2016-09-23 10:12 ` Peter Xu
2016-09-23 10:39 ` Paolo Bonzini
2016-09-23 10:52 ` Peter Xu [this message]
2016-09-27 14:01 ` Radim Krčmář
2016-09-27 21:30 ` Paolo Bonzini
2016-09-27 13:07 ` Igor Mammedov
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=20160923105237.GF29144@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.