xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] public: there's no MMUEXT_SET_FOREIGNDOM
Date: Fri, 9 Jun 2017 14:20:58 +0100	[thread overview]
Message-ID: <e9c679de-01a6-440d-f009-ad419682f4fa@arm.com> (raw)
In-Reply-To: <593987070200007800160EE5@prv-mh.provo.novell.com>

Hi Jan,

On 08/06/17 16:19, Jan Beulich wrote:
> Correct respective comments.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> MMUEXT_{CLEAR,COPY}_PAGE in fact also allow to be invoked on DOMID_IO
> owned pages at present. I've intentionally not added this to the text,
> as I'm not sure we really mean to allow this. If we do, I think the
> operation should also be allowed for MMIO pages not happening to have
> an associated struct page_info.
>
> --- a/xen/include/public/xen.h
> +++ b/xen/include/public/xen.h
> @@ -550,16 +550,19 @@ DEFINE_XEN_GUEST_HANDLE(mmuext_op_t);
>   * is useful to ensure that no mappings to the OS's own heap are accidentally
>   * installed. (e.g., in Linux this could cause havoc as reference counts
>   * aren't adjusted on the I/O-mapping code path).
> - * This only makes sense in MMUEXT_SET_FOREIGNDOM, but in that context can
> - * be specified by any calling domain.
> + * This only makes sense as HYPERVISOR_mmu_update()'s and
> + * HYPERVISOR_update_va_mapping_otherdomain()'s "foreigndom" argument. For
> + * HYPERVISOR_mmu_update() context it can be specified by any calling domain,
> + * otherwise it's only permitted if the caller is privileged.
>   */
>  #define DOMID_IO             xen_mk_uint(0x7FF1)
>
>  /*
>   * DOMID_XEN is used to allow privileged domains to map restricted parts of
>   * Xen's heap space (e.g., the machine_to_phys table).
> - * This only makes sense in MMUEXT_SET_FOREIGNDOM, and is only permitted if
> - * the caller is privileged.
> + * This only makes sense as HYPERVISOR_mmu_update()'s, HYPERVISOR_mmuext_op()'s,
> + * or HYPERVISOR_update_va_mapping_otherdomain()'s "foreigndom" argument, and is
> + * only permitted if the caller is privileged.

DOMID_XEN is used on ARM for mapping Xen buffer (e.g trace) using 
physmap hypercall with XENMAPSPACE_foreign_gmfn_foreign.


>   */
>  #define DOMID_XEN            xen_mk_uint(0x7FF2)

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-06-09 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 15:19 [PATCH] public: there's no MMUEXT_SET_FOREIGNDOM Jan Beulich
2017-06-09 12:29 ` Andrew Cooper
2017-06-09 12:50   ` Jan Beulich
2017-06-09 13:20 ` Julien Grall [this message]
2017-06-09 13:24   ` Julien Grall

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=e9c679de-01a6-440d-f009-ad419682f4fa@arm.com \
    --to=julien.grall@arm.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@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 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).