From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>, Kevin Wolf <kwolf@redhat.com>,
Hanna Reitz <hreitz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcelo Tosatti <mtosatti@redhat.com>,
xen-devel@lists.xenproject.org, qemu-block@nongnu.org,
kvm@vger.kernel.org
Subject: [PULL 0/7] xenfv-stable queue
Date: Mon, 6 Nov 2023 10:39:48 +0000 [thread overview]
Message-ID: <20231106103955.200867-1-dwmw2@infradead.org> (raw)
The following changes since commit d762bf97931b58839316b68a570eecc6143c9e3e:
Merge tag 'pull-target-arm-20231102' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2023-11-03 10:04:12 +0800)
are available in the Git repository at:
git://git.infradead.org/users/dwmw2/qemu.git tags/pull-xenfv-stable-20231106
for you to fetch changes up to a1c1082908dde4867b1ac55f546bea0c17d52318:
hw/xen: use correct default protocol for xen-block on x86 (2023-11-06 10:03:45 +0000)
----------------------------------------------------------------
Bugfixes for emulated Xen support
Selected bugfixes for mainline and stable, especially to the per-vCPU
local APIC vector delivery mode for event channel notifications, which
was broken in a number of ways.
The xen-block driver has been defaulting to the wrong protocol for x86
guest, and this fixes that — which is technically an incompatible change
but I'm fairly sure nobody relies on the broken behaviour (and in
production I *have* seen guests which rely on the correct behaviour,
which now matches the blkback driver in the Linux kernel).
A handful of other simple fixes for issues which came to light as new
features (qv) were being developed.
----------------------------------------------------------------
David Woodhouse (7):
i386/xen: Don't advertise XENFEAT_supervisor_mode_kernel
i386/xen: fix per-vCPU upcall vector for Xen emulation
hw/xen: select kernel mode for per-vCPU event channel upcall vector
hw/xen: don't clear map_track[] in xen_gnttab_reset()
hw/xen: fix XenStore watch delivery to guest
hw/xen: take iothread mutex in xen_evtchn_reset_op()
hw/xen: use correct default protocol for xen-block on x86
hw/block/xen-block.c | 10 +++++++---
hw/i386/kvm/xen_evtchn.c | 7 +++++++
hw/i386/kvm/xen_gnttab.c | 2 --
hw/i386/kvm/xen_xenstore.c | 8 +++++---
include/sysemu/kvm_xen.h | 1 +
target/i386/kvm/xen-emu.c | 16 +++++++++++-----
6 files changed, 31 insertions(+), 13 deletions(-)
next reply other threads:[~2023-11-06 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:39 David Woodhouse [this message]
2023-11-06 10:39 ` [PULL 1/7] i386/xen: Don't advertise XENFEAT_supervisor_mode_kernel David Woodhouse
2023-11-06 10:39 ` [PULL 2/7] i386/xen: fix per-vCPU upcall vector for Xen emulation David Woodhouse
2023-11-06 10:39 ` [PULL 3/7] hw/xen: select kernel mode for per-vCPU event channel upcall vector David Woodhouse
2023-11-06 10:39 ` [PULL 4/7] hw/xen: don't clear map_track[] in xen_gnttab_reset() David Woodhouse
2023-11-06 10:39 ` [PULL 5/7] hw/xen: fix XenStore watch delivery to guest David Woodhouse
2023-11-06 10:39 ` [PULL 6/7] hw/xen: take iothread mutex in xen_evtchn_reset_op() David Woodhouse
2023-11-06 10:39 ` [PULL 7/7] hw/xen: use correct default protocol for xen-block on x86 David Woodhouse
2023-11-07 3:01 ` [PULL 0/7] xenfv-stable queue Stefan Hajnoczi
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=20231106103955.200867-1-dwmw2@infradead.org \
--to=dwmw2@infradead.org \
--cc=anthony.perard@citrix.com \
--cc=eduardo@habkost.net \
--cc=hreitz@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).