From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Alejandro Vallejo <alejandro.vallejo@cloud.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 09:31:22 +0200 [thread overview]
Message-ID: <mzncylj24ftykwunvyzziz3yrb2rrdelsln5vc3yyjo36jvocc@vcjpypsi53c7> (raw)
In-Reply-To: <f29d514f7ae98b65ffd79962fae683f08ad2a06f.1713965534.git.alejandro.vallejo@cloud.com>
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
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118274): https://edk2.groups.io/g/devel/message/118274
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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-25 7:31 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 [this message]
2024-04-25 10:42 ` Alejandro Vallejo via groups.io
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=mzncylj24ftykwunvyzziz3yrb2rrdelsln5vc3yyjo36jvocc@vcjpypsi53c7 \
--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