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

Re: [Xen-devel] [PATCH v2] Don't take the domain lock for p2m operations.

To: Tim Deegan <tim@xxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Mon, 29 Jul 2013 16:10:28 +0100
Cc: stefano.stabellini@xxxxxxxxxx, ian.campbell@xxxxxxxxxx, jbeulich@xxxxxxxx, andres@xxxxxxxxxxxxxxxx
Delivery-date: Mon, 29 Jul 2013 15:10:51 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>
Thread-index: Ac6MbcJVZFV1i2bWlUSoGQbX7l8Xnw==
Thread-topic: [PATCH v2] Don't take the domain lock for p2m operations.

On 29/07/2013 15:06, "Tim Deegan" <tim@xxxxxxx> wrote:

> P2M ops are covered by their own locks, and these uses of the domain
> lock are relics of shadow-v1 code.
> 
> Signed-off-by: Tim Deegan <tim@xxxxxxx>
> ---
> v2: also drop a domain_lock() from ARM mm code.

Acked-by: Keir Fraser <keir@xxxxxxx>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v2] Don't take the domain lock for p2m operations.
  - From: Tim Deegan

Prev by Date: Re: [Xen-devel] [PATCH 3/3] xen/arm: errata 766422: decode thumb store during data abort
Next by Date: Re: [Xen-devel] [PATCH] xen: arm: remove unnecessary cache flush in write_pte
Previous by thread: Re: [Xen-devel] [PATCH v2] Don't take the domain lock for p2m operations.
Index(es):
- Date
- Thread

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