[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD8Lp47E2CDmHTEGSpqYfxxKB4a+JY6VzZdL9e65P7YxqfL9Ag@mail.gmail.com>
Date: Wed, 6 May 2020 10:09:37 +0800
From: Daniel Drake <drake@...lessm.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: Joerg Roedel <joro@...tes.org>, "Raj, Ashok" <ashok.raj@...el.com>,
jacob.jun.pan@...ux.intel.com,
"Tian, Kevin" <kevin.tian@...el.com>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
iommu@...ts.linux-foundation.org,
Linux Kernel <linux-kernel@...r.kernel.org>,
Derrick Jonathan <jonathan.derrick@...el.com>,
Jerry Snitselaar <jsnitsel@...hat.com>,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v4 0/3] Replace private domain with per-group default domain
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!
Powered by blists - more mailing lists