mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: mingo@elte.hu, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing - enabling "__cold" functions
Date: Mon, 12 Oct 2009 13:19:17 +0200	[thread overview]
Message-ID: <20091012111917.GA6934@jolsa.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <1255104899-27784-1-git-send-email-jolsa@redhat.com>

any feedback on this one?

thanks,
jirka

On Fri, Oct 09, 2009 at 06:14:59PM +0200, jolsa@redhat.com wrote:
> Based on the commit:
> 
> a586df06 "x86: Support __attribute__((__cold__)) in gcc 4.3"
> 
> some of the functions goes to the ".text.unlikely" section.
> 
> Looks like there's not many of them (I found printk, panic,
> __ssb_dma_not_implemented, fat_fs_error), but still worth
> to include I think.
> 
> wbr,
> jirka
> 
> 
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> ---
>  scripts/recordmcount.pl |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
> index 090d300..bfb8b2c 100755
> --- a/scripts/recordmcount.pl
> +++ b/scripts/recordmcount.pl
> @@ -119,6 +119,7 @@ my %text_sections = (
>       ".sched.text" => 1,
>       ".spinlock.text" => 1,
>       ".irqentry.text" => 1,
> +     ".text.unlikely" => 1,
>  );
>  
>  $objdump = "objdump" if ((length $objdump) == 0);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2009-10-12 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 16:14 jolsa
2009-10-12 11:19 ` Jiri Olsa [this message]
2009-10-12 11:27   ` Ingo Molnar
2009-10-12 11:39     ` Jiri Olsa
2009-10-12 13:48       ` 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=20091012111917.GA6934@jolsa.lab.eng.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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®