Re: [Xen-devel] [PATCH v3 36/38] altp2m: Allow specifying external-only use-case

2016-08-24 Thread Wei Liu
On Wed, Aug 17, 2016 at 12:17:12AM +0200, Sergej Proskurin wrote: > From: Tamas K Lengyel > > Currently setting altp2mhvm=1 in the domain configuration allows access to the > altp2m interface for both in-guest and external privileged tools. This poses > a problem for use-cases where only external

Re: [Xen-devel] [PATCH v3 36/38] altp2m: Allow specifying external-only use-case

2016-08-17 Thread Daniel De Graaf
On 08/16/2016 06:17 PM, Sergej Proskurin wrote: From: Tamas K Lengyel Currently setting altp2mhvm=1 in the domain configuration allows access to the altp2m interface for both in-guest and external privileged tools. This poses a problem for use-cases where only external access should be allowed,

Re: [Xen-devel] [PATCH v3 36/38] altp2m: Allow specifying external-only use-case

2016-08-17 Thread Jan Beulich
>>> On 17.08.16 at 00:17, wrote: > From: Tamas K Lengyel > > Currently setting altp2mhvm=1 in the domain configuration allows access to the > altp2m interface for both in-guest and external privileged tools. This poses > a problem for use-cases where only external access should be allowed, > re

[Xen-devel] [PATCH v3 36/38] altp2m: Allow specifying external-only use-case

2016-08-16 Thread Sergej Proskurin
From: Tamas K Lengyel Currently setting altp2mhvm=1 in the domain configuration allows access to the altp2m interface for both in-guest and external privileged tools. This poses a problem for use-cases where only external access should be allowed, requiring the user to compile Xen with XSM enable