From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, Leo Duran <leo.duran@amd.com>,
edk2-devel@lists.01.org
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Jeff Fan <jeff.fan@intel.com>, Liming Gao <liming.gao@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH] UefiCpuPkg/LocalApicLib: Exclude second SendIpi sequence on AMD processors.
Date: Wed, 13 Jun 2018 22:52:17 +0200 [thread overview]
Message-ID: <6e4e65de-ef6c-a94a-b94c-aa3572a31dcf@redhat.com> (raw)
In-Reply-To: <9e2b3f74-c37e-06d9-293e-04976713ce8c@redhat.com>
On 13/06/2018 22:49, Laszlo Ersek wrote:
> Hello Leo,
>
> On 06/13/18 22:11, Leo Duran wrote:
>> On AMD processors the second SendIpi in the SendInitSipiSipi and
>> SendInitSipiSipiAllExcludingSelf routines is not required, and may cause
>> undesired side-effects during MP initialization.
>>
>> This patch leverages the StandardSignatureIsAuthenticAMD check to exclude
>> the second SendIpi and its associated MicroSecondDelay (200).
>
> QEMU and KVM emulate some AMD processors too; of particular interest is
> the recent EPYC addition, I believe (for SME/SEV, minimally).
>
> Did you check whether the StandardSignatureIsAuthenticAMD() check
> applies to those QEMU VCPU models, and if so, whether omitting the
> second Startup IPI interferes with *V*CPU startup in OVMF guests? (In
> multiprocessing modules, such as CpuMpPei, CpuDxe, and PiSmmCpuDxeSmm.)
>
> Adding Brijesh, Paolo and Igor.
Actually I would be surprised if any recent processor needs the
INIT-SIPI-SIPI (though I'm not sure what undesired side effects it might
trigger).
Paolo
next prev parent reply other threads:[~2018-06-13 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:11 [PATCH] UefiCpuPkg/LocalApicLib: Exclude second SendIpi on AMD Leo Duran
2018-06-13 20:11 ` [PATCH] UefiCpuPkg/LocalApicLib: Exclude second SendIpi sequence on AMD processors Leo Duran
2018-06-13 20:49 ` Laszlo Ersek
2018-06-13 20:52 ` Paolo Bonzini [this message]
2018-06-14 5:39 ` Ni, Ruiyu
2018-06-14 9:04 ` Paolo Bonzini
2018-06-14 14:08 ` Duran, Leo
2018-06-14 14:52 ` Andrew Fish
2018-06-14 15:00 ` Laszlo Ersek
2018-06-14 15:47 ` Brijesh Singh
2018-06-14 16:36 ` Laszlo Ersek
2018-06-19 5:20 ` Dong, Eric
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=6e4e65de-ef6c-a94a-b94c-aa3572a31dcf@redhat.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