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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BL1PR11MB5271E69F5320258217B5B19A8C042@BL1PR11MB5271.namprd11.prod.outlook.com>
Date: Tue, 17 Dec 2024 07:39:08 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>, Joerg Roedel <joro@...tes.org>, "Will
 Deacon" <will@...nel.org>, Robin Murphy <robin.murphy@....com>, "Jason
 Gunthorpe" <jgg@...pe.ca>, "Liu, Yi L" <yi.l.liu@...el.com>
CC: "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/1] iommu/vt-d: Remove iommu cap audit

> From: Lu Baolu <baolu.lu@...ux.intel.com>
> Sent: Monday, December 16, 2024 3:18 PM
> 
> The capability audit code was introduced by commit <ad3d19029979>
> "iommu/vt-d: Audit IOMMU Capabilities and add helper functions", aiming
> to verify the consistency of capabilities across all IOMMUs for supported
> features.
> 
> Nowadays, all the kAPIs of the iommu subsystem have evolved to be device
> oriented, in preparation for supporting heterogeneous IOMMU architectures.
> There is no longer a need to require capability consistence among IOMMUs
> for any feature.
> 
> Remove the iommu cap audit code to make the driver align with the design
> in the iommu core.
> 
> Signed-off-by: Lu Baolu <baolu.lu@...ux.intel.com>

Reviewed-by: Kevin Tian <kevin.tian@...el.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ