[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290614246.30543.536.camel@gandalf.stny.rr.com>
Date: Wed, 24 Nov 2010 10:57:26 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jason Baron <jbaron@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>, mingo@...e.hu,
mathieu.desnoyers@...ymtl.ca, hpa@...or.com, tglx@...utronix.de,
andi@...stfloor.org, roland@...hat.com, rth@...hat.com,
masami.hiramatsu.pt@...achi.com, fweisbec@...il.com,
avi@...hat.com, davem@...emloft.net, sam@...nborg.org,
ddaney@...iumnetworks.com, michael@...erman.id.au,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] jump label: add enabled/disabled state to jump
label key entries
On Wed, 2010-11-24 at 10:21 -0500, Jason Baron wrote:
> The keys are simply the address of a variable or structure (so as to be
> unique). We can put pointers or anything else in the variable.
Note, there is not a 1 to 1 with keys and places that need to be
patched.
Doing the following objdump:
objdump -dr vmlinux | grep 'jmpq.*<trace_kmalloc' | wc -l
375
That's 375 instances of kmalloc tracepoints[*] and one key. How do you
handle this?
-- Steve
[*] this should be fixed, we probably should find a way to move the
tracepoint into the kmalloc functions that are not inlined.
--
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