linux-kernel - Re: [PATCH] coco: guest: arm64: Update ARM CCA guest driver

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: <20251009113557.000053e6@huawei.com>
Date: Thu, 9 Oct 2025 11:35:57 +0100
From: Jonathan Cameron <jonathan.cameron@...wei.com>
To: Aneesh Kumar K.V <aneesh.kumar@...nel.org>
CC: <linux-coco@...ts.linux.dev>, <linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will@...nel.org>, Steven Price <steven.price@....com>, "Gavin
 Shan" <gshan@...hat.com>, Suzuki K Poulose <suzuki.poulose@....com>, "Jeremy
 Linton" <jeremy.linton@....com>, Sami Mujawar <sami.mujawar@....com>
Subject: Re: [PATCH] coco: guest: arm64: Update ARM CCA guest driver

On Thu, 09 Oct 2025 12:43:49 +0530
Aneesh Kumar K.V <aneesh.kumar@...nel.org> wrote:

> "Aneesh Kumar K.V (Arm)" <aneesh.kumar@...nel.org> writes:
> 
> > Make preparatory updates to the ARM CCA guest driver:
> >
> >  - Switch from using a platform device to a faux device (based on
> >    feedback in [1])
> >  - Rename the device from `arm-cca-dev` to `arm-rsi-dev`, so that the
> >    host driver can register an equivalent `arm-rmi-dev`
> >
> > These changes are purely structural and introduce no new functionality.
> > Subsequent patches will extend this driver to add guest device
> > assignment support.
> >
> > [1] https://lore.kernel.org/all/2025073035-bulginess-rematch-b92e@gregkh
> >  
> 
> I noticed that, this will break autoloading of the driver. 

Ah indeed.  You'd need to arrange for the arch code to call the init()
directly (possibly arch_initcall() as before or maybe directly from
arm64_rsi_init), which makes it tricky to do in a module as there
is nothing to kick off module autoloading. You could kick that off
explicitly but that's a bit ugly.

Jonathan