From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, julien@xen.org, bertrand.marquis@arm.com,
michal.orzel@amd.com, Volodymyr_Babchuk@epam.com,
andrew.cooper3@citrix.com, edgar.iglesias@amd.com,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Juergen Gross" <jgross@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 1/5] xen/arm: Add way to disable traps on accesses to unmapped addresses
Date: Mon, 2 Jun 2025 17:23:05 +0200 [thread overview]
Message-ID: <aD3B2c4jtrT5A85T@zapote> (raw)
In-Reply-To: <4cd82cbb-fc01-425d-b036-62f80a027a9b@suse.com>
On Mon, Jun 02, 2025 at 10:45:36AM +0200, Jan Beulich wrote:
> On 30.05.2025 15:45, Edgar E. Iglesias wrote:
> > --- a/xen/common/domain.c
> > +++ b/xen/common/domain.c
> > @@ -721,7 +721,8 @@ static int sanitise_domain_config(struct xen_domctl_createdomain *config)
> > ~(XEN_DOMCTL_CDF_hvm | XEN_DOMCTL_CDF_hap |
> > XEN_DOMCTL_CDF_s3_integrity | XEN_DOMCTL_CDF_oos_off |
> > XEN_DOMCTL_CDF_xs_domain | XEN_DOMCTL_CDF_iommu |
> > - XEN_DOMCTL_CDF_nested_virt | XEN_DOMCTL_CDF_vpmu) )
> > + XEN_DOMCTL_CDF_nested_virt | XEN_DOMCTL_CDF_vpmu |
> > + XEN_DOMCTL_CDF_trap_unmapped_accesses) )
> > {
> > dprintk(XENLOG_INFO, "Unknown CDF flags %#x\n", config->flags);
> > return -EINVAL;
> > --- a/xen/include/public/domctl.h
> > +++ b/xen/include/public/domctl.h
> > @@ -66,9 +66,11 @@ struct xen_domctl_createdomain {
> > #define XEN_DOMCTL_CDF_nested_virt (1U << _XEN_DOMCTL_CDF_nested_virt)
> > /* Should we expose the vPMU to the guest? */
> > #define XEN_DOMCTL_CDF_vpmu (1U << 7)
> > +/* Should we trap guest accesses to unmapped addresses? */
> > +#define XEN_DOMCTL_CDF_trap_unmapped_accesses (1U << 8)
>
> Besides being pretty long an identifier (and that's already with "guest" not
> even in the name), if this is to be arch-independent, would this perhaps fit
> x86'es recently introduced "advanced" PVH handling of holes? See [1].
>
Looks like the implementation of the options would be related
but trap_unmapped_accesses is intended for domU's and pf-fixup is for
dom0 IIUC, so in terms of configuration they would be different...
I'm happy to change the name of trap_unmapped_accesses if there
are better (and shorter) ideas.
Thanks,
Edgar
> Jan
>
> [1] 104591f5dd67 ("x86/dom0: attempt to fixup p2m page-faults for PVH dom0")
next prev parent reply other threads:[~2025-06-02 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 13:45 [PATCH v3 0/5] xen/arm: Add option to optionally disable trapping on unmapped acceses Edgar E. Iglesias
2025-05-30 13:45 ` [PATCH v3 1/5] xen/arm: Add way to disable traps on accesses to unmapped addresses Edgar E. Iglesias
2025-06-02 8:45 ` Jan Beulich
2025-06-02 15:23 ` Edgar E. Iglesias [this message]
2025-06-02 22:35 ` Stefano Stabellini
2025-06-03 9:36 ` Julien Grall
2025-06-03 12:48 ` Edgar E. Iglesias
2025-05-30 13:45 ` [PATCH v3 2/5] xen/arm: dom0less: Add trap-unmapped-accesses Edgar E. Iglesias
2025-06-02 22:36 ` Stefano Stabellini
2025-06-02 22:47 ` Julien Grall
2025-06-02 22:57 ` Stefano Stabellini
2025-06-03 12:59 ` Edgar E. Iglesias
2025-05-30 13:45 ` [PATCH v3 3/5] tools/arm: Add the trap_unmapped_accesses xl config option Edgar E. Iglesias
2025-06-02 22:42 ` Stefano Stabellini
2025-06-03 9:34 ` Julien Grall
2025-06-03 12:49 ` Edgar E. Iglesias
2025-05-30 13:45 ` [PATCH v3 4/5] tools/ocaml: Update bindings for CDF_TRAP_UNMAPPED_ACCESSES Edgar E. Iglesias
2025-05-30 13:49 ` Christian Lindig
2025-05-30 13:45 ` [PATCH v3 5/5] tools/golang: Regenerate bindings for trap_unmapped_accesses Edgar E. Iglesias
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=aD3B2c4jtrT5A85T@zapote \
--to=edgar.iglesias@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=edgar.iglesias@amd.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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 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.