From: David Miller <davem@davemloft.net>
To: jbaron@redhat.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
mathieu.desnoyers@polymtl.ca, hpa@zytor.com, tglx@linutronix.de,
rostedt@goodmis.org, andi@firstfloor.org, roland@redhat.com,
rth@redhat.com, mhiramat@redhat.com, fweisbec@gmail.com,
avi@redhat.com, vgoyal@redhat.com, sam@ravnborg.org,
tony@bakeyournoodle.com
Subject: Re: [PATCH 06/12] jump label v10: convert jump label to use a key
Date: Wed, 28 Jul 2010 13:37:05 -0700 (PDT) [thread overview]
Message-ID: <20100728.133705.85435354.davem@davemloft.net> (raw)
In-Reply-To: <1d0369680bbab87acfef5499e479bdc6d991ebea.1280263065.git.jbaron@redhat.com>
From: Jason Baron <jbaron@redhat.com>
Date: Tue, 27 Jul 2010 16:54:32 -0400
> Convert the jump label code to use a key to identify each related set of
> jump labels instead of a string. This saves space since we no longer need
> to store strings and their pointers, just the keys. In addition we can
> simplify the JUMP_LABEL macro to 2 arguments from 3. We use the address
> of the conditional variable as the key value. If jump labels are not enabled
> then we can use the conditional variable as usual.
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
It doesn't make any sense to present these changes like this.
If the final implementation of the jump label entries uses this new
key based scheme, well that's what should be in the first patch of
this series which adds the basic jump label infrastructure.
As it is, it's just commit noise.
next prev parent reply other threads:[~2010-07-28 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 20:53 [PATCH 00/12] jump label v10 Jason Baron
2010-07-27 20:54 ` [PATCH 01/12] jump label v10: base patch Jason Baron
2010-07-27 20:54 ` [PATCH 02/12] jump label v10: add module support Jason Baron
2010-07-27 20:54 ` [PATCH 03/12] jump label v10: move ftrace_dyn_arch_init to common code Jason Baron
2010-07-27 20:54 ` [PATCH 04/12] jump label v10: initialize workqueue tracepoints *before* they are registered Jason Baron
2010-07-27 20:54 ` [PATCH 05/12] jump label v10: jump_label_text_reserved() to reserve our jump points Jason Baron
2010-07-27 20:54 ` [PATCH 06/12] jump label v10: convert jump label to use a key Jason Baron
2010-07-28 20:37 ` David Miller [this message]
2010-07-27 20:54 ` [PATCH 07/12] jump label v10: use lib/sort.c Jason Baron
2010-07-28 20:40 ` David Miller
2010-07-27 20:54 ` [PATCH 08/12] jump label v10: tracepoint support Jason Baron
2010-07-27 20:54 ` [PATCH 09/12] jump label v10: convert dynamic debug to use jump labels Jason Baron
2010-07-27 20:54 ` [PATCH 10/12] jump label v10: x86 support Jason Baron
2010-07-27 20:54 ` [PATCH 11/12] jump label v10: add sparc64 support Jason Baron
2010-07-27 20:54 ` [PATCH 12/12] jump label v10: add docs Jason Baron
2010-07-28 19:34 ` [PATCH 00/12] jump label v10 David Miller
2010-07-28 20:14 ` Jason Baron
2010-07-28 20:24 ` David Miller
2010-07-28 20:42 ` Jason Baron
2010-07-28 21:09 ` David Miller
2010-07-29 5:25 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100728.133705.85435354.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=tony@bakeyournoodle.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome