On 07/06/18 17:00, Brijesh Singh wrote:
> The Qemu flash range is marked as 'system ram' in EFI runtime memmap
> but it is actually an IO address. The patch series updates the
> EFI runtime memmap to add this range as Memory Mapped IO address.
>
> Changes since v3:
> - minor changes to address
On 07/06/2018 09:01 AM, Laszlo Ersek wrote:
On 07/05/18 21:12, Brijesh Singh wrote:
The Qemu flash range is marked as 'system ram' in EFI runtime memmap
but it is actually an IO address. The patch series updates the
EFI runtime memmap to add this range as Memory Mapped IO address.
Changes
Hi,All:
may be I should reply this to EDK2 group,I had attached my file again.
After many test,my right key of "ls | grep -trim-last 0 | grep -trim-last 0" is:
1,before pipe out the buffer,trim off all in-visible wchars at end of this
buffer, (the trimed of wchar is "like ASCII's range
AmdSevDxe maps the flash memory range with C=0, but
SetMemorySpaceAttributes() unconditionally resets the C-bit to '1'. Lets
restore the mapping back to C=0.
Cc: Ard Biesheuvel
Cc: Anthony Perard
Cc: Julien Grall
Cc: Justen Jordan L
Cc: Laszlo Ersek
Contributed-under: TianoCore Contribution
In the SMM build, only an SMM driver is using the address range hence we
do not need to expose the flash MMIO range in EFI runtime mapping.
Cc: Ard Biesheuvel
Cc: Anthony Perard
Cc: Julien Grall
Cc: Justen Jordan L
Cc: Laszlo Ersek
Contributed-under: TianoCore Contribution Agreement 1.1
The flash memory range is an IO address and should be presented as Memory
Mapped IO in EFI Runtime mapping. This information can be used by OS
when mapping the flash memory range.
It is especially helpful in SEV guest case, in which IO addresses should
be mapped as unencrypted. If memory region
The Qemu flash range is marked as 'system ram' in EFI runtime memmap
but it is actually an IO address. The patch series updates the
EFI runtime memmap to add this range as Memory Mapped IO address.
Changes since v3:
- minor changes to address Laszlo's review feedback.
Changes since v2:
- added
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Liming
> Gao
> Sent: Thursday, July 5, 2018 11:46 PM
> To: edk2-devel@lists.01.org
> Cc: Yao, Jiewen
> Subject: [edk2] [PATCH edk2-platforms\devel-MinPlatform]
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Liming
> Gao
> Sent: Thursday, July 5, 2018 11:46 PM
> To: edk2-devel@lists.01.org
> Cc: Yao, Jiewen
> Subject: [edk2] [PATCH edk2-platforms\devel-MinPlatform]
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Liming
> Gao
> Sent: Thursday, July 5, 2018 11:46 PM
> To: edk2-devel@lists.01.org
> Cc: Yao, Jiewen
> Subject: [edk2] [PATCH edk2-platforms\devel-MinPlatform]
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: Gao, Liming
> Sent: Thursday, July 5, 2018 11:46 PM
> To: edk2-devel@lists.01.org
> Cc: Yao, Jiewen
> Subject: [PATCH edk2-platforms\devel-MinPlatform] PurleyOpenBoardPkg:
> Remove unnecessary Link16 and IASL override
>
>
On 07/05/18 21:12, Brijesh Singh wrote:
> The Qemu flash range is marked as 'system ram' in EFI runtime memmap
> but it is actually an IO address. The patch series updates the
> EFI runtime memmap to add this range as Memory Mapped IO address.
>
> Changes since v2:
> - added cover letter and
Hopefully this should tidy the conversion warnings.
Add 32-bit and 64-bit functions that count number of set bits in a bitfield
using a divide-and-count method.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Tomas Pilar
Cc: Liming Gao
Cc: Michael D Kinney
---
Apologies, I usually compile with GCC49 since I work on linux. Respinning now.
Cheers
Tom
On 05/07/18 15:07, Gao, Liming wrote:
> warning C4244
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
On 07/05/18 21:12, Brijesh Singh wrote:
> AmdSevDxe maps the flash memory range with C=0, but
> SetMemorySpaceAttributes() unconditionally resets the C-bit to '1'. Lets
> restore the mapping back to C=0.
>
> Cc: Ard Biesheuvel
> Cc: Anthony Perard
> Cc: Julien Grall
> Cc: Justen Jordan L
>
On 07/06/18 13:35, Laszlo Ersek wrote:
> On 07/05/18 21:12, Brijesh Singh wrote:
>> In the SMM build, only an SMM driver is using the address range hence we
>> do not need to expose the flash MMIO range in EFI runtime mapping.
>>
>> Cc: Ard Biesheuvel
>> Cc: Anthony Perard
>> Cc: Julien Grall
On 07/05/18 21:12, Brijesh Singh wrote:
> In the SMM build, only an SMM driver is using the address range hence we
> do not need to expose the flash MMIO range in EFI runtime mapping.
>
> Cc: Ard Biesheuvel
> Cc: Anthony Perard
> Cc: Julien Grall
> Cc: Justen Jordan L
> Cc: Laszlo Ersek
>
On 07/05/18 21:12, Brijesh Singh wrote:
> The flash memory range is an IO address and should be presented as Memory
> Mapped IO in EFI Runtime mapping. This information can be used by OS
> when mapping the flash memory range.
>
> It is especially helpful in SEV guest case, in which IO addresses
Reviewed-by: Star Zeng
And pushed patch at 9090c8b533013078c6df773e128070c76d917830.
Thanks,
Star
-Original Message-
From: Bi, Dandan
Sent: Friday, July 6, 2018 4:11 PM
To: Thomas Palmer ; edk2-devel@lists.01.org
Cc: Dong, Eric ; Zeng, Star
Subject: RE: [edk2] [PATCH 1/1]
On Wed, Jul 4, 2018 at 6:34 PM, AlexeiFedorov wrote:
> From: Alexei Fedorov
>
> Juno's DSDT contains 2 PLPI packages in Clusters #0 and #1 and
> _OSC method reports support for platform coordinated mode only.
> According to the description of LevelID field in
> ACPI 6.2 Errata A Specification
Reviewed-by: Dandan Bi
Thanks,
Dandan
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Thomas
Palmer
Sent: Wednesday, July 4, 2018 12:46 AM
To: edk2-devel@lists.01.org
Cc: Dong, Eric ; Zeng, Star
Subject: [edk2] [PATCH 1/1]
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Liming Gao
Cc: Jiewen Yao
---
ReadMe.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ReadMe.md b/ReadMe.md
index 9de6493..5bcdd1d 100644
--- a/ReadMe.md
+++ b/ReadMe.md
@@ -32,7 +32,7 @@ edk2-non-osi
Use python.exe from PYTHON_HOME
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Liming Gao
Cc: Jiewen Yao
---
Platform/Intel/KabylakeOpenBoardPkg/KabylakeRvp3/bld.bat | 2 +-
.../Tools/Fsp/RebaseAndPatchFspBinBaseAddress.py | 7 ---
PCD value in build report shows HEX and DEC both. PatchFv tool only requires
one value.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Liming Gao
Cc: Jiewen Yao
---
Platform/Intel/MinPlatformPkg/Tools/PatchFv/PatchBfv.py | 2 +-
Link16 is not used any longer. Remove the checker for it.
IASL path is not required to be override.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Liming Gao
Cc: Jiewen Yao
---
.../BoardMtOlympus/PlatformPkgBuildOption.dsc| 2 +-
Pushed at 4d76bbcce62e3b972cd226e5f0e43d21db48a3f7.
Thanks,
Star
-Original Message-
From: Zeng, Star
Sent: Friday, July 6, 2018 3:30 PM
To: Thomas Palmer ; edk2-devel@lists.01.org
Cc: Dong, Eric ; gar...@hpe.com; joseph.shiffl...@hpe.com;
Zeng, Star
Subject: RE: [PATCH 1/1]
Hi Thomas,
Basically, I agree with this patch as PciIoDevice->BusNumberRanges equals
Configuration from PciResAlloc->StartBusEnumeration, and according to PI spec
"Because the size of ACPI resource descriptors is not fixed,
StartBusEnumeration() is responsible for allocating memory for the
Reviewed-by: Star Zeng
-Original Message-
From: Thomas Palmer [mailto:thomas.pal...@hpe.com]
Sent: Wednesday, July 4, 2018 12:41 AM
To: edk2-devel@lists.01.org
Cc: Dong, Eric ; Zeng, Star ;
gar...@hpe.com; joseph.shiffl...@hpe.com; Thomas Palmer
Subject: [PATCH 1/1]
28 matches
Mail list logo
