On Thu, 2 Feb 2023 at 21:42, Dionna Amalie Glaze <dionnagl...@google.com> wrote: > > > > > > > This change is made given a request from Ard. The CC capability is not > > > applied to other system memory ranges that probably should also have > > > that capability, given that it's encrypted and accepted. I haven't > > > considered carefully where EFI_MEMORY_CPU_CRYPTO should be added to > > > conventional memory, given the acceptance happens before DXE > > > initializes. Perhaps > > > CoreConvertResourceDescriptorHobAttributesToCapabilities? This is more > > > of a question to Ard and Thomas. > > > > > > > It's not clear to me whether the CC attribute applies to the host or > > the guest. From the guest PoV, there is really no distinction, whereas > > on the host, I could imagine that only CC capable memory can be used > > for handing out to VMs. > > > > That's a good point. The UEFI spec language is hard to interpret here. > Min or Jiewen, do you have more context on the EFI_MEMORY_CPU_CRYPTO > attribute? >
To keep things moving, I've queued this up (as #4040) with the EFI_MEMORY_CPU_CRYPTO flag dropped. I don't think we need to add it here, given that EDK2 nor Linux ever set or test this flag anywhere else, but if this changes, we can add it back. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#100196): https://edk2.groups.io/g/devel/message/100196 Mute This Topic: https://groups.io/mt/96659595/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
