From: dmkhn@proton.me
To: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Cc: xen-devel@lists.xenproject.org, "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>
Subject: Re: [PATCH] x86: Conditionalise init_dom0_cpu_policy()
Date: Thu, 17 Jul 2025 19:44:05 +0000 [thread overview]
Message-ID: <aHlSf/xNUlYrexYt@kraken> (raw)
In-Reply-To: <20250717175825.463446-1-alejandro.garciavallejo@amd.com>
On Thu, Jul 17, 2025 at 07:58:24PM +0200, Alejandro Vallejo wrote:
> Later patches will keep refactoring create_dom0()
> until it can create arbitrary domains. This is one
> small step in that direction.
>
> Signed-off-by: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
Reviewed-by: Denis Mukhin <dmukhin@ford.com>
> ---
> xen/arch/x86/setup.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c
> index c6890669b9..6943ffba79 100644
> --- a/xen/arch/x86/setup.c
> +++ b/xen/arch/x86/setup.c
> @@ -1054,7 +1054,8 @@ static struct domain *__init create_dom0(struct boot_info *bi)
> if ( IS_ERR(d) )
> panic("Error creating d%u: %ld\n", bd->domid, PTR_ERR(d));
>
> - init_dom0_cpuid_policy(d);
> + if ( pv_shim || d->cdf & (CDF_privileged | CDF_hardware) )
> + init_dom0_cpuid_policy(d);
>
> if ( alloc_dom0_vcpu0(d) == NULL )
> panic("Error creating %pdv0\n", d);
>
> base-commit: 55719030b0bb0069fc8b57cd808dc98dc9d39add
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2025-07-17 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:58 [PATCH] x86: Conditionalise init_dom0_cpu_policy() Alejandro Vallejo
2025-07-17 19:44 ` dmkhn [this message]
2025-07-18 6:45 ` Jan Beulich
2025-07-23 7:18 ` Roger Pau Monné
2025-07-25 10:02 ` Alejandro Vallejo
2025-07-25 10:56 ` Roger Pau Monné
2025-07-29 21:29 ` Daniel P. Smith
2025-07-30 7:48 ` Jan Beulich
2025-07-30 9:48 ` Alejandro Vallejo
2025-07-30 9:58 ` Jan Beulich
2025-07-30 13:47 ` Alejandro Vallejo
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=aHlSf/xNUlYrexYt@kraken \
--to=dmkhn@proton.me \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.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.