public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: "Ni, Ray" <ray.ni@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 0/4] Refactor MpInitLib
Date: Tue, 10 May 2022 10:13:26 -0500	[thread overview]
Message-ID: <b33e279e-e32e-b7b9-9aa6-3cefe90caaa3@amd.com> (raw)
In-Reply-To: <8580deda-b931-7c4f-d40a-c0230d3b8ef7@amd.com>

On 5/10/22 09:44, Tom Lendacky wrote:
> On 5/9/22 18:16, Ni, Ray wrote:
>> https://github.com/niruiyu/edk2/tree/refactormp<https://github.com/niruiyu/edk2/tree/refactormp 
>>
> 
> Thanks for the tree, Ray. I was able to build and test against legacy,
> SEV, SEV-ES and SEV-SNP guests and found everything worked well.
> 
> I did notice a regression in the tree, un-related to your patches, when
> booting an SEV-SNP guest. The following message appears for each AP:
> 
> APIC: Stale IRR: 
> 00000000,00000000,00000000,00000000,00000000,00000000,00000001,00000000 
> ISR: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
> 
> So I'll start bisecting to see which commit introduced that.

This was introduced in the debug hack I needed to boot multiple vCPUs 
successfully (since Min's fix isn't in your tree, yet).

I hadn't noticed this in Min's MpLib fix, but after investigating I do see 
it now. I'll follow up with Min.

Thanks,
Tom

> 
> Thanks,
> Tom
> 
>>
>> thanks,
>> ray
>> --------------------------------------------------------------------------
>> *From:* devel@edk2.groups.io <devel@edk2.groups.io> on behalf of 
>> Lendacky, Thomas via groups.io <thomas.lendacky=amd.com@groups.io>
>> *Sent:* Tuesday, May 10, 2022 5:39:51 AM
>> *To:* devel@edk2.groups.io <devel@edk2.groups.io>; Ni, Ray 
>> <ray.ni@intel.com>
>> *Subject:* Re: [edk2-devel] [PATCH 0/4] Refactor MpInitLib
>> Hi Ray,
>>
>> Do you have a public git tree with these patches that I can use to test
>> with? I'm having lots of problems pulling these patches out of my mail
>> client and applying them.
>>
>> Thanks,
>> Tom
>>
>> On 5/7/22 10:13, Ni, Ray via groups.io wrote:
>>>
>>> Ray Ni (4):
>>>     MpInitLib: Allocate code buffer for PEI phase
>>>     MpInitLib: remove unneeded global ASM_PFX
>>>     MpInitLib: Put SEV logic in separate file
>>>     MpInitLib: Only allocate below 1MB memory for 16bit code
>>>
>>>    UefiCpuPkg/Library/MpInitLib/AmdSev.c         |   6 +-
>>>    UefiCpuPkg/Library/MpInitLib/DxeMpLib.c       |   2 +-
>>>    .../Library/MpInitLib/Ia32/MpFuncs.nasm       |  11 +-
>>>    UefiCpuPkg/Library/MpInitLib/MpEqu.inc        |   2 +-
>>>    UefiCpuPkg/Library/MpInitLib/MpLib.c          |  99 +++++------
>>>    UefiCpuPkg/Library/MpInitLib/MpLib.h          |   2 +-
>>>    UefiCpuPkg/Library/MpInitLib/PeiMpLib.c       |  15 +-
>>>    UefiCpuPkg/Library/MpInitLib/X64/AmdSev.nasm  | 148 ++++++++++++++++
>>>    UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm | 167 +-----------------
>>>    9 files changed, 216 insertions(+), 236 deletions(-)
>>>
>>
>>
>> 
>>
>>

  reply	other threads:[~2022-05-10 15:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 15:13 [PATCH 0/4] Refactor MpInitLib Ni, Ray
2022-05-07 15:13 ` [PATCH 1/4] MpInitLib: Allocate code buffer for PEI phase Ni, Ray
2022-05-07 15:13 ` [PATCH 2/4] MpInitLib: remove unneeded global ASM_PFX Ni, Ray
2022-05-07 15:13 ` [PATCH 3/4] MpInitLib: Put SEV logic in separate file Ni, Ray
2022-05-12 14:13   ` Lendacky, Thomas
2022-05-16  3:51     ` Ni, Ray
2022-05-07 15:13 ` [PATCH 4/4] MpInitLib: Only allocate below 1MB memory for 16bit code Ni, Ray
     [not found] ` <16ECDB685492F55B.14104@groups.io>
2022-05-09 11:54   ` [edk2-devel] [PATCH 3/4] MpInitLib: Put SEV logic in separate file Ni, Ray
2022-05-09 16:35     ` Lendacky, Thomas
2022-05-09 21:39 ` [edk2-devel] [PATCH 0/4] Refactor MpInitLib Lendacky, Thomas
2022-05-09 23:16   ` Ni, Ray
2022-05-10 14:44     ` Lendacky, Thomas
2022-05-10 15:13       ` Lendacky, Thomas [this message]
2022-05-12  1:21         ` Ni, Ray

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=b33e279e-e32e-b7b9-9aa6-3cefe90caaa3@amd.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