From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL 0/6] pc,vhost: fixes
Date: Wed, 2 Dec 2020 06:03:05 -0500 [thread overview]
Message-ID: <20201202101655.122214-1-mst@redhat.com> (raw)
Patch 5 gave me pause but we do need patch 6 as
it's a guest triggerable assert, and it seemed
cleaner to just take the whole patchset than cherry-pick.
The following changes since commit d73c46e4a84e47ffc61b8bf7c378b1383e7316b5:
Update version for v5.2.0-rc4 release (2020-12-01 16:21:01 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream
for you to fetch changes up to a451089140c7b167661d0a23190e6d8bd7eae48d:
memory: Skip bad range assertion if notifier is DEVIOTLB_UNMAP type (2020-12-02 05:14:29 -0500)
----------------------------------------------------------------
pc,vhost: fixes
A couple of last minute bugfixes.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
----------------------------------------------------------------
Alex Chen (1):
vhost-user-scsi: Fix memleaks in vus_proc_req()
Eugenio Pérez (5):
memory: Rename memory_region_notify_one to memory_region_notify_iommu_one
memory: Add IOMMUTLBEvent
memory: Add IOMMU_NOTIFIER_DEVIOTLB_UNMAP IOMMUTLBNotificationType
intel_iommu: Skip page walking on device iotlb invalidations
memory: Skip bad range assertion if notifier is DEVIOTLB_UNMAP type
include/exec/memory.h | 40 ++++++++------
contrib/vhost-user-scsi/vhost-user-scsi.c | 3 +-
hw/arm/smmu-common.c | 13 +++--
hw/arm/smmuv3.c | 13 +++--
hw/i386/intel_iommu.c | 92 ++++++++++++++++++-------------
hw/misc/tz-mpc.c | 32 ++++++-----
hw/ppc/spapr_iommu.c | 15 ++---
hw/s390x/s390-pci-inst.c | 27 +++++----
hw/virtio/vhost.c | 2 +-
hw/virtio/virtio-iommu.c | 30 +++++-----
softmmu/memory.c | 29 ++++++----
11 files changed, 167 insertions(+), 129 deletions(-)
next reply other threads:[~2020-12-02 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 11:03 Michael S. Tsirkin [this message]
2020-12-02 11:03 ` [PULL 1/6] vhost-user-scsi: Fix memleaks in vus_proc_req() Michael S. Tsirkin
2020-12-02 11:03 ` [PULL 2/6] memory: Rename memory_region_notify_one to memory_region_notify_iommu_one Michael S. Tsirkin
2020-12-02 11:03 ` [PULL 3/6] memory: Add IOMMUTLBEvent Michael S. Tsirkin
2020-12-02 11:03 ` [PULL 4/6] memory: Add IOMMU_NOTIFIER_DEVIOTLB_UNMAP IOMMUTLBNotificationType Michael S. Tsirkin
2020-12-02 11:03 ` [PULL 5/6] intel_iommu: Skip page walking on device iotlb invalidations Michael S. Tsirkin
2020-12-02 11:03 ` [PULL 6/6] memory: Skip bad range assertion if notifier is DEVIOTLB_UNMAP type Michael S. Tsirkin
2020-12-03 10:20 ` [PULL 0/6] pc,vhost: fixes Peter Maydell
2020-12-03 10:58 ` Michael S. Tsirkin
2020-12-03 11:02 ` Peter Maydell
2020-12-03 11:57 ` Peter Maydell
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=20201202101655.122214-1-mst@redhat.com \
--to=mst@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).