xen: arm: further clarify the requirement for cached mappings

We need to include all shared memory, including grant table mappings etc
in this statement.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
This commit is contained in:
Ian Campbell committed 2013-12-19 11:28:33 +00:00
1 parent 3d929ba0cd
commit 41fbf77bc8
1 file changed
+11 -4
+11 -4
View File
@@ -59,10 +59,17 @@
* used regardless of guest type. Structures which are passed as
* hypercall arguments are always little endian.
*
* All hypercall arguments passed via a pointer to guest memory must
* reside in memory which is mapped as Normal Inner-cacheable. Any
* Inner cache allocation strategy (Write-Back, Write-Through etc) is
* acceptable. There is no restriction on the Outer-cacheability.
* All memory which is shared with other entities in the system
* (including the hypervisor and other guests) must reside in memory
* which is mapped as Normal Inner-cacheable. This applies to:
* - hypercall arguments passed via a pointer to guest memory.
* - memory shared via the grant table mechanism (including PV I/O
* rings etc).
* - memory shared with the hypervisor (struct shared_info, struct
* vcpu_info, the grant table, etc).
*
* Any Inner cache allocation strategy (Write-Back, Write-Through etc)
* is acceptable. There is no restriction on the Outer-cacheability.
*/
/*
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.