From: Peter Xu <peterx@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] x86: ioapic: upgrade emulated IOAPIC to ver 0x20
Date: Tue, 26 Jul 2016 10:56:51 +0800 [thread overview]
Message-ID: <20160726025651.GC14985@pxdev.nay.redhat.com> (raw)
In-Reply-To: <20160726051419-mutt-send-email-mst@kernel.org>
On Tue, Jul 26, 2016 at 05:15:58AM +0300, Michael S. Tsirkin wrote:
> On Mon, Jul 25, 2016 at 07:36:24PM +0800, 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.
> >
> > This patch is only useful when vIOMMU IR is enabled (which still do not
> > support kernel IOAPIC). So here we are only upgrading QEMU IOAPIC chip
> > to version 0x20. For kernel based IOAPIC, the version will still be
> > 0x11.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
>
> As a minimum, we need to make sure not to change this for
> old machine types.
>
> Given the timing, limiting this for when IR is enabled
> would be a good idea I think.
Thanks Michael. Then let me cook another patch specified to IR, and
then we can choose either one we want.
-- peterx
prev parent reply other threads:[~2016-07-26 2:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 11:36 [Qemu-devel] [PATCH] x86: ioapic: upgrade emulated IOAPIC to ver 0x20 Peter Xu
2016-07-26 2:15 ` Michael S. Tsirkin
2016-07-26 2:56 ` 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=20160726025651.GC14985@pxdev.nay.redhat.com \
--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).