|
[PATCH v1 0/5] Dot graph generator for PPTT
This series adds functionality to print a dot graph of a PPTT table.
This helps with understanding and debugging PPTT tables.
The dot graph generator functionality is generic and could be used
This series adds functionality to print a dot graph of a PPTT table.
This helps with understanding and debugging PPTT tables.
The dot graph generator functionality is generic and could be used
|
By
Joey Gouly
·
#74808
·
|
|
[PATCH v1 5/5] ShellPkg: add PPTT dot file genration
From: Marc Moisson-Franckhauser <marc.moisson-franckhauser@...>
Bugzilla: 3378 (https://bugzilla.tianocore.org/show_bug.cgi?id=3378)
This generates a dot file from the PPTT table that can be
From: Marc Moisson-Franckhauser <marc.moisson-franckhauser@...>
Bugzilla: 3378 (https://bugzilla.tianocore.org/show_bug.cgi?id=3378)
This generates a dot file from the PPTT table that can be
|
By
Joey Gouly
·
#74807
·
|
|
TianoCore Community Meeting - APAC/NAMO - Thu, 05/06/2021 7:30pm-8:30pm
#cal-reminder
Reminder: TianoCore Community Meeting - APAC/NAMO
When: Thursday, 6 May 2021, 7:30pm to 8:30pm, (GMT-07:00) America/Los
Reminder: TianoCore Community Meeting - APAC/NAMO
When: Thursday, 6 May 2021, 7:30pm to 8:30pm, (GMT-07:00) America/Los
|
By
devel@edk2.groups.io Calendar <devel@...>
·
#74806
·
|
|
TianoCore Community Meeting - APAC/NAMO - Thu, 05/06/2021 7:30pm-8:30pm
#cal-reminder
Reminder: TianoCore Community Meeting - APAC/NAMO
When: Thursday, 6 May 2021, 7:30pm to 8:30pm, (GMT-07:00) America/Los
Reminder: TianoCore Community Meeting - APAC/NAMO
When: Thursday, 6 May 2021, 7:30pm to 8:30pm, (GMT-07:00) America/Los
|
By
devel@edk2.groups.io Calendar <devel@...>
·
#74805
·
|
|
Re: [PATCH 2/3] MdePkg: Refactor BaseRngLib to support AARCH64 in addition to X86
I've updated both the x86 and aarch64 code to add checks that the RDRAND and RNDR instructions are supported before trying to use them in GetRandomNumber[16,32,64,128].
However, it causes the X64
I've updated both the x86 and aarch64 code to add checks that the RDRAND and RNDR instructions are supported before trying to use them in GetRandomNumber[16,32,64,128].
However, it causes the X64
|
By
Rebecca Cran <rebecca@...>
·
#74804
·
|
|
Re: [PATCH RFC v2 07/28] OvmfPkg: Use MemEncryptSevClearMmioPageEncMask() to clear EncMask from Mmio
Noted.
I guess Tom's patches were not accepted when I rebased the the SNP
patches. Will pick those changes in next rev.
Noted.
I guess Tom's patches were not accepted when I rebased the the SNP
patches. Will pick those changes in next rev.
|
By
Brijesh Singh
·
#74803
·
|
|
Re: [PATCH RFC v2 06/28] OvmfPkg/BaseMemEncryptSevLib: Introduce MemEncryptSevClearMmioPageEncMask()
Thanks Laszlo, I will go through the feedback on this patch and address
them in next rev.
-Brijesh
Thanks Laszlo, I will go through the feedback on this patch and address
them in next rev.
-Brijesh
|
By
Brijesh Singh
·
#74802
·
|
|
Re: [PATCH RFC v2 11/28] OvmfPkg: Reserve Secrets page in MEMFD
[...]
It mirrors the TPM boot log behaviour: the log is stored in boot time
only memory, so the kernel EFI stub has to copy it out. The reason the
TPM boot log behaves this way is that if the kernel
[...]
It mirrors the TPM boot log behaviour: the log is stored in boot time
only memory, so the kernel EFI stub has to copy it out. The reason the
TPM boot log behaves this way is that if the kernel
|
By
James Bottomley
·
#74801
·
|
|
Re: [PATCH RFC v2 11/28] OvmfPkg: Reserve Secrets page in MEMFD
[...]
That's right: originally the design was not to have the boot secrets
survive boot because they should already be copied into their correct,
and presumably protected, locations by the time exit
[...]
That's right: originally the design was not to have the boot secrets
survive boot because they should already be copied into their correct,
and presumably protected, locations by the time exit
|
By
James Bottomley
·
#74800
·
|
|
TianoCore Community Meeting - EMEA / NAMO - Thu, 05/06/2021 9:00am-10:00am
#cal-reminder
Reminder: TianoCore Community Meeting - EMEA / NAMO
When: Thursday, 6 May 2021, 9:00am to 10:00am, (GMT-07:00) America/Los
Reminder: TianoCore Community Meeting - EMEA / NAMO
When: Thursday, 6 May 2021, 9:00am to 10:00am, (GMT-07:00) America/Los
|
By
devel@edk2.groups.io Calendar <devel@...>
·
#74799
·
|
|
TianoCore Community Meeting - EMEA / NAMO - Thu, 05/06/2021 9:00am-10:00am
#cal-reminder
Reminder: TianoCore Community Meeting - EMEA / NAMO
When: Thursday, 6 May 2021, 9:00am to 10:00am, (GMT-07:00) America/Los
Reminder: TianoCore Community Meeting - EMEA / NAMO
When: Thursday, 6 May 2021, 9:00am to 10:00am, (GMT-07:00) America/Los
|
By
devel@edk2.groups.io Calendar <devel@...>
·
#74798
·
|
|
Re: [PATCH RFC v2 11/28] OvmfPkg: Reserve Secrets page in MEMFD
Hi Dov,
What you describe (= runtime guest OS access) seems to justify changing
the memory type of this allocation. However, that update doesn't look
tied to SEV-SNP -- it's basically a "change of
Hi Dov,
What you describe (= runtime guest OS access) seems to justify changing
the memory type of this allocation. However, that update doesn't look
tied to SEV-SNP -- it's basically a "change of
|
By
Laszlo Ersek
·
#74797
·
|
|
Re: [PATCH RFC v2 09/28] OvmfPkg/VmgExitLib: Allow PMBASE register access in Dxe phase
Actually, I've changed my mind, regarding the squashing.
Patch#21 is already large, and the module-scope PciLib override requires
a fair bit of justification (commit message, 5 DSC files modified
Actually, I've changed my mind, regarding the squashing.
Patch#21 is already large, and the module-scope PciLib override requires
a fair bit of justification (commit message, 5 DSC files modified
|
By
Laszlo Ersek
·
#74796
·
|
|
Re: [PATCH RFC v2 09/28] OvmfPkg/VmgExitLib: Allow PMBASE register access in Dxe phase
The above explanation is inexact. There are several typos ("APIC" is
incorrect, "ACPI" would be correct, for the TimerLib instance in
question), but that's really just a side observation.
The precise
The above explanation is inexact. There are several typos ("APIC" is
incorrect, "ACPI" would be correct, for the TimerLib instance in
question), but that's really just a side observation.
The precise
|
By
Laszlo Ersek
·
#74795
·
|
|
Re: [PATCH RFC v2 08/28] OvmfPkg/BaseMemEncryptSevLib: Remove CacheFlush parameter
The subject and the commit message body refer to "CacheFlush", but the
parameter (at the library class level) is actually called "Flush".
(1) Please update the subject and the commit message
The subject and the commit message body refer to "CacheFlush", but the
parameter (at the library class level) is actually called "Flush".
(1) Please update the subject and the commit message
|
By
Laszlo Ersek
·
#74794
·
|
|
Re: [PATCH RFC v2 11/28] OvmfPkg: Reserve Secrets page in MEMFD
The first use of the secret area was to hold the guest luks disk passphrase; this is used in the grub-inside-OVMF (AmdSev package), and there was no need to keep that page around for the guest
The first use of the secret area was to hold the guest luks disk passphrase; this is used in the grub-inside-OVMF (AmdSev package), and there was no need to keep that page around for the guest
|
By
Dov Murik <dovmurik@...>
·
#74793
·
|
|
Re: [PATCH RFC v2 07/28] OvmfPkg: Use MemEncryptSevClearMmioPageEncMask() to clear EncMask from Mmio
The contents of this patch are sound, but they are incomplete, and
incorrectly structured too.
(1) Please provide a separate patch for each modified module.
(2) You missed the
The contents of this patch are sound, but they are incomplete, and
incorrectly structured too.
(1) Please provide a separate patch for each modified module.
(2) You missed the
|
By
Laszlo Ersek
·
#74792
·
|
|
[PATCH v1 1/1] ArmPkg: Update SCMI Base Protocol version to 0x20000
From: Nicola Mazzucato <nicola.mazzucato@...>
The SCP-firmware has moved to full support for SCMIv2 which means that
the base protocol can be either compliant with SCMI v1 or v2.
Allow any
From: Nicola Mazzucato <nicola.mazzucato@...>
The SCP-firmware has moved to full support for SCMIv2 which means that
the base protocol can be either compliant with SCMI v1 or v2.
Allow any
|
By
PierreGondois
·
#74791
·
|
|
Re: [PATCH RFC v2 06/28] OvmfPkg/BaseMemEncryptSevLib: Introduce MemEncryptSevClearMmioPageEncMask()
The commit message, and five comments in the patch, say "current page
table context". However, Cr3BaseAddress is taken explicitly.
I realize the files being modified in this patch already make
The commit message, and five comments in the patch, say "current page
table context". However, Cr3BaseAddress is taken explicitly.
I realize the files being modified in this patch already make
|
By
Laszlo Ersek
·
#74790
·
|
|
Re: [PATCH v4 1/7] IntelSiliconPkg/ReportCpuHobLib: Add ReportCpuHobLib
1. "Build a HOB for the CPU."
2. PhysicalAddressBits = (UINT8) AddressSizeEax.Bits.PhysicalAddressBits
1. "Build a HOB for the CPU."
2. PhysicalAddressBits = (UINT8) AddressSizeEax.Bits.PhysicalAddressBits
|
By
Ni, Ray
·
#74789
·
|