[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190527150033.GC12745@8bytes.org>
Date: Mon, 27 May 2019 17:00:34 +0200
From: Joerg Roedel <joro@...tes.org>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: David Woodhouse <dwmw2@...radead.org>, ashok.raj@...el.com,
jacob.jun.pan@...el.com, kevin.tian@...el.com,
jamessewart@...sta.com, tmurphy@...sta.com, dima@...sta.com,
sai.praneeth.prakhya@...el.com, iommu@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 00/15] iommu/vt-d: Delegate DMA domain to generic iommu
Hey James, Lu Baolu,
On Sat, May 25, 2019 at 01:41:21PM +0800, Lu Baolu wrote:
> James Sewart (1):
> iommu/vt-d: Implement apply_resv_region iommu ops entry
>
> Lu Baolu (14):
> iommu: Add API to request DMA domain for device
> iommu/vt-d: Expose ISA direct mapping region via
> iommu_get_resv_regions
> iommu/vt-d: Enable DMA remapping after rmrr mapped
> iommu/vt-d: Add device_def_domain_type() helper
> iommu/vt-d: Delegate the identity domain to upper layer
> iommu/vt-d: Delegate the dma domain to upper layer
> iommu/vt-d: Identify default domains replaced with private
> iommu/vt-d: Handle 32bit device with identity default domain
> iommu/vt-d: Probe DMA-capable ACPI name space devices
> iommu/vt-d: Implement is_attach_deferred iommu ops entry
> iommu/vt-d: Cleanup get_valid_domain_for_dev()
> iommu/vt-d: Remove startup parameter from device_def_domain_type()
> iommu/vt-d: Remove duplicated code for device hotplug
> iommu/vt-d: Remove static identity map code
Thanks for working on this. I think it is time to give it some testing
in linux-next, so I applied it to my tree. Fingers crossed this can make
it into v5.3 :)
Regards,
Joerg
Powered by blists - more mailing lists