From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Nicola Vetrini <nicola.vetrini@bugseng.com>
Cc: Jan Beulich <jbeulich@suse.com>,
dmkhn@proton.me, andrew.cooper3@citrix.com,
anthony.perard@vates.tech, julien@xen.org, michal.orzel@amd.com,
sstabellini@kernel.org, teddy.astie@vates.tech, dmukhin@ford.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v8] xen/domain: rewrite emulation_flags_ok()
Date: Tue, 17 Jun 2025 09:18:38 +0200 [thread overview]
Message-ID: <aFEWzjgOOKKqfR51@macbook.local> (raw)
In-Reply-To: <dff6968c29274374d32c01baed7ca806@bugseng.com>
On Tue, Jun 17, 2025 at 08:53:51AM +0200, Nicola Vetrini wrote:
> On 2025-06-17 08:19, Jan Beulich wrote:
> > On 17.06.2025 03:15, dmkhn@proton.me wrote:
> > > --- a/xen/arch/x86/domain.c
> > > +++ b/xen/arch/x86/domain.c
> > > @@ -743,32 +743,75 @@ int arch_sanitise_domain_config(struct
> > > xen_domctl_createdomain *config)
> > > return 0;
> > > }
> > >
> > > +/*
> > > + * Verify that the domain's emulation flags resolve to a supported
> > > configuration.
> > > + *
> > > + * This ensures we only allow a known, safe subset of emulation
> > > combinations
> > > + * (for both functionality and security). Arbitrary mixes are
> > > likely to cause
> > > + * errors (e.g. null pointer dereferences).
> > > + *
> > > + * NB: use the internal X86_EMU_XXX symbols, not the public
> > > XEN_X86_EMU_XXX
> > > + * symbols, to take build-time config options (e.g. CONFIG_HVM)
> > > into account
> > > + * for short-circuited emulations.
> > > + */
> > > static bool emulation_flags_ok(const struct domain *d, uint32_t
> > > emflags)
> > > {
> > > + enum domain_capability {
> > > + CAP_PV = BIT(0, U),
> > > + CAP_HVM = BIT(1, U),
> > > + CAP_HWDOM = BIT(2, U),
> > > + CAP_DOMU = BIT(3, U),
> > > + };
> > > + static const struct {
> > > + enum domain_capability caps;
> > > + uint32_t min;
> > > + uint32_t opt;
> > > + } configs[] = {
> > > +#ifdef CONFIG_PV
> > > + /* PV dom0 and domU */
> > > + {
> > > + .caps = CAP_PV | CAP_HWDOM | CAP_DOMU,
> >
> > Just to double check - are we sure Misra / Eclair will like this (ab)use
> > of an enum?
> >
> > Jan
>
> Likely not, but x86_64 is build with CONFIG_PV=n
It's doing the same for HVM also, so it would trigger for the instance
below then. I will ack v7 then, which used an unsigned int instead.
Thanks, Roger.
next prev parent reply other threads:[~2025-06-17 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 1:15 [PATCH v8] xen/domain: rewrite emulation_flags_ok() dmkhn
2025-06-17 6:19 ` Jan Beulich
2025-06-17 6:53 ` Nicola Vetrini
2025-06-17 7:18 ` Roger Pau Monné [this message]
2025-06-17 9:15 ` 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=aFEWzjgOOKKqfR51@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--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.