[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cd0f526c-da68-ef59-580f-665ad08a395f@linux.intel.com>
Date: Wed, 11 Mar 2020 14:50:39 +0800
From: Lu Baolu <baolu.lu@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>
Cc: baolu.lu@...ux.intel.com, ashok.raj@...el.com,
jacob.jun.pan@...ux.intel.com, kevin.tian@...el.com,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Daniel Drake <drake@...lessm.com>,
Derrick Jonathan <jonathan.derrick@...el.com>,
Jerry Snitselaar <jsnitsel@...hat.com>,
Robin Murphy <robin.murphy@....com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH 0/6] Replace private domain with per-group default
Hi Joerg,
On 2020/3/10 19:15, Joerg Roedel wrote:
> Hi Baolu,
>
> On Sat, Mar 07, 2020 at 02:20:08PM +0800, Lu Baolu wrote:
>> Lu Baolu (5):
>> iommu: Configure default domain with dev_def_domain_type
>> iommu/vt-d: Don't force 32bit devices to uses DMA domain
>> iommu/vt-d: Don't force PCI sub-hierarchy to use DMA domain
>> iommu/vt-d: Add dev_def_domain_type callback
>> iommu/vt-d: Apply per-device dma_ops
>>
>> Sai Praneeth Prakhya (1):
>> iommu: Add dev_def_domain_type() callback in iommu_ops
>
> I like this patch-set, but I fear some regressions from patch
> "iommu/vt-d: Don't force 32bit devices to uses DMA domain". Have you
> tested this series on a couple of machines, ideally even older ones from
> the first generation of VT-d hardware?
The oldest hardware I have is Ivy Bridge. :-) Actually, The effect of
using identity domain for 32-bit devices is the same as that of adding
intel_iommu=off in the kernel parameter. Hence, if there is any
regression, people should also find it with intel_iommu=off.
intel_iommu=off support is added at the very beginning of VT-d driver.
Best regards,
baolu
Powered by blists - more mailing lists