From: Steven Rostedt <rostedt@goodmis.org>
To: tom.leiming@gmail.com
Cc: fweisbec@gmail.com, jean.pihet@newoldbits.com, mingo@redhat.com,
trenn@suse.de, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH 1/3] trace points: power: remove 'cpu_id' from trace_clock_*
Date: Fri, 19 Aug 2011 11:14:00 -0400 [thread overview]
Message-ID: <1313766840.15704.104.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1313766244-22313-1-git-send-email-tom.leiming@gmail.com>
On Fri, 2011-08-19 at 23:04 +0800, tom.leiming@gmail.com wrote:
> From: Ming Lei <tom.leiming@gmail.com>
>
> This patch removes the 'cpu_id' parameter of the clock_*
> trace point, based on the ideas below:
>
> - the cpu_id which is passed to trace point is always the current
> cpu
> - the current cpu info has been included into the trace result already
> - smp_processor_id() can't be used safely in preemptible context.
>
Do you know if these changes wont break powertop?
-- Steve
next prev parent reply other threads:[~2011-08-19 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 15:04 tom.leiming
2011-08-19 15:04 ` [PATCH 2/3] trace points: power: remove 'cpu_id' from trace_power_domain_target tom.leiming
2011-08-19 15:04 ` [PATCH 3/3] trace points: power: remove 'cpu_id' from trace_cpu_idle tom.leiming
2011-08-19 20:31 ` Thomas Renninger
2011-08-20 2:40 ` Ming Lei
2011-08-22 8:27 ` Thomas Renninger
2011-09-02 7:26 ` Jean Pihet
2011-09-02 7:38 ` Ming Lei
2011-08-19 15:14 ` Steven Rostedt [this message]
2011-08-19 15:39 ` [PATCH 1/3] trace points: power: remove 'cpu_id' from trace_clock_* Ming Lei
2011-08-19 16:16 ` Arjan van de Ven
2011-08-20 2:44 ` Ming Lei
2011-08-20 15:59 ` Arjan van de Ven
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=1313766840.15704.104.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=arjan@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tom.leiming@gmail.com \
--cc=trenn@suse.de \
/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®