All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: 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 16:54:02 -0700	[thread overview]
Message-ID: <50244D9A.2070000@gmail.com> (raw)
In-Reply-To: <502444CC.8030906@linux.intel.com>

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

>>
>> I think modifying gcc is something that can help more than tracing. But
>> that's been a pipe dream for such a long time that I've started dreaming
>> about winning a gold medal in the Olympics instead. Standing on the
>> podium listening to the crowd chanting your name along with your country
>> is more fun to dream about than seeing your unlikely code stop becoming
>> hurdles for the CPU sprinters.
>>
>
> At one point, maybe, but lately we have had a lot more traction from the
> gcc developers, giving us features like __fentry__ and asm goto.
>

I don't claim that -freorder-blocks-and-partition is bug free, but I 
imagine that the GCC developers would be open to fixing any bugs found.

David Daney


  reply	other threads:[~2012-08-09 23:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 20:40 [RFC][PATCH] tracepoints: Move the work out of line from hotpath sections 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 [this message]
2012-08-10  1:41         ` Steven Rostedt
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=50244D9A.2070000@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.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=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.