Re: [Xen-devel] [PATCH v2 1/2] x86/altp2m: use __get_gfn_type_access to avoid lock conflicts

2016-09-06 Thread George Dunlap
On Wed, Aug 10, 2016 at 4:00 PM, Tamas K Lengyel wrote: > From: Tamas K Lengyel > > Use __get_gfn_type_access instead of get_gfn_type_access when checking > the hostp2m entries during altp2m mem_access setting and gfn remapping > to avoid a lock

Re: [Xen-devel] [PATCH v2 1/2] x86/altp2m: use __get_gfn_type_access to avoid lock conflicts

2016-08-31 Thread Tamas K Lengyel
On Thu, Aug 11, 2016 at 5:57 AM, Jan Beulich wrote: On 10.08.16 at 17:00, wrote: >> From: Tamas K Lengyel >> >> Use __get_gfn_type_access instead of get_gfn_type_access when checking >> the hostp2m entries during altp2m

Re: [Xen-devel] [PATCH v2 1/2] x86/altp2m: use __get_gfn_type_access to avoid lock conflicts

2016-08-11 Thread Jan Beulich
>>> On 10.08.16 at 17:00, wrote: > From: Tamas K Lengyel > > Use __get_gfn_type_access instead of get_gfn_type_access when checking > the hostp2m entries during altp2m mem_access setting and gfn remapping > to avoid a lock conflict which can make

[Xen-devel] [PATCH v2 1/2] x86/altp2m: use __get_gfn_type_access to avoid lock conflicts

2016-08-10 Thread Tamas K Lengyel
From: Tamas K Lengyel Use __get_gfn_type_access instead of get_gfn_type_access when checking the hostp2m entries during altp2m mem_access setting and gfn remapping to avoid a lock conflict which can make dom0 freeze. During mem_access setting the hp2m is already locked. For