From: Jason Gunthorpe <jgg@ziepe.ca>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Steven Price <steven.price@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Jiri Pirko <jiri@resnulli.us>, GONG Ruiqi <gongruiqi1@huawei.com>
Subject: Re: [PATCH RFC 0/3] firmware: arm_firme: introduce FIRME support for host attestation
Date: Tue, 20 Oct 2026 15:47:37 -0300 [thread overview]
Message-ID: <20261020184737.GS14213@ziepe.ca> (raw)
In-Reply-To: <atefXz-0cD9viNHK@e129823.arm.com>
On Tue, Oct 20, 2026 at 06:05:35PM +0100, Yeoreum Yun wrote:
> >
> > > If we implments this with library, are you thinking that file should
> > > be located at driver/firmware/arm_firme or other place? though we make it
> > > with library, I still think it should be located at
> > > driver/firmware/arm_firme or some place in arch/arm64, but as
> > > perspective abstraction to mange firme helpers in one place,
> > > I think this design seems good.
> >
> > Will has indicated a preference for driver/firwmare
>
> Okay. with this let me make a driver/firmware/arm_firme as library not
> a module format and make this library APIs (base, attestation) to be used
> attestation and other. This means device / driver registeration with
> smccc and done in driver/attestation/provider but use the APIs from
> /driver/firmware/arm_firme.
You should try to structure it with a firme headerfile, and some
inline helpers to invoke the smcs and then a very small set of out of
line functions that *are used by multiple firme drivers*.
Don't put attestation in driver/firmware/arm_firme..
You can look at what I did for DRTM for some inspiration
https://lore.kernel.org/all/11-v2-989a18390eb1+486-arm64_drtm_jgg@nvidia.com/
After some feedback from Jonathon I think it turned out fairly well.
Jason
prev parent reply other threads:[~2026-10-20 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:14 Yeoreum Yun
2026-10-19 14:14 ` [PATCH RFC 1/3] firmware: arm_firme: introduce arm_firme driver Yeoreum Yun
2026-10-19 14:14 ` [PATCH RFC 2/3] firmware: arm-smccc: add FIRME device Yeoreum Yun
2026-10-19 14:14 ` [PATCH RFC 3/3] firmware: arm-firme: TSM_REPORT support using FIRME Yeoreum Yun
2026-10-19 23:35 ` [PATCH RFC 0/3] firmware: arm_firme: introduce FIRME support for host attestation Jason Gunthorpe
2026-10-20 7:13 ` Yeoreum Yun
2026-10-20 12:45 ` Jason Gunthorpe
2026-10-20 13:41 ` Yeoreum Yun
2026-10-20 13:50 ` Jason Gunthorpe
2026-10-20 14:13 ` Yeoreum Yun
2026-10-20 14:36 ` Jason Gunthorpe
2026-10-20 14:43 ` Yeoreum Yun
2026-10-20 14:58 ` Jason Gunthorpe
2026-10-20 15:18 ` Yeoreum Yun
2026-10-20 16:47 ` Jason Gunthorpe
2026-10-20 17:05 ` Yeoreum Yun
2026-10-20 18:47 ` Jason Gunthorpe [this message]
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=20261020184737.GS14213@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gongruiqi1@huawei.com \
--cc=jiri@resnulli.us \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=sami.mujawar@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=yeoreum.yun@arm.com \
/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
all inboxes | Powered by JetHome®