From: "Min Xu" <min.m.xu@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Dong, Eric" <eric.dong@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"James Bottomley" <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH V2 0/6] Support 2 CpuMpPei/CpuDxe in One image
Date: Mon, 9 May 2022 23:37:16 +0000 [thread overview]
Message-ID: <PH0PR11MB50640E178D0C81E9FE44BBFFC5C69@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f52c13a2-f971-742c-fe56-210573e30aee@amd.com>
On May 10, 2022 1:30 AM, Tom Lendacky wrote:
>
> On 5/9/22 07:44, Xu, Min M wrote:
> > Gerd & Tom
> > What are your comments about this patch-set?
>
> Hi Min,
>
> This appears to resolve the issue. I was able to boot a 64 vCPU guest in
> legacy, SEV, SEV-ES and SEV-SNP modes without any asserts.
>
> I'm assuming that you were able to see the ASSERTs on your end and
> validate, too?
>
Yes. I enable a 4 vCPU legacy guest and can see the ASSERTs. But it appears in a random rate so it missed in the CI.
Thanks
Min
next prev parent reply other threads:[~2022-05-09 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 1:36 [PATCH V2 0/6] Support 2 CpuMpPei/CpuDxe in One image Min Xu
2022-05-07 1:36 ` [PATCH V2 1/6] UefiCpuPkg: Revert "UefiCpuPkg: Enable Tdx support in MpInitLib" Min Xu
2022-05-07 5:30 ` Ni, Ray
2022-05-07 1:36 ` [PATCH V2 2/6] OvmfPkg: Add MpInitLibDepLib related PPI/Protocol definitions Min Xu
2022-05-07 1:36 ` [PATCH V2 3/6] OvmfPkg: Add MpInitLibDepLib Min Xu
2022-05-07 1:36 ` [PATCH V2 4/6] OvmfPkg/Sec: Install MpInitLibDepLib PPIs in SecMain.c Min Xu
2022-05-07 1:36 ` [PATCH V2 5/6] OvmfPkg/TdxDxe: Install MpInitLibDepLib protocols Min Xu
2022-05-07 1:36 ` [PATCH V2 6/6] OvmfPkg: Enable 2 different CpuMpPei and CpuDxe drivers Min Xu
2022-05-07 5:30 ` [PATCH V2 0/6] Support 2 CpuMpPei/CpuDxe in One image Ni, Ray
2022-05-09 12:44 ` Min Xu
2022-05-09 17:29 ` Lendacky, Thomas
2022-05-09 23:37 ` Min Xu [this message]
2022-05-10 13:22 ` Lendacky, Thomas
2022-05-10 15:16 ` Lendacky, Thomas
2022-05-10 9:26 ` Gerd Hoffmann
2022-05-11 0:13 ` Min Xu
2022-05-11 8:47 ` Yao, Jiewen
2022-05-11 8:47 ` Yao, Jiewen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR11MB50640E178D0C81E9FE44BBFFC5C69@PH0PR11MB5064.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox