public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Alejandro Vallejo via groups.io" <alejandro.vallejo=cloud.com@groups.io>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: devel@edk2.groups.io, Anthony Perard <anthony.perard@citrix.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg: Set PcdCpuMaxLogicalProcessorNumber in OvmfXen
Date: Thu, 25 Apr 2024 11:42:01 +0100	[thread overview]
Message-ID: <5c832dc4-57e9-43a4-96ed-63074da2652f@cloud.com> (raw)
In-Reply-To: <mzncylj24ftykwunvyzziz3yrb2rrdelsln5vc3yyjo36jvocc@vcjpypsi53c7>

Hi,

On 25/04/2024 08:31, Gerd Hoffmann wrote:
> On Wed, Apr 24, 2024 at 02:36:32PM +0100, Alejandro Vallejo wrote:
>> Bump the compile-time constant for maximum processor count from 64 to 128
>> in order to allow that many vCPUs to be brought online on Xen guests with
>> the default OVMF configuration.
> 
>> +  # UefiCpuPkg PCDs related to initial AP bringup and general AP management.
>> +  gUefiCpuPkgTokenSpaceGuid.PcdCpuMaxLogicalProcessorNumber|128
> 
> Note that this is a dynamic PCD, so you can set it at runtime to the
> number of vcpus present in the VM.  See MaxCpuCountInitialization() in
> OvmfPkg/PlatformPei/Platform.c for example.
> 
> take care,
>   Gerd
> 

Thanks for the heads up. Do you mean setting it at runtime through
fw_cfg? I saw PlatformMaxCpuCountInitialization() providing some
customizability, but Xen's toolstack doesn't provide fw_cfg at the
moment so it can't (as far as I've seen) use it.

I'm currently forced to do the override at compile time passing this...

    --pcd gUefiCpuPkgTokenSpaceGuid.PcdCpuMaxLogicalProcessorNumber=128

... to build.sh, but I'd rather have the default max match Xen's idea of
max unless there's a strong reason not to.

Cheers,
Alejandro


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118286): https://edk2.groups.io/g/devel/message/118286
Mute This Topic: https://groups.io/mt/105721898/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-04-25 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 13:36 [edk2-devel] [PATCH] OvmfPkg: Set PcdCpuMaxLogicalProcessorNumber in OvmfXen Alejandro Vallejo via groups.io
2024-04-25  7:31 ` Gerd Hoffmann
2024-04-25 10:42   ` Alejandro Vallejo via groups.io [this message]
2024-04-25 10:59     ` Anthony PERARD via groups.io
2024-04-25 13:58       ` Gerd Hoffmann
2024-06-28 14:25         ` Alejandro Vallejo via groups.io

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=5c832dc4-57e9-43a4-96ed-63074da2652f@cloud.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