From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Wei Liu" <wei.liu2@citrix.com>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
"Julien Grall" <julien.grall@linaro.org>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] libxc: introduce a per architecture scratch pfn for temporary grant mapping
Date: Wed, 14 Jan 2015 13:31:00 +0000 [thread overview]
Message-ID: <1421242260.19103.258.camel@citrix.com> (raw)
In-Reply-To: <54B66DEA.4010105@citrix.com>
On Wed, 2015-01-14 at 13:23 +0000, Andrew Cooper wrote:
> > ARM is defining a grant table range which is out of the RAM and not
> > mapped at that time. So we can reuse it with any possible issue.
>
> Do you mean to say that there is a grant table range baked into the ABI
> occupying guest physical address space?
A range of otherwise unused IPA space is suggested to the guest via the
device tree node, as a convenience for the guest so it doesn't need to
figure one out for itself (it's morally equivalent to the BAR provided
on the x86 platform PCI device).
So the actual address is not part of the guest ABI, but the toolstack
does know what it is going to be since it is privy to some internal
details of the guest layout.
Ian.
next prev parent reply other threads:[~2015-01-14 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 20:10 [PATCH] libxc: introduce a per architecture scratch pfn for temporary grant mapping Julien Grall
2015-01-14 11:03 ` Ian Campbell
2015-01-14 13:32 ` Julien Grall
2015-01-14 12:58 ` Andrew Cooper
2015-01-14 13:20 ` Julien Grall
2015-01-14 13:23 ` Andrew Cooper
2015-01-14 13:26 ` Julien Grall
2015-01-14 13:31 ` Ian Campbell [this message]
2015-01-14 13:56 ` Andrew Cooper
2015-01-15 10:45 ` Tim Deegan
2015-01-15 13:14 ` Andrew Cooper
2015-01-15 13:20 ` Julien Grall
2015-01-21 12:03 ` Julien Grall
2015-01-21 12:07 ` Andrew Cooper
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=1421242260.19103.258.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.