lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Mar 2020 12:15:03 +0100 From: Joerg Roedel <joro@...tes.org> To: Lu Baolu <baolu.lu@...ux.intel.com> Cc: 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 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? Regards, Joerg
Powered by blists - more mailing lists