On Mon, Dec 04, 2023 at 11:57:43AM +0100, Ard Biesheuvel wrote:
> On Mon, Dec 4, 2023 at 11:53 AM Gerd Hoffmann <kra...@redhat.com> wrote:
> >
> > > So let's introduce a QEMU command line option to indicate that the
> > > protocol should not be exposed at all.
> > >
> > > -fw_cfg opt/org.tianocore/DisableMemAttrProtocol,string=y
> >
> > Can we name this 'MemAttrProtocol={y,n}' so it works both ways (enabling
> > and disabling) without double negative?
> >
>
> Sure, but with the same behavior, right?
>
> =y means it will get installed
> =n means it will get installed and uninstalled again
>
> > The fedora distro builds have the protocol disabled, and I'll keep it
> > that way until we finally have fixed shim.efi builds. Having the option
> > to enable this would be nice though.
> >
>
> So how did you disable the protocol? That part is not upstream afaik.
Yes, right now it's a fedora-specific patch. Which I'd drop in favor of
this patch, or a slightly modified version of it.
> We can disable the protocol via this method but how would you set it
> to =n by default?
if (Status != EFI_SUCCESS)
// opt/org.tiabocode/MemAttrProtocol not present on the qemu cmdline
MemAttrProtocol = ThisBuildsDefault
}
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112036): https://edk2.groups.io/g/devel/message/112036
Mute This Topic: https://groups.io/mt/102967690/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
