EFI_RESOURCE_MEMORY_UNACCEPTED has been officially defined in the PI
1.8 specification. So all temporary solutions have been replaced with
the actual definition.
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Jiewen Yao
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
OvmfPkg/AmdSevDxe/AmdSevDxe.c
Added WaitOnEvent() function to EFI_DELAYTED_DISPATCH_PPI.
Modified DispatchRegister() parameter list.
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdePkg/Include/Ppi/DelayedDispatch.h | 24 +++-
1 file changed, 23 insertions(+), 1
Revision macros have been updated to indicate PI 1.8 specification
support
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdePkg/Include/Pi/PiDxeCis.h | 6 +++---
MdePkg/Include/Pi/PiMmCis.h | 6 +++---
MdePkg/Include/Pi/PiMultiPhase.h | 6 ++
Defined Encrypted and Special Purpose resource attributes as
defined in PI 1.8 Specification
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdePkg/Include/Pi/PiHob.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MdePkg/Include/Pi/PiHob.h
EFI_RESOURCE_MEMORY_UNACCEPTED has been officially defined in the PI
1.8 specification. So all temporary solutions have been replaced with
the actual definition.
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdePkg/Include/Pi/PiDxeCis.h | 13 +
EFI_RESOURCE_MEMORY_UNACCEPTED has been officially defined in the PI
1.8 specification. So all temporary solutions have been replaced with
the actual definition.
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdeModulePkg/Core/Dxe/Gcd/Gcd.c | 10
In accordance with UEFI 2.10 Specification:
Adding definition for NVMe Over Fabric (NVMe-oF) Device Path
of Messaging Sub-Type.
Cc: Felix Polyudov
Cc: Dhanaraj V
Cc: Liming Gao
Signed-off-by: Sachin Ganesh
---
MdePkg/Include/Protocol/DevicePath.h | 22 ++
1 file changed,
This series of patches are for general updates to MdePkg and MdeModulePkg based
on
UEFI 2.10 and PI 1.8 Specifications
Sachin Ganesh (7):
MdePkg: Add definition for NVMe Over Fabric Device Path
MdePkg: Add new Resource Attributes defined in PI 1.8 Spec
MdePkg: Define Unaccepted Memory Type
From: Ard Biesheuvel
The optimization that enabled entry with MMU and caches enabled at EL1
removed the strict alignment requirement for XIP code (roughly, any code
that might execute with the MMU and caches off, which means SEC and PEI
phase modules but also *all* BASE libraries), on the basis
Ensure that when a #VC exception happens, the instruction at the
instruction pointer matches the instruction that is expected given the
error code. This is to mitigate the ahoi WeSee attack [1] that could
allow hypervisors to breach integrity and confidentiality of the
firmware by maliciously
On Fri, Apr 19, 2024 at 8:13 AM Tom Lendacky wrote:
>
> On 4/17/24 11:54, Adam Dunlap wrote:
> > +
> > +case SVM_EXIT_INVD:
> > + break;
>
> This changes the current behavior today, but I'm ok with that.
>
Whoops, I should've checked that. Should we delete InvdExit() then, if
it's dead
On Fri, 19 Apr 2024 at 18:36, Ard Biesheuvel wrote:
>
> On Fri, 19 Apr 2024 at 18:09, Jonathan Cameron via groups.io
> wrote:
> >
> > On Fri, 19 Apr 2024 13:52:07 +0200
> > Gerd Hoffmann wrote:
> >
> > > Hi,
> > >
> > > > Gerd, any ideas? Maybe I needs something subtly different in my
> > >
Reviewed-by: Michael D Kinney
> -Original Message-
> From: Jayaprakash, N
> Sent: Friday, April 19, 2024 2:01 AM
> To: devel@edk2.groups.io
> Cc: Jayaprakash, N ; Rebecca Cran
> ; Kinney, Michael D
> Subject: [edk2-libc Patch v3 1/1] ek2-libc: wrmsr function available
> in edk2module
Reviewed-by: Michael D Kinney
> -Original Message-
> From: devel@edk2.groups.io On Behalf Of Chang,
> Abner via groups.io
> Sent: Friday, April 19, 2024 12:40 AM
> To: devel@edk2.groups.io
> Cc: Kinney, Michael D ; Andrew Fish
> ; Leif Lindholm ; Attar,
> AbdulLateef (Abdul Lateef) ;
On Fri, 19 Apr 2024 at 18:09, Jonathan Cameron via groups.io
wrote:
>
> On Fri, 19 Apr 2024 13:52:07 +0200
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > > Gerd, any ideas? Maybe I needs something subtly different in my
> > > edk2 build? I've not looked at this bit of the qemu infrastructure
> > >
On Fri, 19 Apr 2024 13:52:07 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > Gerd, any ideas? Maybe I needs something subtly different in my
> > edk2 build? I've not looked at this bit of the qemu infrastructure
> > before - is there a document on how that image is built?
>
> There is
On 4/17/24 11:54, Adam Dunlap wrote:
Ensure that when a #VC exception happens, the instruction at the
instruction pointer matches the instruction that is expected given the
error code. This is to mitigate the ahoi WeSee attack [1] that could
allow hypervisors to breach integrity and
On 4/18/24 07:15, Gerd Hoffmann via groups.io wrote:
On Wed, Apr 17, 2024 at 09:54:00AM -0700, Adam Dunlap via groups.io wrote:
Ensure that when a #VC exception happens, the instruction at the
instruction pointer matches the instruction that is expected given the
error code. This is to mitigate
On Fri, 19 Apr 2024 at 15:00, Chang, Abner wrote:
>
> [AMD Official Use Only - General]
>
> I guess my RB misled contributors thought the patch is good to merge.
> However, I was thinking Eric's team should give the final RB after the
> validation as they are the maintainers for the subordinate
[AMD Official Use Only - General]
I guess my RB misled contributors thought the patch is good to merge. However,
I was thinking Eric's team should give the final RB after the validation as
they are the maintainers for the subordinate VanGoghBoard platform. Suppose the
impacted packages should
Cc: Ard Biesheuvel
Cc: Jiewen Yao
Cc: Konstantin Kostiuk
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/VirtHstiDxe/README.md | 48 +++
1 file changed, 48 insertions(+)
create mode 100644 OvmfPkg/VirtHstiDxe/README.md
diff --git a/OvmfPkg/VirtHstiDxe/README.md
Detects qemu config issue: code pflash is writable.
Checked for both PC and Q35.
Cc: Ard Biesheuvel
Cc: Jiewen Yao
Cc: Konstantin Kostiuk
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/VirtHstiDxe/VirtHstiDxe.inf | 2 ++
OvmfPkg/VirtHstiDxe/VirtHstiDxe.h | 13 +++
From: Konstantin Kostiuk
The driver supports qemu machine types 'pc' and 'q35'.
This patch adds some helper functions to manage the bitmasks.
The implemented features depend on both OVMF build configuration
and qemu VM configuration.
For q35 a single security feature is supported and checked:
Detects qemu config issue: vars pflash is not in secure mode (write
access restricted to smm). Applies to Q35 with SMM only.
Cc: Ard Biesheuvel
Cc: Jiewen Yao
Cc: Konstantin Kostiuk
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/VirtHstiDxe/VirtHstiDxe.inf | 4 ++
From: Konstantin Kostiuk
Cc: Ard Biesheuvel
Cc: Jiewen Yao
Signed-off-by: Konstantin Kostiuk
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/OvmfPkgIa32.dsc| 2 ++
OvmfPkg/OvmfPkgIa32X64.dsc | 2 ++
OvmfPkg/OvmfPkgX64.dsc | 2 ++
OvmfPkg/OvmfPkgIa32.fdf| 1 +
OvmfPkg/OvmfPkgIa32X64.fdf
v2:
- remove 'Q35' from test bits
- add patch with a README.md
Gerd Hoffmann (3):
OvmfPkg/VirtHstiDxe: add varstore flash check
OvmfPkg/VirtHstiDxe: add code flash check
OvmfPkg/VirtHstiDxe: add README.md
Konstantin Kostiuk (2):
OvmfPkg: Add VirtHstiDxe driver
OvmfPkg: Add
On Fri, Apr 19, 2024 at 08:11:27AM +0800, Min Xu wrote:
> From: Min M Xu
>
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4756
>
> There are below updates in this patch:
> 1. Rename README to README.md so that it can be show as markdown
>document.
> 2. Update some information about
Hi,
> Gerd, any ideas? Maybe I needs something subtly different in my
> edk2 build? I've not looked at this bit of the qemu infrastructure
> before - is there a document on how that image is built?
There is roms/Makefile for that.
make -C roms help
make -C roms efi
So easiest would be to
[AMD Official Use Only - General]
Hi Ard,
Agree with you, reverting code looks not a good way now. We will think about
new method to resolve this issue. Just need a bit more time and I will hold on
checking in code to VanGoghBoard before it.
Thanks again for your suggestion and help us improve
On Thu, Apr 18, 2024 at 08:39:20AM -0700, Adam Dunlap wrote:
> On Thu, Apr 18, 2024 at 5:15 AM Gerd Hoffmann wrote:
> >
> > On Wed, Apr 17, 2024 at 09:54:00AM -0700, Adam Dunlap via groups.io wrote:
> > > + UINT8 OpCode;
> >
> > The linux kernel patch uses "unsigned int opcode" and apparently
>
On Wed, Apr 10, 2024 at 01:50:12PM +0800, WangYang wrote:
> This commit adds the initial support for BOSC's
> nanhu platform which provides up to 2 RISC-V RV64
> processor cores.
>
> Signed-off-by: Yang Wang
> Signed-off-by: Ran Wang
> Signed-off-by: YunFeng Yang
> Signed-off-by: YaXing Guo
>
Dear Michael,
I don't know if you had time to answer one follow-up question.
Obviously one thing that someone might want to do is to notify on protocol
installs and trap installs of this protocol - e.g. so that something other than
UefiBootManagerLib can manage and monitor HTTP boot, but still
On Fri, 19 Apr 2024 at 11:06, Xing, Eric wrote:
>
> [AMD Official Use Only - General]
>
> Hi Ard,
>
> This checkin causes VanGoghBoard build fail now. Would you help revert it?
> I will merge PATCH to VanGoghBoard after the code review process done and
> code changes are verified pass on real
[AMD Official Use Only - General]
Hi Ard,
This checkin causes VanGoghBoard build fail now. Would you help revert it?
I will merge PATCH to VanGoghBoard after the code review process done and code
changes are verified pass on real board.
Thanks,
Eric
> -Original Message-
> From: Ard
Thanks Mike as suggested made the logic simpler.
Sent the updated v3 patch for review.
Regards,
JP
-Original Message-
From: Kinney, Michael D
Sent: Friday, April 19, 2024 2:35 AM
To: Jayaprakash, N ; devel@edk2.groups.io
Cc: Rebecca Cran ; Kinney, Michael D
Subject: RE: [edk2-libc
The wrmsr function always writes 0s to the higher 32 bits of the msr register.
This PR fixes this issue reported through the BZ4745
Jayaprakash N (1):
ek2-libc: wrmsr function available in edk2module is not working as
expected
.../Python/Python-3.6.8/PyMod-3.6.8/Modules/edk2module.c
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4745
This commit fixes the issue reported in the BZ4745.
The wrmsr was always writing 0 to the higher 32 bits of the msr register.
This was due to a logical flaw in the code, where the input variable of
type unsigned int was left shitted by 32
On Fri, 19 Apr 2024 at 10:10, Xing, Eric via groups.io
wrote:
>
> [AMD Official Use Only - General]
>
>
> Thanks Duke.
>
>
>
> Hi Thomas,
>
>
>
> PATCH1/2 still cannot be checked in because today’s VanGoghBoard is based off
> EDK2_202208. Please hold on this PATCH check in.
>
>
Apologies, but I
[AMD Official Use Only - General]
Thanks Duke.
Hi Thomas,
PATCH1/2 still cannot be checked in because today’s VanGoghBoard is based off
EDK2_202208. Please hold on this PATCH check in.
Added my comments below.
Thanks,
Eric
> -Original Message-
> From: Zhai, MingXin
[AMD Official Use Only - General]
Hi edk2 stewards,
Per off-line discussion with Ray Ni, he considers Liming's RB is good enough
for this patch set. Please help to review this and give your RB to the
maintainship of MdeModulePkg/Bus/Spi If you don't have concerns.
Thank you!
Abner
>
[AMD Official Use Only - General]
Hi Thomas,
Yes, I agree with your opinion, edk2-platforms should be able to build against
the latest edk2 repo. That is why we plan to update VanGoghBoard to support
latest EDK2, In fact we are doing QA testing.
I think every change on VanGoghBoard need
So this is just junk unallocated memory that we are reporting as
a type it *could* be if an allocation occurs to minimize failures
of ExitBootServices. Which is questionable. But in terms of
attributes, I would expect we either have this unallocated
memory marked the same as the bin type or
42 matches
Mail list logo
