|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v5 09/17] xen/arm: p2m type definitions and changes
Hi Tamas, You skipped my comments/questions on v4. On 10/09/14 06:28, Tamas K Lengyel wrote: diff --git a/xen/include/asm-arm/p2m.h b/xen/include/asm-arm/p2m.h index 08ce07b..b4ca86d 100644 --- a/xen/include/asm-arm/p2m.h +++ b/xen/include/asm-arm/p2m.h @@ -2,6 +2,9 @@ [..] +#include <public/memory.h> +#include <public/mem_event.h> Why do you need those 2 includes? Any reason to move the enum earlier? If not, I would prefer to keep at the same place. It will be easier with git-blame to find when a new type has been added. +/* + * Additional access types, which are used to further restrict + * the permissions given by the p2m_type_t memory type. Violations + * caused by p2m_access_t restrictions are sent to the mem_event + * interface. + * + * The access permissions are soft state: when any ambigious change of page ambiguous. [..] + /* Default P2M access type for each page in the the domain: new pages, + * swapped in pages, cleared pages, and pages that are ambiquously Did you intend to mean ambiguously rather than ambiquously? [..] +/* mem_event and mem_access are supported on all ARM */ I don't find "all ARM" clear. I would replace by "any ARM guest" Regards, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |