lockmeter
[Top] [All Lists]

Re: Lockmetering a custom kernel module

To: <lockmeter@xxxxxxxxxxx>, "Florian Boelstler" <euphoria@xxxxxxxx>
Subject: Re: Lockmetering a custom kernel module
From: "John Hawkes" <jrhawkes@xxxxxxxxx>
Date: Fri, 25 Aug 2006 15:11:00 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=Mt9g0YW59lplgnWsep1QNU7DUHm4a3DIAWu/rysLhrUpa5QaClVOkHFGmHsEowolDewzea3Izzb5mr5UVxEAecvvNbsOch2N5ZGkPMfAXGlco4UYjt9m0+ZynlfowIPiRGpi1absStEhOPEhSmgcoDITscqmaFTdozQ3eoZ2bG8= ;
References: <eckhpr$o1u$1@sea.gmane.org> <ecknka$es5$1@sea.gmane.org>
Sender: lockmeter-bounce@xxxxxxxxxxx
From: "Florian Boelstler" <euphoria@xxxxxxxx>
Florian Boelstler schrieb:
Is it really true that lockmeter does not work for kernel modules loaded at runtime? Or is it "hidden" behind some symbol denoted by an address?

Just wanted to let you know that when the driver is built into the kernel I get all expected spinlock profiles.

Yes, this is true. An already-built kernel module was compiled against the unpatched versions of routines like spin_lock() and spin_unlock() which don't perform any lockmetering. It seems to me that a kernel module that is compiled against lockmeter-patched kernel source should link to the lockmeter'ing locking/unlocking routines. Are you saying that these post-patch-built modules do not 'meter' correctly, either?


John Hawkes


<Prev in Thread] Current Thread [Next in Thread>