[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 0/6] pc,vhost: fixes
|
From: |
Peter Maydell |
|
Subject: |
Re: [PULL 0/6] pc,vhost: fixes |
|
Date: |
Thu, 3 Dec 2020 11:02:28 +0000 |
On Thu, 3 Dec 2020 at 10:59, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Thu, Dec 03, 2020 at 10:20:03AM +0000, Peter Maydell wrote:
> > On Wed, 2 Dec 2020 at 11:03, Michael S. Tsirkin <mst@redhat.com> wrote:
> > >
> > > 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.
> >
> > Is this only "fixes a guest triggerable assert"?
>
> My understanding is that without the patches a rhel7 guest triggers
> the assert if started with vtd enabled and virtio-net with
> iommu_platform=on.
>
> https://bugs.launchpad.net/qemu/+bug/1885175
Bug reported in June ? Is this a regression since 5.1, or
was it this way in 5.1 as well?
thanks
-- PMM
- [PULL 0/6] pc,vhost: fixes, Michael S. Tsirkin, 2020/12/02
- [PULL 1/6] vhost-user-scsi: Fix memleaks in vus_proc_req(), Michael S. Tsirkin, 2020/12/02
- [PULL 2/6] memory: Rename memory_region_notify_one to memory_region_notify_iommu_one, Michael S. Tsirkin, 2020/12/02
- [PULL 3/6] memory: Add IOMMUTLBEvent, Michael S. Tsirkin, 2020/12/02
- [PULL 4/6] memory: Add IOMMU_NOTIFIER_DEVIOTLB_UNMAP IOMMUTLBNotificationType, Michael S. Tsirkin, 2020/12/02
- [PULL 6/6] memory: Skip bad range assertion if notifier is DEVIOTLB_UNMAP type, Michael S. Tsirkin, 2020/12/02
- [PULL 5/6] intel_iommu: Skip page walking on device iotlb invalidations, Michael S. Tsirkin, 2020/12/02
- Re: [PULL 0/6] pc,vhost: fixes, Peter Maydell, 2020/12/03