[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100611212336.GB30404@dvomlehn-lnx2.corp.sa.net>
Date: Fri, 11 Jun 2010 14:23:37 -0700
From: David VomLehn <dvomlehn@...co.com>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: to@...mlehn-lnx2.corp.sa.net, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org
Subject: Re: [PATCH 3/4 v3][RFC] Infrastructure for compact call location
representation
On Fri, Jun 11, 2010 at 01:43:00PM -0700, Randy Dunlap wrote:
> On Fri, 11 Jun 2010 13:33:56 -0700 David VomLehn wrote:
>
> > This patch allows the location of a call to be recorded as a small integer,
> > with each call location ("callsite") assigned a new value the first time
> > the code in that location is executed. Locations can be recorded as a
> > an address or as a __FILE__/__LINE__ pair. The later is easier to read, but
> > requires significantly more space.
>
> Did you happen to look at what drivers/base/power/trace.c does for callsite
> recording?
No, but at one point I did have a similar implementation working. I moved
away from it because I was leery of add yet another section to vmlinux.lds.S
for such a narrow range of functionality. If adding a section makes sense
to others, I'll do it since I felt it was overall a better solution.
--
David VL
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists