On Fri, Mar 02, 2018 at 11:19:31AM +0100, Laszlo Ersek wrote:
> On 03/01/18 11:48, Guo Heyi wrote:
> > On Thu, Mar 01, 2018 at 11:17:30AM +0100, Laszlo Ersek wrote:
> >> On 03/01/18 07:57, Heyi Guo wrote:
>
> >>> diff --git a/OvmfPkg/Library/PciHostBridgeLib/XenSupport.c
> >>>
On 03/03/18 10:03, Jian J Wang wrote:
>> v2 changes:
>> a. Reserve memory of mReservedApLoopFunc and mReservedTopOfApStack
>>separately to avoid making mReservedTopOfApStack executable.
>
> if PcdDxeNxMemoryProtectionPolicy is enabled for EfiReservedMemoryType
> of memory, #PF will be
On 03/02/18 13:53, Dr. David Alan Gilbert wrote:
> * Laszlo Ersek (ler...@redhat.com) wrote:
>> CC Dave
>> To give you the simplest example, binaries (and varstores) corresponding
>> to FD_SIZE_2MB and FD_SIZE_4MB are incompatible. If a domain is
>> originally defined on top of an FD_SIZE_2MB
On 03/02/18 14:17, Brijesh Singh wrote:
>
>
> On 3/2/18 5:53 AM, Laszlo Ersek wrote:
>> On 03/02/18 02:16, Brijesh Singh wrote:
>>>
>>> On 3/1/18 6:03 PM, Laszlo Ersek wrote:
I also tried to test the series with SEV guests (again with Brijesh's v2
2/2 patch applied on top).
On 03/05/18 06:49, Tiger Liu(BJ-RD) wrote:
> Hi, experts:
> I have a question about Ovmf.
>
> Must Ovmf be run with qemu tool?
> Or It could be run with Xen without needed qemu software.
>
> It seems Xen began to support uefi boot from 4.4 version.
- From the Xen wiki:
Hi, Laszlo:
Got it!
Thanks a lot!
Best wishes,
-邮件原件-
发件人: Laszlo Ersek [mailto:ler...@redhat.com]
发送时间: 2018年3月5日 17:15
收件人: Tiger Liu(BJ-RD)
抄送: 'edk2-devel@lists.01.org' ; Anthony Perard
; Julien Grall
Add PcdVTdPeiDmaBufferSize(S3) to replace the hard coded value
TOTAL_DMA_BUFFER_SIZE and TOTAL_DMA_BUFFER_SIZE_S3 in IntelVTdPmrPei.
Cc: Jiewen Yao
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
Hi
On Fri, Feb 23, 2018 at 8:45 PM, Andrew Fish wrote:
>
>
>> On Feb 23, 2018, at 5:23 AM, marcandre.lur...@redhat.com wrote:
>>
>> From: Marc-André Lureau
>>
>> Without this hack, GetNextHob() loops infinitely with the next patch.
>> I don't
Reviewed-by: Liming Gao
>-Original Message-
>From: Zhu, Yonghong
>Sent: Wednesday, February 07, 2018 8:36 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming ; Kinney, Michael D
>; Shaw, Kevin W
Reviewed-by: Liming Gao
>-Original Message-
>From: Zhu, Yonghong
>Sent: Wednesday, February 07, 2018 8:36 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming ; Kinney, Michael D
>; Shaw, Kevin W
Reviewed-by: Liming Gao
>-Original Message-
>From: Zhu, Yonghong
>Sent: Wednesday, February 07, 2018 8:36 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming ; Kinney, Michael D
>; Shaw, Kevin W
Reviewed-by: Liming Gao
>-Original Message-
>From: Zhu, Yonghong
>Sent: Wednesday, February 07, 2018 8:36 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming ; Kinney, Michael D
>; Shaw, Kevin W
Hi Laszlo,
On 03/05/2018 08:00 AM, Laszlo Ersek wrote:
On 03/02/18 14:17, Brijesh Singh wrote:
On 3/2/18 5:53 AM, Laszlo Ersek wrote:
Do you have (maybe updated) instructions for setting up the SEV host?
What are the latest bits that are expected to work together?
For host kernel:
-
One more comment.
On 03/05/2018 08:44 AM, Brijesh Singh wrote: >> \
-device
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
\
-netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 \
-device
On 03/02/18 14:17, Brijesh Singh wrote:
> On 3/2/18 5:53 AM, Laszlo Ersek wrote:
>> Do you have (maybe updated) instructions for setting up the SEV host?
>> What are the latest bits that are expected to work together?
> For host kernel:
> - use recent kvm/master
> - make sure following kernel
Reviewed-by: Liming Gao
>-Original Message-
>From: Laszlo Ersek [mailto:ler...@redhat.com]
>Sent: Saturday, March 03, 2018 2:09 AM
>To: edk2-devel-01
>Cc: Ard Biesheuvel ; Cole Robinson
>;
Reviewed-by: Liming Gao
>-Original Message-
>From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>Yonghong Zhu
>Sent: Monday, February 26, 2018 4:05 PM
>To: edk2-devel@lists.01.org
>Cc: Kinney, Michael D ; Shaw, Kevin W
Updated the IORT SMMUv3 Node structure and flags to match the
IO Remapping Table, Platform Design Document, Revision C dated
15 MAY 2017.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Sami Mujawar
Signed-off-by: Evan Lloyd
---
NULL is returned to Mapping when Operation is BusMasterCommonBuffer or
EdkiiIoMmuOperationBusMasterCommonBuffer64 in PeiIoMmuMap().
So Mapping == NULL is valid when calling PeiIoMmuUnmap().
940dbd071e9f01717236af236740aa0da716805f wrongly changed EFI_SUCCESS
to EFI_INVALID_PARAMETER when Mapping
On 5 March 2018 at 14:53, Sami Mujawar wrote:
> Updated the IORT SMMUv3 Node structure and flags to match the
> IO Remapping Table, Platform Design Document, Revision C dated
> 15 MAY 2017.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Sami
Reviewed-by: Jaben Carsey
> -Original Message-
> From: Wu, Hao A
> Sent: Friday, March 02, 2018 7:05 PM
> To: edk2-devel@lists.01.org
> Cc: Wu, Hao A ; Carsey, Jaben
> ; Ni, Ruiyu
> Subject: [PATCH]
In that case, would you be happy to take Girish's patches with the ASSERTs done
your (our) way?
Leif can fulminate about it when he gets back, if he really feels that strongly.
I suspect, though, that Leif is capable of being reasonable if pressed (and
offered beer at Plugfest).
Regards,
Evan
Hi
On Mon, Feb 26, 2018 at 10:50 AM, Laszlo Ersek wrote:
> On 02/23/18 14:23, marcandre.lur...@redhat.com wrote:
>> From: Marc-André Lureau
>>
>> This module measures and log the boot environment. It also produces
>> the Tcg2 protocol, which
On 03/05/18 15:05, Marc-André Lureau wrote:
> Hi
>
> On Fri, Feb 23, 2018 at 8:45 PM, Andrew Fish wrote:
>>
>>
>>> On Feb 23, 2018, at 5:23 AM, marcandre.lur...@redhat.com wrote:
>>>
>>> From: Marc-André Lureau
>>>
>>> Without this hack, GetNextHob()
On 03/05/18 16:45, Marc-André Lureau wrote:
> Hi
>
> On Mon, Feb 26, 2018 at 10:50 AM, Laszlo Ersek wrote:
>> On 02/23/18 14:23, marcandre.lur...@redhat.com wrote:
>>> + SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.inf {
>>> +
>>> +
>>>
On 03/05/18 15:13, Gao, Liming wrote:
> Reviewed-by: Liming Gao
Thank you, Liming; I pushed the series as commit range
20203d3f98d6..9de306701312.
Laszlo
>> -Original Message-
>> From: Laszlo Ersek [mailto:ler...@redhat.com]
>> Sent: Saturday, March 03, 2018 2:09
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: Zeng, Star
> Sent: Monday, March 5, 2018 10:17 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star ; Yao, Jiewen
> Subject: [PATCH] IntelSiliconPkg VTdPmrPei: Add
Reviewed-by: jiewen@intel.com
> -Original Message-
> From: Zeng, Star
> Sent: Monday, March 5, 2018 9:34 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star ; Yao, Jiewen
> Subject: [PATCH] IntelSiliconPkg VTdPmrPei: Return SUCCESS when
> On Mar 5, 2018, at 10:22 AM, Laszlo Ersek wrote:
>
> On 03/05/18 15:05, Marc-André Lureau wrote:
>> Hi
>>
>> On Fri, Feb 23, 2018 at 8:45 PM, Andrew Fish wrote:
>>>
>>>
On Feb 23, 2018, at 5:23 AM, marcandre.lur...@redhat.com wrote:
On 03/05/18 15:44, Brijesh Singh wrote:
> On 03/05/2018 08:00 AM, Laszlo Ersek wrote:
>> QEMU exits with the following error for me:
>>
>> 2018-03-05T13:40:12.478835Z qemu-system-x86_64: sev_ram_block_added:
>> failed to register region (0x7f3df3e0+0x2)
>> 2018-03-05T13:40:12.489183Z
Hi Ray,
Any comments for v5?
Regards,
Heyi
On Thu, Mar 01, 2018 at 02:57:22PM +0800, Heyi Guo wrote:
> PCI address translation is necessary for some non-x86 platforms. On
> such platforms, address value (denoted as "device address" or "address
> in PCI view") set to PCI BAR registers in
Correct the way of handling EFI_SECTION_GUID_DEFINED type sections
with a large size
Cc: Leif Lindholm
Cc: Ard Biesheuvel
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ge Song
---
On 03/05/2018 12:22 PM, Laszlo Ersek wrote:
PEIMs generally "execute in place" (XIP), i.e. they run from flash, not
RAM. In this status they use "temporary RAM" (e.g. CPU caches configured
like RAM) for stack & heap; whatever HOBs they produce are stored in
"temp RAM" as well. Then one of the
Laszlo:
I also suggest to check the generated ProcessLibraryConstructorList ()
function. It is in the driver build output AutoGen.c code. You can check what
library function be called in this function. Then, further add debug message in
the library function. I suspect some function does the
Ruiyu Ni (2):
MdeModulePkg/NullMemoryTest: Change prototype of ConvertToTestedMemory
MdeModulePkg/NullMemoryTest: Fix bug in CompatibleRangeTest
.../MemoryTest/NullMemoryTestDxe/NullMemoryTest.c | 82 +-
1 file changed, 65 insertions(+), 17 deletions(-)
--
CompatibleRangeTest() contains two bugs:
1. It doesn't reject the memory above 16MB
2. it cannot handle the case when the partial or whole range of
requested memory is already tested.
The patch fixes the two bugs.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ruiyu Ni
The patch should not impact the functionality.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ruiyu Ni
Cc: Liming Gao
---
.../MemoryTest/NullMemoryTestDxe/NullMemoryTest.c | 37 ++
1 file changed, 24
Hi,
I am using Mmc Driver implemented in " EmbeddedPkg/Universal/MmcDxe/" for my
SD/MMC controller and my controller is not on PCI bus.
I am a bit confused if i should move to SD implementation available in
'MdeModulePkg\Bus\Pci\SdMmcPciHcDxe".
Please suggest.
Thanks,
Meenakshi
>
38 matches
Mail list logo