linux-kernel - Re: [RFC PATCH v2 0/6] powerpc: pSeries: vfio: iommu: Re-enable support for SPAPR TCE VFIO

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]

Message-ID: <703f15b0-d895-4518-9886-0827a6c4e769@amd.com>
Date: Thu, 2 May 2024 11:29:04 +1000
From: Alexey Kardashevskiy <aik@....com>
To: Jason Gunthorpe <jgg@...pe.ca>, Shivaprasad G Bhat <sbhat@...ux.ibm.com>
Cc: mpe@...erman.id.au, tpearson@...torengineering.com,
 alex.williamson@...hat.com, linuxppc-dev@...ts.ozlabs.org,
 npiggin@...il.com, christophe.leroy@...roup.eu, aneesh.kumar@...nel.org,
 naveen.n.rao@...ux.ibm.com, gbatra@...ux.vnet.ibm.com,
 brking@...ux.vnet.ibm.com, aik@...abs.ru, ruscur@...sell.cc,
 robh@...nel.org, linux-kernel@...r.kernel.org, joel@....id.au,
 kvm@...r.kernel.org, msuchanek@...e.de, oohall@...il.com,
 mahesh@...ux.ibm.com, jroedel@...e.de, vaibhav@...ux.ibm.com,
 svaidy@...ux.ibm.com
Subject: Re: [RFC PATCH v2 0/6] powerpc: pSeries: vfio: iommu: Re-enable
 support for SPAPR TCE VFIO



On 2/5/24 00:09, Jason Gunthorpe wrote:
> On Tue, Apr 30, 2024 at 03:05:34PM -0500, Shivaprasad G Bhat wrote:
>> RFC v1 was posted here [1]. As I was testing more and fixing the
>> issues, I realized its clean to have the table_group_ops implemented
>> the way it is done on PowerNV and stop 'borrowing' the DMA windows
>> for pSeries.
>>
>> This patch-set implements the iommu table_group_ops for pSeries for
>> VFIO SPAPR TCE sub-driver thereby enabling the VFIO support on POWER
>> pSeries machines.
> 
> Wait, did they previously not have any support?
 >
> Again, this TCE stuff needs to go away, not grow. I can grudgingly
> accept fixing it where it used to work, but not enabling more HW that
> never worked before! :(


This used to work when I tried last time 2+ years ago, not a new stuff. 
Thanks,


-- 
Alexey