From: Julien Grall <julien@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org
Cc: Oleksii Kurochko <oleksii.kurochko@gmail.com>,
Community Manager <community.manager@xenproject.org>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v7] xen: allow up to 16383 cpus
Date: Fri, 10 May 2024 22:16:58 +0100 [thread overview]
Message-ID: <83f234f2-d43e-4141-b447-bc53a368d81f@xen.org> (raw)
In-Reply-To: <78fcd0d2-00fc-41ea-a531-7edbb8201dfc@citrix.com>
On 10/05/2024 22:11, Andrew Cooper wrote:
> On 10/05/2024 10:08 pm, Julien Grall wrote:
>> Hi Juergen,
>>
>> On 10/05/2024 15:16, Juergen Gross wrote:
>>> With lock handling now allowing up to 16384 cpus (spinlocks can handle
>>> 65535 cpus, rwlocks can handle 16384 cpus), raise the allowed limit for
>>> the number of cpus to be configured to 16383.
>>>
>>> The new limit is imposed by IOMMU_CMD_BUFFER_MAX_ENTRIES and
>>> QINVAL_MAX_ENTRY_NR required to be larger than 2 * CONFIG_NR_CPUS.
>>>
>>> Add a support limit of physical CPUs to SUPPORT.md (4096 on x86, 128
>>> on ARM).
>>>
>>> Signed-off-by: Juergen Gross <jgross@suse.com>
>>> Acked-by: Jan Beulich <jbeulich@suse.com>
>>
>> I am a bit surprised that this is kept given you added SUPPORT.md. I'd
>> like Jan (or other x86 maintainers) to confirm they are happy with the
>> proposed x86 security supported limit the SUPPORT.md.
>>
>> For Arm (only):
>>
>> Acked-by: Julien Grall <jgrall@amazon.com>
>
> XenServer is currently at 2k and we're waiting on this series to move to 4k.
>
> I'm happy with this being the security statement for now.
Thanks for confirming :). Committed.
Cheers,
--
Julien Grall
prev parent reply other threads:[~2024-05-10 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 14:16 [PATCH v7] xen: allow up to 16383 cpus Juergen Gross
2024-05-10 21:08 ` Julien Grall
2024-05-10 21:11 ` Andrew Cooper
2024-05-10 21:16 ` Julien Grall [this message]
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-all 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=83f234f2-d43e-4141-b447-bc53a368d81f@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=community.manager@xenproject.org \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).