From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: ehabkost@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, peterx@redhat.com,
Alex Williamson <alex.williamson@redhat.com>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH for-4.1 v2] q35: Revert to kernel irqchip
Date: Wed, 12 Jun 2019 11:01:50 +0200 [thread overview]
Message-ID: <20190612090150.GD6897@redhat.com> (raw)
In-Reply-To: <694a140e-1415-2595-8e22-0834ee17139f@redhat.com>
On Mon, Jun 03, 2019 at 10:06:06AM +0200, Paolo Bonzini wrote:
> On 29/05/19 05:30, Michael S. Tsirkin wrote:
> > On Tue, May 14, 2019 at 02:14:41PM -0600, Alex Williamson wrote:
> >> Commit b2fc91db8447 ("q35: set split kernel irqchip as default") changed
> >> the default for the pc-q35-4.0 machine type to use split irqchip, which
> >> turned out to have disasterous effects on vfio-pci INTx support. KVM
> >> resampling irqfds are registered for handling these interrupts, but
> >> these are non-functional in split irqchip mode. We can't simply test
> >> for split irqchip in QEMU as userspace handling of this interrupt is a
> >> significant performance regression versus KVM handling (GeForce GPUs
> >> assigned to Windows VMs are non-functional without forcing MSI mode or
> >> re-enabling kernel irqchip).
> >>
> >> The resolution is to revert the change in default irqchip mode in the
> >> pc-q35-4.1 machine and create a pc-q35-4.0.1 machine for the 4.0-stable
> >> branch. The qemu-q35-4.0 machine type should not be used in vfio-pci
> >> configurations for devices requiring legacy INTx support without
> >> explicitly modifying the VM configuration to use kernel irqchip.
> >>
> >> Link: https://bugs.launchpad.net/qemu/+bug/1826422
> >> Fixes: b2fc91db8447 ("q35: set split kernel irqchip as default")
> >> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > OK I guess but it's really a kvm patch.
> > So I'd like Paolo to review and merge if appropriate.
> >
> > Can't say this makes me too happy. split irqchip
> > has a bunch of advantages.
>
> Yeah, me too but I don't see an alternative. I'll merge it today.
FYI in Fedora we've had another unrelated regression bug that was identified
as caused by the split irqchip change. With a Windows 7 guest, the clock
is way too fast, for every 1 second wallclock time, 15 seconds passes
in the guest. See the bug for more info:
https://bugzilla.redhat.com/show_bug.cgi?id=1704375
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-06-12 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 20:14 [Qemu-devel] [PATCH for-4.1 v2] q35: Revert to kernel irqchip Alex Williamson
2019-05-15 6:15 ` Peter Xu
2019-05-15 8:42 ` Daniel P. Berrangé
2019-05-15 13:23 ` [Qemu-devel] [PATCH for-4.1 v2] q35: Revert to kernel irqchipQEM Alex Williamson
2019-05-16 2:01 ` Peter Xu
2019-05-29 3:30 ` [Qemu-devel] [PATCH for-4.1 v2] q35: Revert to kernel irqchip Michael S. Tsirkin
2019-05-29 13:43 ` Alex Williamson
2019-05-29 16:01 ` Michael S. Tsirkin
2019-05-31 15:22 ` Alex Williamson
2019-06-03 8:06 ` Paolo Bonzini
2019-06-12 9:01 ` Daniel P. Berrangé [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=20190612090150.GD6897@redhat.com \
--to=berrange@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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.