Michael:
This is my suggestion to resolve such compatible issue. As you say, it needs
more review and discussion. So, it may not be applied immediately.
If this patch set needs to catch this table tag, it has to take current way
to update each DSC file. Have the patch set got reviewed-by
Merge it https://github.com/tianocore/edk2/pull/2887
Thanks
Liming
> -邮件原件-
> 发件人: devel@edk2.groups.io 代表 gaoliming
> 发送时间: 2022年5月12日 14:56
> 收件人: 'Rebecca Cran' ; 'Ard Biesheuvel'
>
> 抄送: 'edk2-devel-groups-io' ; 'Leif Lindholm'
> ; 'Ard Biesheuvel' ;
> 'Sami Mujawar' ; 'Gerd
On 5/11/22 19:52, Min Xu via groups.io wrote:
On May 11, 2022 10:06 PM, Lendacky, Thomas wrote:
On 5/10/22 21:00, Xu, Min M wrote:
On May 11, 2022 4:30 AM, Tom Lendacky wrote:
I'm replying to this patch since I can't find patch V12 46/47
anywhere in my email.
I've bisected a regression in
Can you please respond with your preference?
I am ready to do this but if it is required now, it should be documented
so it becomes a consistent pattern for future changes.
Thanks,
Michael
On 5/10/2022 11:01 AM, Michael Kubacki wrote:
What's the plan for next steps? The v5 PR has been up for
Reminder
On 5/10/2022 1:34 PM, Michael Kubacki wrote:
Another reminder to look at this patch.
Thanks,
Michael
On 4/29/2022 4:07 PM, Michael Kubacki wrote:
Another reminder to merge this series. Chasel has added his review and
that is in this branch:
Reminder to review this patch.
On 5/10/2022 1:33 PM, Michael Kubacki wrote:
Another reminder to review this patch.
Thanks,
Michael
On 4/29/2022 4:08 PM, Michael Kubacki wrote:
Please help review this patch when possible.
Thanks,
Michael
On 4/22/2022 10:02 AM, Michael Kubacki wrote:
Hi Gerd,
> Is there some way to (a) figure ovmf runs on aws, and (b) figure what the
> physical address space is?
We do not have a straight way to do either at the moment without adding
something else which we would prefer to avoid.
> (keeping the series as-is is fine with me too).
If you
On Fri, May 13, 2022 at 08:56:06AM -0500, Tom Lendacky wrote:
> On 5/13/22 08:22, Michael Roth wrote:
> > A full-featured SEV-SNP guest will not rely on the AP jump table, and
> > will instead use the AP Creation interface defined by the GHCB. However,
> > a guest is still allowed to use the AP
On Fri, May 13, 2022 at 08:32:38AM -0500, Tom Lendacky wrote:
> On 5/13/22 08:22, Michael Roth wrote:
> > The Confidential Computing blob defined here is intended to match the
> > definition defined by linux guest kernel. Previously, both definitions
> > relied on natural alignment, but that
A full-featured SEV-SNP guest will not rely on the AP jump table, and
will instead use the AP Creation interface defined by the GHCB. However,
a guest is still allowed to use the AP jump table if desired.
However, unlike with SEV-ES guests, SEV-SNP guests should not
store/retrieve the jump table
The Confidential Computing blob defined here is intended to match the
definition defined by linux guest kernel. Previously, both definitions
relied on natural alignment, but that relies on both OVMF and kernel
being compiled as 64-bit. While there aren't currently any plans to
enable SNP support
On 5/13/22 08:22, Michael Roth wrote:
A full-featured SEV-SNP guest will not rely on the AP jump table, and
will instead use the AP Creation interface defined by the GHCB. However,
a guest is still allowed to use the AP jump table if desired.
However, unlike with SEV-ES guests, SEV-SNP guests
On 5/13/22 08:22, Michael Roth wrote:
The Confidential Computing blob defined here is intended to match the
definition defined by linux guest kernel. Previously, both definitions
relied on natural alignment, but that relies on both OVMF and kernel
being compiled as 64-bit. While there aren't
On 5/3/2022 12:25 PM, Ard Biesheuvel wrote:
On Tue, 3 May 2022 at 17:54, annie li wrote:
Adding maintainers into the CC list...
On 5/2/2022 5:05 PM, annie li wrote:
Hello
I am wondering if anyone will review this patch please? Any comments
are welcome.
Thanks
Annie
On 4/15/2022 5:15 PM,
Hi Sami,
Sorry for the late reply.
https://github.com/waip23/edk2/tree/upstread-fix-mm-issue
branch: upstread-fix-mm-issue
Regards,
Ming Huang
在 4/6/22 5:03 PM, Sami Mujawar 写道:
> Hi Ming,
>
> I am not sure if this is an issue at my end, but I cannot apply this patch
> series, can you
Hi Liming,
It's just an example for downstream developer how to use DEBUG_FILE_PATH.
If the developer prefer the original ASSERT, nothing need to do.
Now, we have an option to avoid the random file path at least.
Another benefit is that we can save flash size when we developing new feature
Thanks Chinni! Just few comments below inline, please help to check.
Would you also help to update commit message format and include Bugzilla link
for reference?
Thanks,
Chasel
> -Original Message-
> From: devel@edk2.groups.io On Behalf Of
> cbduggap
> Sent: Thursday, May 12, 2022
17 matches
Mail list logo
