From: Jason Gunthorpe <jgg@nvidia.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
linux-coco@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will@kernel.org>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v9 1/7] firmware: smccc: Add an Arm SMCCC bus
Date: Fri, 4 Sep 2026 14:50:13 -0300 [thread overview]
Message-ID: <20260904175013.GW4157646@nvidia.com> (raw)
In-Reply-To: <20260904-imperial-partridge-of-atheism-bafcb3@sudeepholla>
On Fri, Sep 04, 2026 at 03:27:27PM +0100, Sudeep Holla wrote:
> > IMHO to lean into the bus design I would have a discovery SMCCC that
> > returns a list of supported ABIs, something like (spec, spec version,
> > ABI, FID, feature supported bitmap). There could be overlaps if the
> > FW supports several ABI incompatible versions, like RSI v1 and RSI v2.
> >
>
> But then we will have to wait for that discovery SMCCC ABI first and that
> mean how will it work on existing deployed systems ? But I like the idea.
Oh, I wasn't saying to wait for anything. This is good enough as is.
I was suggesting a next step to make this even better and solve some
of the real problem the ecosystem feels with the FW/kernel ABI.
> the software that purely relies on feature bits. So a big yes for that
> idea and I think some specs and in some form are doing it. I can't
> recall specific but I have seen it. We just need push only for that
> in future specs.
I was advocating the approach of a discovery spec that codifies
exactly how all this should work. So each team writing a new spec
doesn't have to reinvent it.
Jason
next prev parent reply other threads:[~2026-09-04 17:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 6:32 [PATCH v9 0/7] Switch Arm SMCCC firmware services to an SMCCC bus Aneesh Kumar K.V (Arm)
2026-08-05 6:32 ` [PATCH v9 1/7] firmware: smccc: Add an Arm " Aneesh Kumar K.V (Arm)
2026-08-28 19:34 ` Jason Gunthorpe
2026-09-03 8:52 ` Aneesh Kumar K.V
2026-09-03 12:57 ` Jason Gunthorpe
2026-09-03 14:13 ` Sudeep Holla
2026-09-03 14:29 ` Jason Gunthorpe
2026-09-03 14:35 ` Aneesh Kumar K.V
2026-09-03 15:46 ` Jason Gunthorpe
2026-09-03 16:18 ` Sudeep Holla
2026-09-03 18:21 ` Jason Gunthorpe
2026-09-04 5:50 ` Aneesh Kumar K.V
2026-09-04 10:02 ` Sudeep Holla
2026-09-04 13:53 ` Jason Gunthorpe
2026-09-04 14:27 ` Sudeep Holla
2026-09-04 17:50 ` Jason Gunthorpe [this message]
2026-08-05 6:32 ` [PATCH v9 2/7] firmware: hwrng: arm_smccc_trng: Register as an SMCCC device Aneesh Kumar K.V (Arm)
2026-08-05 11:08 ` Catalin Marinas
2026-08-28 19:34 ` Jason Gunthorpe
2026-08-29 5:54 ` Aneesh Kumar K.V
2026-08-29 19:11 ` Jason Gunthorpe
2026-08-05 6:32 ` [PATCH v9 3/7] firmware: arm_rmm: Move RSI support out of arch/arm64 Aneesh Kumar K.V (Arm)
2026-08-05 11:21 ` Catalin Marinas
2026-08-05 13:05 ` Aneesh Kumar K.V
2026-08-10 10:03 ` Suzuki K Poulose
2026-08-28 19:34 ` Jason Gunthorpe
2026-08-29 5:58 ` Aneesh Kumar K.V
2026-08-05 6:32 ` [PATCH v9 4/7] arm64: realm: Move Realm memory encryption ops to RSI code Aneesh Kumar K.V (Arm)
2026-08-10 10:12 ` Suzuki K Poulose
2026-08-10 12:15 ` Aneesh Kumar K.V
2026-08-05 6:32 ` [PATCH v9 5/7] virt: coco: arm-cca-guest: Rename TSM report source file Aneesh Kumar K.V (Arm)
2026-08-28 19:34 ` Jason Gunthorpe
2026-08-29 6:02 ` Aneesh Kumar K.V
2026-08-29 19:07 ` Jason Gunthorpe
2026-08-05 6:32 ` [PATCH v9 6/7] firmware: smccc: arm-cca-guest: Bind the TSM provider to an SMCCC device Aneesh Kumar K.V (Arm)
2026-08-28 19:34 ` Jason Gunthorpe
2026-08-29 6:12 ` Aneesh Kumar K.V
2026-08-29 19:13 ` Jason Gunthorpe
2026-08-05 6:32 ` [PATCH v9 7/7] coco: guest: arm64: Replace dummy CCA device with sysfs ABI Aneesh Kumar K.V (Arm)
2026-08-28 19:34 ` Jason Gunthorpe
2026-08-05 9:51 ` [PATCH v9 0/7] Switch Arm SMCCC firmware services to an SMCCC bus Catalin Marinas
2026-08-05 12:22 ` Aneesh Kumar K.V
2026-08-10 9:35 ` Aneesh Kumar K.V
2026-08-10 10:24 ` Will Deacon
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=20260904175013.GW4157646@nvidia.com \
--to=jgg@nvidia.com \
--cc=Suzuki.Poulose@arm.com \
--cc=andre.przywara@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.linton@arm.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@kernel.org \
--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