From: Steven Rostedt <rostedt@goodmis.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Avi Kivity <avi@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] tracepoints: Move the work out of line from hotpath sections
Date: Thu, 09 Aug 2012 21:41:26 -0400 [thread overview]
Message-ID: <1344562886.6935.93.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <50244D9A.2070000@gmail.com>
On Thu, 2012-08-09 at 16:54 -0700, David Daney wrote:
> On 08/09/2012 04:16 PM, H. Peter Anvin wrote:
> > On 08/09/2012 03:25 PM, Steven Rostedt wrote:
> >>>
> >>> It might be better to improve gcc to move really cold branches out of
> >>> line (really, really far away), and use the compiler to do this, rather
> >>> than to use an extra indirection that adds bloat and complexity to the
> >>> kernel.
>
> Oh, you mean like: -freorder-blocks-and-partition
Actually, what would be really nice is to place a block in a section of
your choice. Something like:
if (unlikely(x)) __attribute__((section(".unlikely"))) {
/* code here will be in the ".unlikely" section */
}
-- Steve
next prev parent reply other threads:[~2012-08-10 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 20:40 Steven Rostedt
2012-08-09 20:50 ` Mathieu Desnoyers
2012-08-09 22:25 ` Steven Rostedt
2012-08-09 23:16 ` H. Peter Anvin
2012-08-09 23:54 ` David Daney
2012-08-10 1:41 ` Steven Rostedt [this message]
2012-08-10 2:05 ` Mathieu Desnoyers
2012-08-10 3:09 ` Steven Rostedt
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=1344562886.6935.93.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=ddaney.cavm@gmail.com \
--cc=hch@infradead.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®