From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] x86: ioapic: conditionally upgrade IOAPIC version
Date: Mon, 1 Aug 2016 22:00:43 +0800 [thread overview]
Message-ID: <20160801140043.GD6207@pxdev.xzpeter.org> (raw)
In-Reply-To: <a120592d-db60-f821-27a9-a226df4535c8@redhat.com>
On Mon, Aug 01, 2016 at 12:38:58PM +0200, Paolo Bonzini wrote:
>
>
> On 26/07/2016 05:28, Peter Xu wrote:
> > IOMMU IR and IOAPIC legacy devices (e.g., e1000) cannot work well
> > together with some old Linux kernels (upstream before v4.0, or any
> > released RHEL kernels). This patch fixes it.
> >
> > The problem is that: some old linux kernels (with IR enabled) only
> > support IOAPIC chips with version 0x20. New kernels after commit d32932d
> > ("x86/irq: Convert IOAPIC to use hierarchical irqdomain interfaces")
> > fixed this problem. To make sure we can work with even old kernels,
> > let's upgrade our IOAPIC to version 0x20.
> >
> > To make sure we have minimum impact on old systems, IOAPIC version is
> > only boosted to 0x20 when vIOMMU IR is enabled. Besides that, the old
> > version 0x11 is used.
>
> I'd rather do this conditional only on the machine type, but as you
> pointed out it's a bit late to change the default in QEMU 2.7.
> Therefore, for 2.7 you could add a property to the IOAPIC device, and
> document that you need "-global ioapic.version=0x20" for interrupt
> remapping to work with Linux <= 4.0. QEMU 2.8 can then flip the default
> for the new machine types.
Yes, an property seems to be a better choice. V3 sent. Thanks!
-- peterx
prev parent reply other threads:[~2016-08-01 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 3:28 [Qemu-devel] [PATCH v2] x86: ioapic: conditionally upgrade IOAPIC version Peter Xu
2016-08-01 10:38 ` Paolo Bonzini
2016-08-01 14:00 ` Peter Xu [this message]
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=20160801140043.GD6207@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).