From: Jan Beulich <jbeulich@suse.com>
To: Penny Zheng <penny.zheng@arm.com>
Cc: Wei.Chen@arm.com, Bertrand.Marquis@arm.com,
xen-devel@lists.xenproject.org, sstabellini@kernel.org,
julien@xen.org
Subject: Re: [PATCH v2 1/6] xen: introduce XEN_DOMCTL_CDF_directmap
Date: Fri, 15 Oct 2021 10:46:41 +0200 [thread overview]
Message-ID: <073d4b36-cb2f-88b2-76d2-3438d4ef589a@suse.com> (raw)
In-Reply-To: <20211015030945.2082898-2-penny.zheng@arm.com>
On 15.10.2021 05:09, Penny Zheng wrote:
> From: Stefano Stabellini <stefano.stabellini@xilinx.com>
>
> This commit introduces a new arm-specific flag XEN_DOMCTL_CDF_directmap to
> specify that this domain should have its memory directly mapped
> (guest physical address == physical address) at domain creation.
>
> Refine is_domain_direct_mapped to check whether the flag
> XEN_DOMCTL_CDF_directmap is set.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
> Signed-off-by: Penny Zheng <penny.zheng@arm.com>
> ---
> CC: andrew.cooper3@citrix.com
> CC: jbeulich@suse.com
> CC: George Dunlap <George.Dunlap@eu.citrix.com>
> CC: Ian Jackson <ian.jackson@eu.citrix.com>
> CC: Wei Liu <wl@xen.org>
> CC: "Roger Pau Monné" <roger.pau@citrix.com>
> ---
Please have here a brief log of changes in the new version, to aid
reviewers.
> xen/arch/arm/domain.c | 3 ++-
> xen/arch/arm/domain_build.c | 4 +++-
> xen/common/domain.c | 3 ++-
> xen/include/asm-arm/domain.h | 4 ++--
> xen/include/public/domctl.h | 4 +++-
> 5 files changed, 12 insertions(+), 6 deletions(-)
You clearly had to re-base over the XEN_DOMCTL_CDF_vpmu addition. I think
just like that change (which I'd expect you to have looked at while doing
the re-base) you also need to at least fiddle with OCaml's
domain_create_flag, to keep the ABI check there happy.
> --- a/xen/include/public/domctl.h
> +++ b/xen/include/public/domctl.h
> @@ -72,9 +72,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)
> +/* If this domain has its memory directly mapped? (ARM only) */
> +#define XEN_DOMCTL_CDF_directmap (1U << 8)
The comment doesn't read well; how about "Should domain memory be directly
mapped?" That's if a comment here is really needed in the first place. I
also don't think "Arm only" should be here - this may go stale. What I'm
missing in this regard is rejecting of the flag in x86'es
arch_sanitise_domain_config() (or by whichever other means).
Jan
next prev parent reply other threads:[~2021-10-15 8:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 3:09 [PATCH v2 0/6] direct-map memory map Penny Zheng
2021-10-15 3:09 ` [PATCH v2 1/6] xen: introduce XEN_DOMCTL_CDF_directmap Penny Zheng
2021-10-15 8:46 ` Jan Beulich [this message]
2021-10-15 9:59 ` Penny Zheng
2021-10-15 10:08 ` Jan Beulich
2021-10-15 8:56 ` Julien Grall
2021-10-15 10:03 ` Penny Zheng
2021-11-09 10:05 ` Penny Zheng
2021-10-15 3:09 ` [PATCH v2 2/6] xen/arm: introduce direct-map for domUs Penny Zheng
2021-10-19 17:19 ` Julien Grall
2021-10-15 3:09 ` [PATCH v2 3/6] xen/arm: if direct-map domain use native addresses for GICv2 Penny Zheng
2021-10-19 17:39 ` Julien Grall
2021-10-15 3:09 ` [PATCH v2 4/6] xen/arm: if direct-map domain use native addresses for GICv3 Penny Zheng
2021-10-20 11:11 ` Julien Grall
2021-10-21 5:45 ` Penny Zheng
2021-10-15 3:09 ` [PATCH v2 5/6] xen/arm: if direct-map domain use native UART address and IRQ number for vPL011 Penny Zheng
2021-10-20 11:38 ` Julien Grall
2021-10-15 3:09 ` [PATCH v2 6/6] xen/docs: add a document to explain how to do passthrough without IOMMU Penny Zheng
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=073d4b36-cb2f-88b2-76d2-3438d4ef589a@suse.com \
--to=jbeulich@suse.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Wei.Chen@arm.com \
--cc=julien@xen.org \
--cc=penny.zheng@arm.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 NNTP newsgroup(s).