[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1 of 6] REDO: mem_access & mem_access 2: introduce P2M mem_access types



At 22:07 +0000 on 04 Jan (1294178829), Joe Epstein wrote:
> * Introduces access types for each page, giving independent read, write, and
>   execute permissions for each page.  The permissions are restrictive from
>   what the page type gives: for example, a p2m_type_ro page with an access of
>   p2m_access_rw would have read-only permissions in total, as p2m_type_ro
>   removed write access and p2m_access_rw removed execute access.
> 
> * Implements the access flag storage for EPT, moving some bits from P2M type,
>   which had 10 bits of storage, to the four bits for access.
> 
> * Access flags are stored according to a loose consistency contract, where
>   pages can be reset to the default access permissions at any time.  Right
>   now, that happens on page type changes, where one would want to reevaluate
>   whether permissions make sense for that page as they are anyway.
> 
> Signed-off-by: Joe Epstein <jepstein98@xxxxxxxxx>

I won't apply this until the rest of the series is ready, but:
Acked-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.