Re: [Xen-devel] Alternate p2m design specification

2015-06-11 Thread Ed White
On 06/11/2015 12:05 AM, Jan Beulich wrote: On 10.06.15 at 18:39, wrote: >> On 06/10/2015 12:43 AM, Jan Beulich wrote: >> On 10.06.15 at 02:09, wrote: Design == >>> >>> Reads all quite reasonable; just one minor remark: >>> - Core altp2m functionality A new al

Re: [Xen-devel] Alternate p2m design specification

2015-06-11 Thread Ed White
On 06/11/2015 05:06 AM, Tim Deegan wrote: > At 00:09 +0100 on 11 Jun (1433981379), Andrew Cooper wrote: >> On 10/06/15 20:41, Ed White wrote: >>> On 06/10/2015 11:23 AM, Andrew Cooper wrote: Also, hardware accelerated altp2m is mutually exclusive with EPT PML, as we have no way of determi

Re: [Xen-devel] Alternate p2m design specification

2015-06-11 Thread Tim Deegan
At 00:09 +0100 on 11 Jun (1433981379), Andrew Cooper wrote: > On 10/06/15 20:41, Ed White wrote: > > On 06/10/2015 11:23 AM, Andrew Cooper wrote: > >> Also, hardware accelerated altp2m is mutually exclusive with EPT PML, as > >> we have no way of determining which translation was in use when a gpa

Re: [Xen-devel] Alternate p2m design specification

2015-06-11 Thread Jan Beulich
>>> On 10.06.15 at 18:39, wrote: > On 06/10/2015 12:43 AM, Jan Beulich wrote: > On 10.06.15 at 02:09, wrote: >>> Design >>> == >> >> Reads all quite reasonable; just one minor remark: >> >>> - Core altp2m functionality >>> >>> A new altp2m type is added to the p2m types (in addition to

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Andrew Cooper
On 10/06/15 20:41, Ed White wrote: > On 06/10/2015 11:23 AM, Andrew Cooper wrote: >> On 10/06/15 01:09, Ed White wrote: >>> This document describes a new capability for VM Introspection, Security and >>> Privacy in Xen. The new capability is called “altp2m” (short for Alternate >>> p2m) that is u

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Ed White
On 06/10/2015 04:09 PM, Andrew Cooper wrote: > On 10/06/15 20:41, Ed White wrote: >> On 06/10/2015 11:23 AM, Andrew Cooper wrote: >>> On 10/06/15 01:09, Ed White wrote: This document describes a new capability for VM Introspection, Security and Privacy in Xen. The new capability is calle

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Ed White
On 06/10/2015 11:23 AM, Andrew Cooper wrote: > On 10/06/15 01:09, Ed White wrote: >> This document describes a new capability for VM Introspection, Security and >> Privacy in Xen. The new capability is called “altp2m” (short for Alternate >> p2m) that is used to provide the ability for Xen to hos

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Andrew Cooper
On 10/06/15 01:09, Ed White wrote: > This document describes a new capability for VM Introspection, Security and > Privacy in Xen. The new capability is called “altp2m” (short for Alternate > p2m) that is used to provide the ability for Xen to host alternate guest > physical memory domains for a

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Ed White
On 06/10/2015 12:43 AM, Jan Beulich wrote: On 10.06.15 at 02:09, wrote: >> Design >> == > > Reads all quite reasonable; just one minor remark: > >> - Core altp2m functionality >> >> A new altp2m type is added to the p2m types (in addition to the previous >> hostp2m and nestedp2m types)

Re: [Xen-devel] Alternate p2m design specification

2015-06-10 Thread Jan Beulich
>>> On 10.06.15 at 02:09, wrote: > Design > == Reads all quite reasonable; just one minor remark: > - Core altp2m functionality > > A new altp2m type is added to the p2m types (in addition to the previous > hostp2m and nestedp2m types). An HVM domain can be started in hostp2m mode > and s