From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] perfcounter fixes
Date: Thu, 6 Aug 2009 05:26:04 +0200 [thread overview]
Message-ID: <20090806032603.GD25478@erda.amd.com> (raw)
In-Reply-To: <20090804191832.GA2020@elte.hu>
On 04.08.09 21:18:32, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest perfcounters-fixes-for-linus git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git perfcounters-fixes-for-linus
>
> Note, i was unsure about this commit:
>
> f265426: perf_counter: Set the CONFIG_PERF_COUNTERS default to y if CONFIG_PROFILING=y
>
> Is it proper to offer up a default-y if CONFIG_PROFILING is set to y
> already and default-off otherwise?
>
> I kept this the last commit so we can zap it easily if it's not ok.
>
> Thanks,
>
> Ingo
>
> ------------------>
> Arnaldo Carvalho de Melo (1):
> perf top: Add mwait_idle_with_hints to skip_symbols[]
>
> Ingo Molnar (2):
> perf_counter tools: Fix link errors with older toolchains
> perf_counter: Set the CONFIG_PERF_COUNTERS default to y if CONFIG_PROFILING=y
Setting CONFIG_PERF_COUNTERS=y per default for -rc6? Wouldn't this be
something for the next merge window? Give people the chance to test
this, changing default configurations shouln't be made this late in
the release cycle.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
prev parent reply other threads:[~2009-08-06 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 19:18 [GIT PULL] perfcounter fixes Ingo Molnar
2009-08-06 3:26 ` Robert Richter [this message]
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=20090806032603.GD25478@erda.amd.com \
--to=robert.richter@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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