xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Dave Scott <Dave.Scott@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@citrix.com>,
	Thomas Leonard <talex5@gmail.com>,
	Anil Madhavapeddy <anil@recoil.org>
Subject: Re: mini-os: arm: grant mapping
Date: Mon, 22 Sep 2014 13:31:20 +0200	[thread overview]
Message-ID: <20140922113120.GP3486@type.bordeaux.inria.fr> (raw)
In-Reply-To: <1411384156.18331.39.camel@kazak.uk.xensource.com>

Ian Campbell, le Mon 22 Sep 2014 12:09:16 +0100, a écrit :
> On Mon, 2014-09-22 at 11:01 +0000, Dave Scott wrote:
> > I also noticed that the x86 version initialises the “demand mapping
> > area” from “max_pfn” in mm.c. I’m a bit suspicious about this on arm
> > since the grant table is being mapped in somewhere pre-ordained in the
> > device tree (If I’m reading it correctly) and there could be an
> > overlap (if we’re unlucky).
> 
> AIUI the demand mapping is for the domains own allocated memory (similar
> to COW/allocate-OW memory on a normal Unix process), not for grant
> mappings, but I may be confused.

No, we only implement COW for anonymous mmap and the BSS. "demand
mapping area" is for getting virtual address space, which is used for
mapping all kinds of things (mmap, ioremap, and here, grants).

Samuel

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

  reply	other threads:[~2014-09-22 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 11:01 mini-os: arm: grant mapping Dave Scott
2014-09-22 11:09 ` Ian Campbell
2014-09-22 11:31   ` Samuel Thibault [this message]
2014-09-22 11:34     ` Ian Campbell
2014-09-22 11:25 ` Samuel Thibault

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=20140922113120.GP3486@type.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=Dave.Scott@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Stefano.Stabellini@citrix.com \
    --cc=anil@recoil.org \
    --cc=talex5@gmail.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).