linux-kernel - Re: [RFC PATCH v1 11/38] KVM: arm64: CCA: register host tsm platform device

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: <2025101516-handbook-hyphen-62ec@gregkh>
Date: Wed, 15 Oct 2025 14:37:57 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@...nel.org>,
	Jeremy Linton <jeremy.linton@....com>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Dan Williams <dan.j.williams@...el.com>, linux-coco@...ts.linux.dev,
	kvmarm@...ts.linux.dev, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, aik@....com, lukas@...ner.de,
	Samuel Ortiz <sameo@...osinc.com>,
	Xu Yilun <yilun.xu@...ux.intel.com>,
	Suzuki K Poulose <Suzuki.Poulose@....com>,
	Steven Price <steven.price@....com>,
	Catalin Marinas <catalin.marinas@....com>,
	Marc Zyngier <maz@...nel.org>, Will Deacon <will@...nel.org>,
	Oliver Upton <oliver.upton@...ux.dev>
Subject: Re: [RFC PATCH v1 11/38] KVM: arm64: CCA: register host tsm platform
 device

On Wed, Oct 15, 2025 at 09:15:33AM -0300, Jason Gunthorpe wrote:
> On Wed, Oct 15, 2025 at 01:57:38PM +0200, Greg KH wrote:
> 
> > If this really is a firmware thing, and you have a firmware device, then
> > I am confused why this was even brought up at all?  Use a real platform
> > device, with the resources that are needed to talk to this platform
> > device and you should be fine.
> 
> I think the issue today is the PSCI does not always get a
> platform_device, fixing that seems straightforward then all the
> downstream things can switch from using more platform devices to using
> an aux device with the PSCI as the parent..

Great, fix that up and it should get much easier.

> > BUT, if you are making child devices that are NOT actually talking to
> > the firmware,
> 
> This thread is about how to bind various subsystems to this shared
> firmware interface.

Great, use the platform device that the firmware created for you!

thanks,

greg k-h