From: Keir Fraser Subject: Re: [Patch] support of lock profiling in Xen Date: Tue, 13 Oct 2009 16:49:01 +0100 Message-ID: References: <4AD4870E.9090502@ts.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AD4870E.9090502@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 13/10/2009 14:56, "Juergen Gross" wrote: >> Requires a 'struct lock_profile lock_profile' or similar to be declared >> within the domain structure. No need to hide that definition within a macro >> I expect, nor to specify in advance the 'max # locks'. > > Round 3 then :-) > > I think a rw-lock is not needed, as reading is a very rare event which will > be executed in parallel less then once a year. ;-) > > Better? Yeah, this is fine I think. -- Keir