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

Re: [Xen-devel] [PATCH v1 3/7] mm: Use statically defined locking order

To: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Tue, 10 May 2016 15:46:05 +0100
Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
Delivery-date: Tue, 10 May 2016 14:46:54 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 06/05/16 16:48, Ross Lagerwall wrote:
> Instead of using a locking order based on line numbers which doesn't
> play nicely with xSplice, statically define the locking order.
>
> Signed-off-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx>

Along with this change, it would useful to modify the message in
__check_lock_level() to explicitly refer to mm-locks.h

The current message is very obscure to anyone who doesn't know about
mm-locks.h

~Andrew

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

References:
- [Xen-devel] [PATCH v1 0/7] Make building xSplice patches easier
  - From: Ross Lagerwall
- [Xen-devel] [PATCH v1 3/7] mm: Use statically defined locking order
  - From: Ross Lagerwall

Prev by Date: Re: [Xen-devel] [PATCH v1 4/7] page-alloc: Remove dependency on __LINE__ for release builds
Next by Date: Re: [Xen-devel] [PATCH v1 5/7] iommu: Remove dependency on __LINE__ for release builds
Previous by thread: Re: [Xen-devel] [PATCH v1 3/7] mm: Use statically defined locking order
Next by thread: [Xen-devel] [PATCH v1 1/7] lib: Add a generic implementation of current_text_addr()
Index(es):
- Date
- Thread

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