From: Jeremy Linton <jeremy.linton@arm.com>
To: dan.j.williams@intel.com,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>
Cc: linux-coco@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Steven Price <steven.price@arm.com>,
Gavin Shan <gshan@redhat.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [PATCH] coco: guest: arm64: Update ARM CCA guest driver
Date: Fri, 10 Oct 2025 06:48:32 -0500 [thread overview]
Message-ID: <ed3d71a3-b454-4e9b-97bb-7eb4d0b770ec@arm.com> (raw)
In-Reply-To: <68e86e45599bc_199281005d@dwillia2-mobl4.notmuch>
Hi,
Hi,
On 10/9/25 9:24 PM, dan.j.williams@intel.com wrote:
> Jonathan Cameron wrote:
>> On Thu, 09 Oct 2025 12:43:49 +0530
>> Aneesh Kumar K.V <aneesh.kumar@kernel.org> wrote:
>>
>>> "Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.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.
>
> Does ARM64 not have the equivalent of MODULE_DEVICE_TABLE(x86cpu, ...)?
No, it doesn't. There is a hwcap based method, but that requires
allocating a hwcap.
next prev parent reply other threads:[~2025-10-10 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 13:27 [PATCH] coco: guest: arm64: Update ARM CCA guest driver Aneesh Kumar K.V (Arm)
2025-10-09 7:13 ` Aneesh Kumar K.V
2025-10-09 10:35 ` Jonathan Cameron
2025-10-10 2:24 ` dan.j.williams
2025-10-10 11:48 ` Jeremy Linton [this message]
2025-10-09 10:25 ` Jonathan Cameron
2025-10-10 14:16 ` kernel test robot
2025-10-10 15:23 ` Jeremy Linton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed3d71a3-b454-4e9b-97bb-7eb4d0b770ec@arm.com \
--to=jeremy.linton@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=gshan@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=sami.mujawar@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox