From: Julien Grall <julien.grall@arm.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
george.dunlap@citrix.com, tim@xen.org,
Julien Grall <julien.grall@arm.com>,
shannon.zhao@linaro.org
Subject: [for-4.7 v2 2/2] xen/arm: Document the behavior of XENMAPSPACE_dev_mmio
Date: Wed, 25 May 2016 16:56:41 +0100 [thread overview]
Message-ID: <1464191801-1294-3-git-send-email-julien.grall@arm.com> (raw)
In-Reply-To: <1464191801-1294-1-git-send-email-julien.grall@arm.com>
Currently, XENMAPSPACE_dev_mmio maps MMIO regions using one of the most
restrictive memory attribute (Device-nGnRE).
Signed-off-by: Julien Grall <julien.grall@arm.com>
---
Changes in v2:
- s/Device_nGnRE/Device-nGnRE/ to match the spec
- Update the comment to mention the name for ARMv7.
---
xen/include/public/memory.h | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/memory.h b/xen/include/public/memory.h
index a5ab139..cfb427f 100644
--- a/xen/include/public/memory.h
+++ b/xen/include/public/memory.h
@@ -220,7 +220,11 @@ DEFINE_XEN_GUEST_HANDLE(xen_machphys_mapping_t);
#define XENMAPSPACE_gmfn_range 3 /* GMFN range, XENMEM_add_to_physmap only. */
#define XENMAPSPACE_gmfn_foreign 4 /* GMFN from another dom,
* XENMEM_add_to_physmap_batch only. */
-#define XENMAPSPACE_dev_mmio 5 /* device mmio region */
+#define XENMAPSPACE_dev_mmio 5 /* device mmio region
+ ARM only; the region will be mapped
+ in Stage-2 using the memory attribute
+ "Device-nGnRE" (previously named
+ "Device" on ARMv7) */
/* ` } */
/*
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-25 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 15:56 [for-4.7 v2 0/2] xen: XENMEM_add_to_phymap_batch: Mark 'foreign_id' as reserved for dev_mmio Julien Grall
2016-05-25 15:56 ` [for-4.7 v2 1/2] xen: XENMEM_add_to_physmap_batch: " Julien Grall
2016-05-27 9:58 ` Jan Beulich
2016-05-27 15:16 ` Julien Grall
2016-05-27 16:05 ` Jan Beulich
2016-05-25 15:56 ` Julien Grall [this message]
2016-05-27 9:51 ` [for-4.7 v2 2/2] xen/arm: Document the behavior of XENMAPSPACE_dev_mmio Jan Beulich
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=1464191801-1294-3-git-send-email-julien.grall@arm.com \
--to=julien.grall@arm.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).