Hi Stefano,
On 26/05/2016 10:18, Stefano Stabellini wrote:
On Wed, 25 May 2016, Julien Grall wrote:
On 25/05/16 14:14, Jan Beulich wrote:
Also - is Device_nGnRE a term uniform between ARM32 and ARM64?
Actually it should be Device-nGnRE to match with the spec. This has been
introduced on Armv
On Wed, 25 May 2016, Julien Grall wrote:
> Hi Jan,
>
> On 25/05/16 14:14, Jan Beulich wrote:
> > > > > On 25.05.16 at 13:41, wrote:
> > > --- a/xen/include/public/memory.h
> > > +++ b/xen/include/public/memory.h
> > > @@ -220,7 +220,10 @@ DEFINE_XEN_GUEST_HANDLE(xen_machphys_mapping_t);
> > > #
>>> On 25.05.16 at 16:43, wrote:
> I could say:
>
> "ARM only; the region will be mapped in Stage-2 using the memory
> attribute 'Device-nGnRE' (previously named 'Device' on ARMv7)".
SGTM
Jan
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http:
Hi Jan,
On 25/05/16 14:14, Jan Beulich wrote:
On 25.05.16 at 13:41, wrote:
--- a/xen/include/public/memory.h
+++ b/xen/include/public/memory.h
@@ -220,7 +220,10 @@ DEFINE_XEN_GUEST_HANDLE(xen_machphys_mapping_t);
#define XENMAPSPACE_gmfn_range 3 /* GMFN range, XENMEM_add_to_physmap only.
>>> On 25.05.16 at 13:41, wrote:
> --- a/xen/include/public/memory.h
> +++ b/xen/include/public/memory.h
> @@ -220,7 +220,10 @@ DEFINE_XEN_GUEST_HANDLE(xen_machphys_mapping_t);
> #define XENMAPSPACE_gmfn_range 3 /* GMFN range, XENMEM_add_to_physmap
> only. */
> #define XENMAPSPACE_gmfn_foreig
Currently, XENMAPSPACE_dev_mmio maps MMIO regions using one of the most
restrictive memory attribute (Device_nGnRE).
Signed-off-by: Julien Grall
---
xen/include/public/memory.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/xen/include/public/memory.h b/xen/include/publi
