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] [thread-next>] [day] [month] [year] [list]
Date: Fri, 26 Jan 2024 11:17:01 -0400
From: Jason Gunthorpe <jgg@...pe.ca>
To: Shivaprasad G Bhat <sbhat@...ux.ibm.com>
Cc: iommu@...ts.linux.dev, linuxppc-dev@...ts.ozlabs.org,
	linux-kernel@...r.kernel.org, mpe@...erman.id.au, npiggin@...il.com,
	christophe.leroy@...roup.eu, aneesh.kumar@...nel.org,
	naveen.n.rao@...ux.ibm.com, jroedel@...e.de,
	tpearson@...torengineering.com, aik@....com, bgray@...ux.ibm.com,
	gregkh@...uxfoundation.org, gbatra@...ux.vnet.ibm.com,
	vaibhav@...ux.ibm.com
Subject: Re: [PATCH 1/2] powerpc: iommu: Bring back table group
 release_ownership() call

On Fri, Jan 26, 2024 at 08:43:12PM +0530, Shivaprasad G Bhat wrote:
> > Also, is there any chance someone can work on actually fixing this to
> > be a proper iommu driver? I think that will become important for power
> > to use the common dma_iommu code in the next year...
> We are looking into it.

Okay, let me know, I can possibly help make parts of this happen

power is the last still-current architecture to be outside the modern
IOMMU and DMA API design and I'm going to start proposing things that
will not be efficient on power because of this.

I think a basic iommu driver using the dma API would not be so hard.

I don't know what to do about the SPAPR VFIO mess though. :(

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ