From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Xen-devel" <xen-devel@lists.xenproject.org>
Cc: "Jan Beulich" <JBeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86/cpu-policy: Extend the guest max policy max leaf/subleaves
Date: Tue, 29 Oct 2024 18:26:38 +0000 [thread overview]
Message-ID: <D58I2I9IY2VV.FGUNJOWYNQ7U@cloud.com> (raw)
In-Reply-To: <20241029175505.2698661-1-andrew.cooper3@citrix.com>
On Tue Oct 29, 2024 at 5:55 PM GMT, Andrew Cooper wrote:
> We already have one migration case opencoded (feat.max_subleaf). A more
> recent discovery is that we advertise x2APIC to guests without ensuring that
> we provide max_leaf >= 0xb.
>
> In general, any leaf known to Xen can be safely configured by the toolstack if
> it doesn't violate other constraints.
>
> Therefore, introduce guest_common_{max,default}_leaves() to generalise the
> special case we currently have for feat.max_subleaf, in preparation to be able
> to provide x2APIC topology in leaf 0xb even on older hardware.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Alejandro Vallejo <alejandro.vallejo@cloud.com>
Cheers,
Alejandro
next prev parent reply other threads:[~2024-10-29 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 17:55 [PATCH] x86/cpu-policy: Extend the guest max policy max leaf/subleaves Andrew Cooper
2024-10-29 18:26 ` Alejandro Vallejo [this message]
2024-10-30 6:51 ` Jan Beulich
2024-10-30 10:30 ` Andrew Cooper
2024-10-30 8:59 ` Roger Pau Monné
2024-10-30 10:39 ` Andrew Cooper
2024-10-30 11:03 ` Roger Pau Monné
2024-10-30 14:45 ` Andrew Cooper
2024-10-30 15:13 ` Roger Pau Monné
2024-10-30 15:59 ` Alejandro Vallejo
2024-10-30 16:30 ` Roger Pau Monné
2024-10-30 16:51 ` Andrew Cooper
2024-10-30 17:10 ` Roger Pau Monné
2024-10-30 17:24 ` Andrew Cooper
2024-10-31 9:20 ` Jan Beulich
2024-10-31 9:16 ` Jan Beulich
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=D58I2I9IY2VV.FGUNJOWYNQ7U@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.