[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXGDRDCOgVXAYU2wM1SsT9A20-dxCRqiOu3-FbjGTvWehw@mail.gmail.com>
Date: Mon, 29 May 2023 15:29:03 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Jens Wiklander <jens.wiklander@...aro.org>
Cc: Masahisa Kojima <masahisa.kojima@...aro.org>,
Sumit Garg <sumit.garg@...aro.org>,
linux-kernel@...r.kernel.org, op-tee@...ts.trustedfirmware.org,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH v5 0/3] introduce tee-based EFI Runtime Variable Service
On Mon, 29 May 2023 at 11:05, Jens Wiklander <jens.wiklander@...aro.org> wrote:
>
> On Fri, May 26, 2023 at 3:10 PM Ard Biesheuvel <ardb@...nel.org> wrote:
> >
> > On Fri, 26 May 2023 at 03:08, Masahisa Kojima
> > <masahisa.kojima@...aro.org> wrote:
> > >
> > > This series introduces the tee based EFI Runtime Variable Service.
> > >
> > > The eMMC device is typically owned by the non-secure world(linux in
> > > this case). There is an existing solution utilizing eMMC RPMB partition
> > > for EFI Variables, it is implemented by interacting with
> > > OP-TEE, StandaloneMM(as EFI Variable Service Pseudo TA), eMMC driver
> > > and tee-supplicant. The last piece is the tee-based variable access
> > > driver to interact with OP-TEE and StandaloneMM.
> > >
> > > Changelog:
> > > v4 -> v5
> > > - rebase to efi-next based on v6.4-rc1
> > > - set generic_ops.query_variable_info, it works as expected as follows.
> > > $ df -h /sys/firmware/efi/efivars/
> > > Filesystem Size Used Avail Use% Mounted on
> > > efivarfs 16K 1.3K 15K 8% /sys/firmware/efi/efivars
> >
> > Excellent, thanks a lot for double checking that.
> >
> > Jens, did you have any feedback on this? If not, I intend to queue it
> > up for v6.5
>
> Looks good to me.
>
> Thanks,
> Jens
>
Thanks
I've queued this up now.
Powered by blists - more mailing lists