From: Keir Fraser Subject: Re: [Patch] support of lock profiling in Xen Date: Thu, 08 Oct 2009 09:40:50 +0100 Message-ID: References: <4ACDA27A.80603@ts.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4ACDA27A.80603@ts.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Juergen Gross Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 08/10/2009 09:27, "Juergen Gross" wrote: > It would even be possible to define lock arrays if summing up all data for > e.g. domain specific locks is not desired. Allowing spinlock_init() to specify not only a name but also a 'category-specific index' might be okay. For example, domid, in the case of a domain-specific lock. Hiding the allocation of profiling info structs in the spinlock subsystem somehow... (e.g., radix tree to make a simple growable array). -- Keir