public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, ray.ni@intel.com
Subject: Re: [edk2-devel] [PATCH 0/4] Sync BSP's APIC mode to APs in MP init flow
Date: Fri, 7 Jul 2023 10:55:41 +0200	[thread overview]
Message-ID: <4nerjr3hcwfepwzllcsrm3vurwzdyvr7qz6b4lqfualkngt7he@vjtw4v2ixksc> (raw)
In-Reply-To: <20230707052901.869-1-ray.ni@intel.com>

On Fri, Jul 07, 2023 at 01:28:57PM +0800, Ni, Ray wrote:

[ empty cover letter ]

Summary of the patch series changes would be nice.

If I read things correctly this series will:

  (a) allow platforms use x2apic mode by simply switching the BSP into
      x2apic mode early enough (for example in PlatformPei).
  (b) avoids waking up all APs a second time to set apic mode.

Is that correct?

Do you still plan to add a PCD to enable x2apic mode, or is that plan
obsoleted by (a) ?

take care,
  Gerd


  parent reply	other threads:[~2023-07-07  8:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  5:28 [PATCH 0/4] Sync BSP's APIC mode to APs in MP init flow Ni, Ray
2023-07-07  5:28 ` [PATCH 1/4] UefiCpuPkg/MpInitLib: Separate X2APIC enabling to subfunction Ni, Ray
2023-07-07  5:28 ` [PATCH 2/4] UefiCpuPkg/MpInitLib: Sync BSP's APIC mode to APs in InitConfig path Ni, Ray
2023-07-07  5:29 ` [PATCH 3/4] UefiCpuPkg/MpInitLib: Skip X2APIC enabling when BSP in X2APIC already Ni, Ray
2023-07-07  5:29 ` [PATCH 4/4] UefiCpuPkg/CpuFeatures: Deprecate CPU_FEATURE_X2APIC Ni, Ray
2023-07-07  8:55 ` Gerd Hoffmann [this message]
2023-07-07  9:25   ` [edk2-devel] [PATCH 0/4] Sync BSP's APIC mode to APs in MP init flow Ni, Ray
2023-07-07 11:26     ` Gerd Hoffmann
2023-11-09 16:29       ` Aaron Young via groups.io
2023-11-09 18:08         ` Michael D Kinney
2023-11-13 12:32           ` Laszlo Ersek

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=4nerjr3hcwfepwzllcsrm3vurwzdyvr7qz6b4lqfualkngt7he@vjtw4v2ixksc \
    --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