On 16 November 2017 at 09:48, Zeng, Star wrote:
> As I remember UEFI 2.5 clarified this and added EFI_MEMORY_RO was because
> EFI_MEMORY_WP had been typically used for cache even before UEFI 2.5.
>
> And I do not think this patch should filter out EFI_MEMORY_WP since this
>
V2: Halt HC at EndOfPei.
Update the EhciPei driver to consume IOMMU_PPI to allocate DMA buffer.
If no IOMMU_PPI exists, this driver still calls PEI service to allocate
DMA buffer, with assumption that DRAM==DMA.
Cc: Jiewen Yao
Contributed-under: TianoCore Contribution
Currently, each ARM platform built with RVCT that uses ArmHvcLib
or ArmSmcLib needs to specify a CPU target that implements both the
security and virtualization extensions, so that the assembler does
not choke on the 'hvc' and 'smc' instructions in ArmHvcLib/ArmSvcLib.
Let's move these overrides
On 16 November 2017 at 14:15, Ard Biesheuvel wrote:
> On 16 November 2017 at 12:34, Ard Biesheuvel
> wrote:
>>
>>
>>> On 16 Nov 2017, at 11:59, Leif Lindholm wrote:
>>>
On Thu, Nov 16, 2017 at 09:40:58AM
XenHypercallLib uses the 'hvc' instruction, which is not implemented
on all ARMv7 CPUs, and so we need to explicitly specify a CPU that
has the virtualization extensions.
This override used to be set at the platform level, but this was removed
in commit 0d36a219c7bdbb27d775b50837823b2a9928147c
Forward to Julien at his @linaro.org address.
-- Forwarded message --
From: Ard Biesheuvel
Date: 16 November 2017 at 16:56
Subject: [PATCH] OvmfPkg/XenHypercallLib: enable virt extensions for ARM
To: edk2-devel@lists.01.org, leif.lindh...@linaro.org,
On Wed, Nov 15, 2017 at 11:19:32AM +, Ard Biesheuvel wrote:
> From: Pipat Methavanitpong
>
> Add Macronix MX66U1G45G definition to NorFlashInfoLib
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Pipat Methavanitpong
On 2017.11.16 14:48, Gao, Liming wrote:
I agree to separate HOST and ARCH. For this patch, I have minor comment on
WINSDK10_BIN.
DEFINE WINSDK10_BIN = ENV(WINSDK10_PREFIX)x86
==>
DEFINE WINSDK10_BIN = ENV(WINSDK10_PREFIX)DEF(VS2017_HOST)
Good point. I agree that the SDK should
Apologies for delay in responding.
On Thu, Nov 09, 2017 at 04:41:55PM +0800, Haojian Zhuang wrote:
> > > In the HiKey platform, I prepared the same driver for both eMMC and
> > > SD. So the device paths are in below.
> > > SD: /HardwareVendor(0d51905b-b77e-452a-a2c0-eca0cc8d514a)[9: 00 e0 23 f7
Some OSs will treat EFI_MEMORY_DESCRIPTOR.Attribute as really
set attributes and change memory paging attribute accordingly.
But current EFI_MEMORY_DESCRIPTOR.Attribute is assigned by
value from Capabilities in GCD memory map. This might cause
boot problems. Clearing all paging related
Ard:
Does this error only happen on ACPI table compiling? But, I see -no-pie is
also in normal DLINK flag. Why is the driver not compiled failed?
Thanks
Liming
> -Original Message-
> From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org]
> Sent: Thursday, November 16, 2017 11:09 PM
>
On 11/15/2017 07:18 PM, Paulo Alcantara wrote:
This patch adds stack trace support during a X64 CPU exception.
It will dump out back trace, stack contents as well as image module
names that were part of the call stack.
Contributed-under: TianoCore Contribution Agreement 1.1
Cc: Eric Dong
On Wed, Nov 15, 2017 at 01:06:45PM +, Ard Biesheuvel wrote:
> The PL031 driver implements a VExpress/Juno specific hack to set the
> battery backed clock in addition to the PL031. However, none of the
> remaining VExpress based hardware we support in EDK2 actuall implements
> this feature so
On 16 November 2017 at 16:24, Leif Lindholm wrote:
> On Wed, Nov 15, 2017 at 11:19:32AM +, Ard Biesheuvel wrote:
>> From: Pipat Methavanitpong
>>
>> Add Macronix MX66U1G45G definition to NorFlashInfoLib
>>
>> Contributed-under:
The PL011 code in ArmPlatformPkg is organized in a weird way: there is
a single PL011Uart.h header file under Include/Drivers containing both
register definitions and function entry points. The PL011Uart library
itself is in Drivers/ but it is actually a library.
So let's clean this up: add a new
On 16 November 2017 at 15:07, Marcin Wojtas wrote:
> Hi Ard,
>
> 2017-11-16 15:48 GMT+01:00 Ard Biesheuvel :
>> On 16 November 2017 at 14:38, Marcin Wojtas wrote:
>>> Hi Ard,
>>>
>>> With both PIE disabling patches for AARCH64,
On Thu, Nov 16, 2017 at 02:35:46PM +, Ard Biesheuvel wrote:
> Currently, each ARM platform built with RVCT that uses ArmHvcLib
> or ArmSmcLib needs to specify a CPU target that implements both the
> security and virtualization extensions, so that the assembler does
> not choke on the 'hvc' and
On 16 November 2017 at 15:31, Gao, Liming wrote:
> Ard:
> Does this error only happen on ACPI table compiling? But, I see -no-pie is
> also in normal DLINK flag. Why is the driver not compiled failed?
>
The main difference is that the ACPI tables don't tolerate any
Seemingly, the Memory Attributes Table should be consumed for memory protection.
UEFI spec: "The Memory Attributes Table is currently used to describe memory
protections that may be applied to the EFI Runtime code and data by an
operating system or hypervisor."
Someone (Jiewen?) familiar with
> v6
> a. Add workaround in core to filter out all paging related capabilities.
>This is to fix boot issue in Fedora 26 and Windows Server 2016.
> b. Add code to check if EFI_MEMORY_XP should be added for GCD memory map
More than one entry of RT_CODE memory might cause boot problem for some
> v6:
>Add ExecuteDisable feature check to include/exclude EFI_MEMORY_XP
> v5:
>Coding style clean-up
> v4:
> a. Remove DoUpdate and check attributes mismatch all the time to avoid
>a logic hole
> b. Add warning message if failed to update capability
> c. Add local variable to hold
1. Call IoMmuInit() after locating gPeiUsbControllerPpiGuid.
2. Call XhcPeiFreeSched() to do cleanup in XhcEndOfPei.
Cc: Jiewen Yao
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
1. The use of WindowsSdkVerBinPath allows us to access the latest SDK,
which we will need when we introduce VS2017 support for AARCH64.
2. Make the breakdown between host and target more explicit, and more in
line with how Microsoft reorganized the latest Visual Studio
toolchains, by
Hi Ard,
2017-11-16 15:48 GMT+01:00 Ard Biesheuvel :
> On 16 November 2017 at 14:38, Marcin Wojtas wrote:
>> Hi Ard,
>>
>> With both PIE disabling patches for AARCH64, when compiling ACPI tables with
>>
On 16 November 2017 at 14:38, Marcin Wojtas wrote:
> Hi Ard,
>
> With both PIE disabling patches for AARCH64, when compiling ACPI tables with
> gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
> I get following errors:
> [...]
> aarch64-linux-gnu-gcc:
> On 16 Nov 2017, at 11:59, Leif Lindholm wrote:
>
>> On Thu, Nov 16, 2017 at 09:40:58AM +, Ard Biesheuvel wrote:
>>> On 15 November 2017 at 14:03, Ard Biesheuvel
>>> wrote:
>>> Now that the PL031 RTC driver library no longer depends
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Guo Mang
---
Platform/BroxtonPlatformPkg/BiosId.env | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Platform/BroxtonPlatformPkg/BiosId.env
b/Platform/BroxtonPlatformPkg/BiosId.env
Series Reviewed-by: Jordan Justen
On 2017-11-15 13:56:59, Laszlo Ersek wrote:
> Repo: https://github.com/lersek/edk2.git
> Branch: temp_ram_tweaks_v2
>
> This is a series for
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=747
>
> specifically an update on
Hi Ard,
With both PIE disabling patches for AARCH64, when compiling ACPI tables with
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
I get following errors:
[...]
aarch64-linux-gnu-gcc: error: unrecognized command line option '-no-pie'
Do I understand correctly, that I
The following is a set of changes that I'd like to see applied to Liming's
2017-10-18 VS2017 support proposal for IA32 and X64.
(See https://lists.01.org/pipermail/edk2-devel/2017-October/016175.html)
Since I am planning to submit a v2 of my VS2017 ARM/AARCH64 proposal, that
relies on these
On 16 November 2017 at 12:34, Ard Biesheuvel wrote:
>
>
>> On 16 Nov 2017, at 11:59, Leif Lindholm wrote:
>>
>>> On Thu, Nov 16, 2017 at 09:40:58AM +, Ard Biesheuvel wrote:
On 15 November 2017 at 14:03, Ard Biesheuvel
On Thu, Nov 16, 2017 at 09:40:58AM +, Ard Biesheuvel wrote:
> On 15 November 2017 at 14:03, Ard Biesheuvel
> wrote:
> > Now that the PL031 RTC driver library no longer depends on the ARM
> > platform specific ArmPlatformSysConfigLib, we no longer need to
> >
Paulo,
I don't understand why you - 1 when calculating EIP offset in image, it
confused me.
+ for (;;) {
+//
+// Print stack frame in the following format:
+//
+// # @ + (RBP) in [ | ]
+//
+InternalPrintMessage (
+ "%d 0x%016lx @ 0x%016lx+0x%x (0x%016lx) in
Switch to the new version of PL011UartLib which supersedes the one
residing in Drivers/ inappropriately.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/AMD/OverdriveBoard/OverdriveBoard.dsc | 2 +-
Remove all gEmbeddedTokenSpaceGuid.PcdEmbeddedPrompt assignments, which
are no longer meaningful with EBL removed.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/ARM/JunoPkg/ArmJuno.dsc | 1 -
No drivers actually use PL35xSmcLib so remove any resolutions for it.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/ARM/VExpressPkg/ArmVExpress.dsc.inc | 2 --
Silicon/Hisilicon/Hisilicon.dsc.inc | 2 --
2
On 11/16/17 11:47, Paolo Bonzini wrote:
> When SEV is enabled, every debug message printed by OVMF to the
> QEMU debug port traps from the guest to QEMU character by character
> because "REP OUTSB" cannot be used by IoWriteFifo8. Furthermore,
> when OVMF is built with the DEBUG_VERBOSE bit (value
On 11/16/17 11:47, Paolo Bonzini wrote:
> The next patch will want to add a global variable to
> PlatformDebugLibIoPort, but this is not suitable for the SEC
> phase, because SEC runs from read-only flash. The solution is
> to have two library instances, one for SEC and another
> for all other
Clean up the PL011 UART support library, by moving it into the appropriate
place for libraries, and splitting the header file into an implementation
and an interface part.
Ard Biesheuvel (2):
ArmPlatformPkg: reorganize PL011 code
ArmVirtPkg: switch to new PL011UartLib implementation
The PL011 code in ArmPlatformPkg is organized in a weird way: there is
a single PL011Uart.h header file under Include/Drivers containing both
register definitions and function entry points. The PL011Uart library
itself is in Drivers/ but it is actually a library.
So let's clean this up: add a new
Switch to the new, cleaned up PL011UartLib implementation so we will
be able to remove the old one.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
ArmVirtPkg/ArmVirt.dsc.inc| 2 +-
On Thu, Nov 16, 2017 at 05:38:10PM +, Ard Biesheuvel wrote:
> On 16 November 2017 at 17:36, Leif Lindholm wrote:
> > On Thu, Nov 16, 2017 at 05:12:16PM +, Ard Biesheuvel wrote:
> >> The PL011 code in ArmPlatformPkg is organized in a weird way: there is
> >> a
On Thu, Nov 16, 2017 at 05:12:16PM +, Ard Biesheuvel wrote:
> The PL011 code in ArmPlatformPkg is organized in a weird way: there is
> a single PL011Uart.h header file under Include/Drivers containing both
> register definitions and function entry points. The PL011Uart library
> itself is in
On 16 November 2017 at 17:36, Leif Lindholm wrote:
> On Thu, Nov 16, 2017 at 05:12:16PM +, Ard Biesheuvel wrote:
>> The PL011 code in ArmPlatformPkg is organized in a weird way: there is
>> a single PL011Uart.h header file under Include/Drivers containing both
>>
These platforms don't actually include the SP804 driver so no need
to set the PCDs.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/Hisilicon/D02/Pv660D02.dsc | 8
Platform/Hisilicon/D03/D03.dsc | 8
Remove copy-pasted ArmTrustedMonitorLib library class resolutions
that none of the platforms actually need.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/AMD/OverdriveBoard/OverdriveBoard.dsc | 2 --
This is mostly a preparatory series that will allow us to get rid of a lot
of code that is specific to only a single ARM development platform out of
the main EDK2 tree.
First of all, it removes a couple of false dependencies of various platforms
on libraries that are no longer used, or not
Remove copy-pasted ArmPlatformSecExtraActionLib library class resolutions
that none of the platforms actually need.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/AMD/OverdriveBoard/OverdriveBoard.dsc |
On Thu, Nov 16, 2017 at 05:47:06PM +, Ard Biesheuvel wrote:
> Clean up the PL011 UART support library, by moving it into the appropriate
> place for libraries, and splitting the header file into an implementation
> and an interface part.
For the series:
Reviewed-by: Leif Lindholm
On 11/16/17 18:47, Ard Biesheuvel wrote:
> Switch to the new, cleaned up PL011UartLib implementation so we will
> be able to remove the old one.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ard Biesheuvel
> ---
>
Hi Brijan,
On Thu, November 16, 2017 1:43 pm, Brian J. Johnson
>
> (These comments apply to patch 3/3 as well.)
>
> Typo: UnwondStacksCount should be UnwoundStacksCount
Fixed in v3. Thanks!
>
> It's good to check the alignment of the stack, as you're doing. But
> I'll reiterate that you
On Thu, November 16, 2017 5:47 am, Hao Wu wrote:
> In order to create all of the children (El Torito standard and UDF) for
> a CD/DVD media in an entry of the PartitionDriverBindingStart(), this
> commit merges the discovery of the El Torito feature
> (PartitionInstallElToritoChildHandles) into
Currently, in TlsInitialize(), neither the return status of
OPENSSL_init_ssl(0, or 1) nor the return code of RandomSeed
(TRUE or FALSE) is not checked. Also VOID is used as the return
type of TlsInitialize(), which can't be used to capture the
returned value for the error handling.
>From Long Qin
when build a single module with GenC/GenMake option, currently it will
direct return after create Autogen code files, then it cause MaList is
empty, which cause an incorrect error message is reported.
Cc: Liming Gao
Contributed-under: TianoCore Contribution Agreement 1.1
This is version 2 of the patch I sent yesterday, now with proper SEC
support. The series makes OvmfPkg's PlatformDebugLibIoPort library
skip I/O port writes when the debug port device wasn't added to the
virtual machine.
Patch 1 creates a separate PlatformDebugLibIoPort instance for SEC, so
that
Mike,
Returning EFI_NOT_READY for USB_BOOT_ASC_NO_MEDIA seems a little confusing, but
based on the real case, I am ok with the patch.
Reviewed-by: Star Zeng
Thanks,
Star
-Original Message-
From: Kinney, Michael D
Sent: Wednesday, November 15, 2017 9:28 AM
To:
Mike,
After this patch, the return status of UsbBotGetMaxLun seems confusing and
useless. Fortunately, there is no one using the return status of it.
What do you think?
Thanks,
Star
-Original Message-
From: Kinney, Michael D
Sent: Thursday, November 16, 2017 11:58 AM
To:
ArmVExpress.dsc.inc declares a TimerLib dependency and resolves it
using ArmPlatformPkg/Library/SP804TimerLib/SP804TimerLib.inf, but
all users of the include file supersede it with ArmArchTimerLib.inf
so let's just use that instead.
Contributed-under: TianoCore Contribution Agreement 1.1
Move ArmJunoPkg into edk2-platforms, so it can be removed from the main
EDK2 tree.
This allows use to remove the dodgy -I arguments to GCC to build shared
modules with a different copy of ArmPlatform.h, which was making it very
difficult to properly split the various modules into their own
Remove false copy-pasted dependencies on various VExpress support
libraries.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/Hisilicon/D02/Pv660D02.dsc | 3 ---
Platform/Hisilicon/D03/D03.dsc | 5 -
None of these platforms still include EBL, but some references
remained to its support libraries. Get rid of that.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/ARM/VExpressPkg/ArmVExpress.dsc.inc | 6 --
No FVP driver uses this library so remove the resolution.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Platform/ARM/VExpressPkg/ArmVExpress-FVP-AArch64.dsc | 1 -
1 file changed, 1 deletion(-)
diff --git
When SEV is enabled, every debug message printed by OVMF to the
QEMU debug port traps from the guest to QEMU character by character
because "REP OUTSB" cannot be used by IoWriteFifo8. Furthermore,
when OVMF is built with the DEBUG_VERBOSE bit (value 0x0040)
enabled in
Hi Liming,
I chatted with Aaron on the phone today. The VfrCompiler race condition was
discovered using "make -j " (where n > 1). I have filed the bug in Bugzilla:
https://bugzilla.tianocore.org/show_bug.cgi?id=786
For the ARCH environment variable, we brainstormed two possible new names
On 11/16/17 17:56, Ard Biesheuvel wrote:
> XenHypercallLib uses the 'hvc' instruction, which is not implemented
> on all ARMv7 CPUs, and so we need to explicitly specify a CPU that
> has the virtualization extensions.
>
> This override used to be set at the platform level, but this was removed
>
Hi,
This series adds stack trace support during a X64 CPU exception.
Informations like back trace, stack contents and image module names
(that were part of the call stack) will be dumped out.
We already have such support in ARM/AArch64 (IIRC) exception handling
(thanks to Ard), and then I
This patch adds stack trace support during a IA32 CPU exception.
It will dump out back trace, stack contents as well as image module
names that were part of the call stack.
Contributed-under: TianoCore Contribution Agreement 1.1
Cc: Eric Dong
Cc: Laszlo Ersek
Hi Andrew,
On Thu, November 16, 2017 3:01 am, Andrew Fish wrote:
> Paulo,
>
> Those attached stack traces don't look right.
What about the new ones?
Thanks!
Paulo
>
> Thanks,
>
> Andrew Fish
>
>> On Nov 15, 2017, at 5:46 PM, Paulo Alcantara wrote:
>>
>> Hi,
>>
>> On
The next patch will want to add a global variable to
PlatformDebugLibIoPort, but this is not suitable for the SEC
phase, because SEC runs from read-only flash. The solution is
to have two library instances, one for SEC and another
for all other firmware phases. This patch adds the "plumbing"
for
This is version 3 of the series to skip debug port I/O port writes
when the debug port device wasn't added to the virtual machine.
The differences from v2 are entirely cosmetic, and I'm including them
at the end of this message for ease of review.
Thanks,
Paolo
Paolo Bonzini (3):
OvmfPkg:
Remove Uefi.h, which includes UefiSpec.h, and change the
return value to match the RETURN_STATUS type.
Contributed-under: TianoCore Contribution Agreement 1.1
Tested-by: Laszlo Ersek
Cc: Laszlo Ersek
Cc: Ard Biesheuvel
Cc: Jordan
This function will be used by both IA32 and X64 exception handling in
order to print out image module names during stack unwinding.
Cc: Eric Dong
Cc: Laszlo Ersek
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Paulo Alcantara
This patch adds stack trace support during a X64 CPU exception.
It will dump out back trace, stack contents as well as image module
names that were part of the call stack.
Contributed-under: TianoCore Contribution Agreement 1.1
Cc: Eric Dong
Cc: Laszlo Ersek
Hi Jiewen,
On Wed, November 15, 2017 11:57 pm, Yao, Jiewen wrote:
> Hi Paulo
> Thanks to bring this cool feature.
>
> I have same feeling as Jeff Fan. It is great!
>
> I have some questions, hope you can clarify.
> 1) Would you please let us know which tool change is validated? Such as
> MSVC, or
Hello All,
When I do SCT test, get the below failure
GenericTest\EFICompliantTest 0 0 CB6F7B77-0B15-43F7-A95B-8C7F9FD70B21 FAIL UEFI
Compliant - TLS support is required
The reason for the failure is that the platform doesn't have TLS related
protocols installed.
->if the platform supports TLS
HI
I have 2 comments:
1) I do not think we need mention: WORKAROUND.
I suggest we just use "NOTE".
We have similar example before, see MdePkg\Library\BasePeCoffLib\BasePeCoff.c
//
// NOTE: Some versions of Linux ELILO for Itanium have an incorrect magic
value
// in the PE/COFF
Hi Karunakar,
Can you provide more detailed info for the SCT test steps? The crash can happen
after "Sct.efi -u" or need run any specific test case?
Thanks,
Jiaxin
From: Karunakar P [mailto:karunak...@amiindia.co.in]
Sent: Thursday, November 16, 2017 4:48 PM
To: 'edk2-devel@lists.01.org'
How about calling IoMmuInit () after locating gEdkiiPeiUfsHostControllerPpiGuid?
Same comment to SdBlockIoPei and EmmcBlockIoPei.
If you agree, Reviewed-by: Star Zeng
Thanks,
Star
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On
The next patch will want to add a global variable to
PlatformDebugLibIoPort, but this is not suitable for the SEC
phase, because SEC runs from read-only flash. The solution is
to have two library instances, one for SEC and another
for all other firmware phases. This patch adds the "plumbing"
for
1) Sure. I'll update the wording.
2) I still think this is just a workaround . In the long run, I don't think the
merge is a good idea. It looks like it will "fix" more issues, but actually it
just "hide" them and would cause more and more workaround in the future.
Anyway, if no one else has
I agree. Thanks for the comment.
> -Original Message-
> From: Zeng, Star
> Sent: Friday, November 17, 2017 10:31 AM
> To: Wang, Jian J ; edk2-devel@lists.01.org
> Cc: Yao, Jiewen ; Dong, Eric ;
> Zeng, Star
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: Zeng, Star
> Sent: Thursday, November 16, 2017 6:03 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star ; Yao, Jiewen
> Subject: [PATCH V2] MdeModulePkg EhciPei: Support IoMmu
>
> V2:
According to the definitions, DEBUG_POOL and DEBUG_PAGE are for alloc & free
pool/page.
#define DEBUG_POOL 0x0010 // Alloc & Free (pool)
#define DEBUG_PAGE 0x0020 // Alloc & Free (page)
How about changing the debug level to DEBUG_VERBOSE?
If you agree, you do not need send a
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: Zeng, Star
> Sent: Thursday, November 16, 2017 6:45 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star ; Yao, Jiewen
> Subject: [PATCH] MdeModulePkg XhciPei: Minor refinement about
> -Original Message-
> From: Zeng, Star
> Sent: Thursday, November 16, 2017 6:38 PM
> To: Wu, Hao A; edk2-devel@lists.01.org
> Cc: Wu, Hao A; Yao, Jiewen; Zeng, Star
> Subject: RE: [edk2] [PATCH v2] MdeModulePkg/UfsBlockIoPei: Support IoMmu
>
> How about calling IoMmuInit () after
Yes, same comments to SD/eMMC series.
Thanks,
Star
-Original Message-
From: Wu, Hao A
Sent: Friday, November 17, 2017 10:37 AM
To: Zeng, Star ; edk2-devel@lists.01.org
Cc: Yao, Jiewen
Subject: RE: [edk2] [PATCH v2] MdeModulePkg/UfsBlockIoPei:
Thanks for your reply. Comments below:
> -Original Message-
> From: Paulo Alcantara [mailto:pca...@zytor.com]
> Sent: Friday, November 17, 2017 6:13 AM
> To: Yao, Jiewen
> Cc: Paulo Alcantara ; edk2-devel@lists.01.org; Laszlo Ersek
>
Hi Jiaxin,
Below are the detailed steps for SCT test
[Steps to reproduce]
.
5. Run SCT test
a. Execute the following commands to run SCT test on SUT
sct -r
sct -u
b. In Test Case Management page, Enable GenericTest
c. Press F9 to run the selected test case
I will try to reproduce the issue with EDK2 trunk code, then feedback to you.
Thanks the report.
Jiaxin
From: Karunakar P [mailto:karunak...@amiindia.co.in]
Sent: Friday, November 17, 2017 2:32 PM
To: Wu, Jiaxin ; 'edk2-devel@lists.01.org'
Cc: Fu,
V2:
* Correct the commit log.
Currently, the return code of OPENSSL_init_ssl(0 or 1) and RandomSeed
(TRUE or FALSE) are not checked in TlsInitialize(). Also "VOID" is used
as the return type of TlsInitialize(), which can't be used to capture
the returned value for error handling.
>From Long Qin
On 15 November 2017 at 21:57, Laszlo Ersek wrote:
> This allows the PEI core to report the maximum temporary SEC/PEI stack
> usage on the DEBUG_INFO level, in the PeiCheckAndSwitchStack() function
> [MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c]:
>
> * Normal boot:
>
>> Temp
As I remember UEFI 2.5 clarified this and added EFI_MEMORY_RO was because
EFI_MEMORY_WP had been typically used for cache even before UEFI 2.5.
And I do not think this patch should filter out EFI_MEMORY_WP since this patch
is to filter out new paging bits caused by
Update Guid.xref to contain information from FILE statements in FDF
file.
Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=778
Cc: Liming Gao
Cc: Dmitry Antipov
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu
On 16 November 2017 at 07:26, Jian J Wang wrote:
> Some OSs will treat EFI_MEMORY_DESCRIPTOR.Attribute as really
> set attributes and change memory paging attribute accordingly.
> But current EFI_MEMORY_DESCRIPTOR.Attribute is assigned by
> value from Capabilities in GCD
Ard,
EFI_MEMORY_WP is for cache.
UefiSpec.h
//
// Note: UEFI spec 2.5 and following: use EFI_MEMORY_RO as write-protected
physical memory
// protection attribute. Also, EFI_MEMORY_WP means cacheability attribute.
//
#define EFI_MEMORY_WP 0x1000ULL
Thanks,
Star
On 16 November 2017 at 09:28, Zeng, Star wrote:
> Ard,
>
> EFI_MEMORY_WP is for cache.
>
> UefiSpec.h
> //
> // Note: UEFI spec 2.5 and following: use EFI_MEMORY_RO as write-protected
> physical memory
> // protection attribute. Also, EFI_MEMORY_WP means cacheability
On 15 November 2017 at 21:57, Laszlo Ersek wrote:
> "Main.asm" calls TransitionFromReal16To32BitFlat (and does some other
> things) before it jumps to the platform's SEC entry point.
>
> TransitionFromReal16To32BitFlat enters big real mode, and sets the DS, ES,
> FS, GS, and SS
On 15 November 2017 at 21:57, Laszlo Ersek wrote:
> This allows the PEI core to report the maximum temporary SEC/PEI stack
> usage on the DEBUG_INFO level, in the PeiCheckAndSwitchStack() function
> [MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c]:
>
> * Normal boot:
>
>> Temp
On 15 November 2017 at 14:03, Ard Biesheuvel wrote:
> Now that the PL031 RTC driver library no longer depends on the ARM
> platform specific ArmPlatformSysConfigLib, we no longer need to
> implement ArmPlatform.h or have a resolution for that library.
> This allows us
On 16 November 2017 at 01:01, Shannon Zhao wrote:
>
>
> On 2017/11/15 22:03, Ard Biesheuvel wrote:
>> On 15 November 2017 at 13:51, Laszlo Ersek wrote:
>>> > On 11/14/17 11:22, Ard Biesheuvel wrote:
>> The VariableRuntimeDxe driver may use
100 matches
Mail list logo