Re: [PATCH v5 0/3] introduce tee-based EFI Runtime Variable Service

[Ard Biesheuvel]

On Mon, 29 May 2023 at 11:05, Jens Wiklander <jens.wiklander@xxxxxxxxxx> wrote:
>
> On Fri, May 26, 2023 at 3:10 PM Ard Biesheuvel <ardb@xxxxxxxxxx> wrote:
> >
> > On Fri, 26 May 2023 at 03:08, Masahisa Kojima
> > <masahisa.kojima@xxxxxxxxxx> 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.