On Tue, Sep 10, 2019 at 04:53:23PM +0200, Joerg Roedel wrote:
> On Fri, Sep 06, 2019 at 02:14:47PM +0800, Lu Baolu wrote:
> > Lu Baolu (5):
> > swiotlb: Split size parameter to map/unmap APIs
> > iommu/vt-d: Check whether device requires bounce buffer
> > iommu/vt-d: Don't switch off swiotlb if bounce page is used
> > iommu/vt-d: Add trace events for device dma map/unmap
> > iommu/vt-d: Use bounce buffer for untrusted devices
> >
> > .../admin-guide/kernel-parameters.txt | 5 +
> > drivers/iommu/Kconfig | 1 +
> > drivers/iommu/Makefile| 1 +
> > drivers/iommu/intel-iommu.c | 310 +-
> > drivers/iommu/intel-trace.c | 14 +
> > drivers/xen/swiotlb-xen.c | 8 +-
> > include/linux/swiotlb.h | 8 +-
> > include/trace/events/intel_iommu.h| 106 ++
> > kernel/dma/direct.c | 2 +-
> > kernel/dma/swiotlb.c | 30 +-
> > 10 files changed, 449 insertions(+), 36 deletions(-)
> > create mode 100644 drivers/iommu/intel-trace.c
> > create mode 100644 include/trace/events/intel_iommu.h
>
> Applied, thanks.
Please un-apply the swiotlb until the WARN_ON gets fixed. Or alternatively
squash the fix once that is done.
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
