From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] x86: ioapic: conditionally upgrade IOAPIC version
Date: Mon, 1 Aug 2016 12:38:58 +0200 [thread overview]
Message-ID: <a120592d-db60-f821-27a9-a226df4535c8@redhat.com> (raw)
In-Reply-To: <1469503738-28269-1-git-send-email-peterx@redhat.com>
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.
Thanks,
Paolo
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> hw/intc/ioapic.c | 25 ++++++++++++++++++++++++-
> include/hw/i386/ioapic_internal.h | 3 +--
> 2 files changed, 25 insertions(+), 3 deletions(-)
>
> diff --git a/hw/intc/ioapic.c b/hw/intc/ioapic.c
> index 2d3282a..cd3f283 100644
> --- a/hw/intc/ioapic.c
> +++ b/hw/intc/ioapic.c
> @@ -244,6 +244,23 @@ void ioapic_dump_state(Monitor *mon, const QDict *qdict)
> }
> }
>
> +static uint32_t ioapic_get_version(void)
> +{
> + X86IOMMUState *iommu = x86_iommu_get_default();
> +
> + /*
> + * If we enabled vIOMMU IR, we provide a upgraded version of
> + * IOAPIC 0x20, which support explicit EOI request from guest.
> + * This fixes a bug that IR not working on some old upstream
> + * kernels (before v4.0, commit d32932d) or most RHEL ones.
> + */
> + if (iommu && iommu->intr_supported) {
> + return 0x20;
> + }
> +
> + return 0x11;
> +}
> +
> static uint64_t
> ioapic_mem_read(void *opaque, hwaddr addr, unsigned int size)
> {
> @@ -265,7 +282,7 @@ ioapic_mem_read(void *opaque, hwaddr addr, unsigned int size)
> val = s->id << IOAPIC_ID_SHIFT;
> break;
> case IOAPIC_REG_VER:
> - val = IOAPIC_VERSION |
> + val = ioapic_get_version() |
> ((IOAPIC_NUM_PINS - 1) << IOAPIC_VER_ENTRIES_SHIFT);
> break;
> default:
> @@ -354,6 +371,12 @@ ioapic_mem_write(void *opaque, hwaddr addr, uint64_t val,
> }
> }
> break;
> + case IOAPIC_EOI:
> + if (size != 4 || ioapic_get_version() != 0x20) {
> + break;
> + }
> + ioapic_eoi_broadcast(val);
> + break;
> }
>
> ioapic_update_kvm_routes(s);
> diff --git a/include/hw/i386/ioapic_internal.h b/include/hw/i386/ioapic_internal.h
> index d89ea1b..6f266c3 100644
> --- a/include/hw/i386/ioapic_internal.h
> +++ b/include/hw/i386/ioapic_internal.h
> @@ -29,8 +29,6 @@
>
> #define MAX_IOAPICS 1
>
> -#define IOAPIC_VERSION 0x11
> -
> #define IOAPIC_LVT_DEST_SHIFT 56
> #define IOAPIC_LVT_DEST_IDX_SHIFT 48
> #define IOAPIC_LVT_MASKED_SHIFT 16
> @@ -71,6 +69,7 @@
>
> #define IOAPIC_IOREGSEL 0x00
> #define IOAPIC_IOWIN 0x10
> +#define IOAPIC_EOI 0x40
>
> #define IOAPIC_REG_ID 0x00
> #define IOAPIC_REG_VER 0x01
>
next prev parent reply other threads:[~2016-08-01 10:39 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 [this message]
2016-08-01 14:00 ` 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=a120592d-db60-f821-27a9-a226df4535c8@redhat.com \
--to=pbonzini@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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).