On Tue, May 11, 2021 at 2:17 AM Kaneda, Erik <erik.kaneda@xxxxxxxxx> wrote: > > > > > -----Original Message----- > > From: Rafael J. Wysocki <rafael@xxxxxxxxxx> > > Sent: Monday, May 10, 2021 9:58 AM > > To: Kuppuswamy Sathyanarayanan > > <sathyanarayanan.kuppuswamy@xxxxxxxxxxxxxxx>; Kaneda, Erik > > <erik.kaneda@xxxxxxxxx> > > Cc: Rafael J Wysocki <rjw@xxxxxxxxxxxxx>; Len Brown <lenb@xxxxxxxxxx>; > > Moore, Robert <robert.moore@xxxxxxxxx>; ACPI Devel Maling List <linux- > > acpi@xxxxxxxxxxxxxxx>; open list:ACPI COMPONENT ARCHITECTURE > > (ACPICA) <devel@xxxxxxxxxx>; Linux Kernel Mailing List <linux- > > kernel@xxxxxxxxxxxxxxx>; Wysocki, Rafael J <rafael.j.wysocki@xxxxxxxxx> > > Subject: Re: [PATCH 1/1] ACPICA: Add SVKL table headers > > > > On Thu, Apr 22, 2021 at 9:29 PM Kuppuswamy Sathyanarayanan > > <sathyanarayanan.kuppuswamy@xxxxxxxxxxxxxxx> wrote: > > > > > > ACPICA commit b5e6bcf69dbb9877481992d5ce86008cfb94f5b8 > > > > > > SVKL (Storage Volume Key Location Table) is used by BIOS/Firmware > > > to share storage volume encryption key's with OS. It will be used > > > by userspace to decrypt and mount encrypted drives. > > > > > > So add SVKL table signature and add it to known signatures array > > > support SVKL. > > > > > > You can find details about the SVKL table in TDX specfication > > > titled "Guest-Host-Communication Interface (GHCI) for Intel > > > Trust Domain Extensions (Intel® TDX)", sec 4.4 and in ACPI > > > specification r6.4, sec 5.2.6. > > > > > > > > https://software.intel.com/content/dam/develop/external/us/en/documen > > ts/intel-tdx-guest-hypervisor-communication-interface.pdf > > > > > > Cc: Robert Moore <robert.moore@xxxxxxxxx> > > > Cc: Erik Kaneda <erik.kaneda@xxxxxxxxx> > > > Cc: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > > > > > Link: https://github.com/acpica/acpica/commit/b5e6bcf6 > > > Signed-off-by: Kuppuswamy Sathyanarayanan > > <sathyanarayanan.kuppuswamy@xxxxxxxxxxxxxxx> > > > Signed-off-by: Bob Moore <robert.moore@xxxxxxxxx> > > > Signed-off-by: Erik Kaneda <erik.kaneda@xxxxxxxxx> > > > > Erik, what's the plan regarding this patch and the other ACPICA change > > requisite for this series? > > > > Are they going to be part of the next ACPICA release and am I going to > > receive them the usual way? > > Yes, we'll do this the usual way OK, thanks!
