[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d0fa0782473f5c7ef63dcded596ab6694b74b149.camel@intel.com>
Date: Wed, 6 May 2020 17:50:48 +0000
From: "Derrick, Jonathan" <jonathan.derrick@...el.com>
To: "baolu.lu@...ux.intel.com" <baolu.lu@...ux.intel.com>,
"drake@...lessm.com" <drake@...lessm.com>
CC: "robin.murphy@....com" <robin.murphy@....com>,
"joro@...tes.org" <joro@...tes.org>, "hch@....de" <hch@....de>,
"jacob.jun.pan@...ux.intel.com" <jacob.jun.pan@...ux.intel.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"Raj, Ashok" <ashok.raj@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jsnitsel@...hat.com" <jsnitsel@...hat.com>,
"Prakhya, Sai Praneeth" <sai.praneeth.prakhya@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>
Subject: Re: [PATCH v4 0/3] Replace private domain with per-group default
domain
On Wed, 2020-05-06 at 10:09 +0800, Daniel Drake wrote:
> On Wed, May 6, 2020 at 10:03 AM Lu Baolu <baolu.lu@...ux.intel.com> wrote:
> > https://lkml.org/lkml/2020/4/14/616
> > [This has been applied in iommu/next.]
> >
> > Hence, there is no need to keep the private domain implementation
> > in the Intel IOMMU driver. This patch series aims to remove it.
>
> I applied these patches on top of Joerg's branch and confirmed that
> they fix the issue discussed in the thread:
>
> [PATCH v2] iommu/vt-d: consider real PCI device when checking if
> mapping is needed
> (the patch there is no longer needed)
>
> Tested-by: Daniel Drake <drake@...lessm.com>
>
> Thanks!
Looks like the key to the real DMA dev fix was removing
identity_mapping() paths that led to dev->archdata.iommu == NULL -> DMA
domain
Works great for me as well
Reviewed-by: Jon Derrick <jonathan.derrick@...el.com>
Powered by blists - more mailing lists