[Qemu-devel] [PATCH v2 0/2] intel_iommu: misc scalable mode fixes for 4.0

Peter Xu posted 2 patches 5 years ago
Test docker-mingw@fedora passed
Test docker-clang@ubuntu passed
Test checkpatch passed
Test asan passed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20190329061422.7926-1-peterx@redhat.com
Maintainers: Eduardo Habkost <ehabkost@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Marcel Apfelbaum <marcel.apfelbaum@gmail.com>, Richard Henderson <rth@twiddle.net>
hw/i386/intel_iommu.c          | 30 ++++++++++++++++++++++--------
hw/i386/intel_iommu_internal.h |  1 -
hw/i386/trace-events           |  2 +-
include/hw/i386/intel_iommu.h  |  1 -
4 files changed, 23 insertions(+), 11 deletions(-)
[Qemu-devel] [PATCH v2 0/2] intel_iommu: misc scalable mode fixes for 4.0
Posted by Peter Xu 5 years ago
v2:
- patch 2: use "1" instead of "sizeof(bool)" for VMSTATE_UNUSED
  because sizeof(bool) can be >1 depends on definition [Dave]

The first patch is the important one.  It should fix up a migration
issue that Dave reported between 3.1<->4.0.  The second patch is born
only because I noticed it when drafting patch 1 and I think we can
probably do that too together as a fixup to the scalable patchset for
4.0.

Please have a look, thanks.

Peter Xu (2):
  intel_iommu: Fix root_scalable migration breakage
  intel_iommu: Drop extended root field

 hw/i386/intel_iommu.c          | 30 ++++++++++++++++++++++--------
 hw/i386/intel_iommu_internal.h |  1 -
 hw/i386/trace-events           |  2 +-
 include/hw/i386/intel_iommu.h  |  1 -
 4 files changed, 23 insertions(+), 11 deletions(-)

-- 
2.17.1


Re: [Qemu-devel] [PATCH v2 0/2] intel_iommu: misc scalable mode fixes for 4.0
Posted by Peter Xu 5 years ago
On Fri, Mar 29, 2019 at 02:14:20PM +0800, Peter Xu wrote:
> v2:
> - patch 2: use "1" instead of "sizeof(bool)" for VMSTATE_UNUSED
>   because sizeof(bool) can be >1 depends on definition [Dave]
> 
> The first patch is the important one.  It should fix up a migration
> issue that Dave reported between 3.1<->4.0.  The second patch is born
> only because I noticed it when drafting patch 1 and I think we can
> probably do that too together as a fixup to the scalable patchset for
> 4.0.

Ping - just want to make sure this series won't miss 4.0.  Thanks,

-- 
Peter Xu