From: Thomas Renninger <trenn@suse.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: "Robert Schöne" <robert.schoene@tu-dresden.de>,
"Dave Jones" <davej@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
cpufreq <cpufreq@vger.kernel.org>,
x86@kernel.org
Subject: Re: [PATCH] trace power_frequency events on the correct cpu (for Intel x86 CPUs)
Date: Thu, 18 Mar 2010 21:43:22 +0100 [thread overview]
Message-ID: <201003182143.22929.trenn@suse.de> (raw)
In-Reply-To: <4BA10642.8070208@linux.intel.com>
On Wednesday 17 March 2010 05:41:38 pm Arjan van de Ven wrote:
> On 3/17/2010 9:36, Thomas Renninger wrote:
> > On Tuesday 16 March 2010 17:40:18 Arjan van de Ven wrote:
> >> On 3/16/2010 7:50, Thomas Renninger wrote:
> >>> Still, as this is totally broken:
> >>> - by design -> only one of a dozen cpufreq drivers is supported
> >>
> >> the one I care about is supported.
> >
> > And that's the problem, before it's not removed, you do not care to
> > provide/suggest a proper solution that could fit others as well.
>
> why don't you provide the others then?
Is it possible somehow to provide a kind of wrapper/backup function:
trace_power_frequency_cpu(POWER_PSTATE, frequency, cpu);
or another trace interface with eventually some more overhead?
Then it should be easy to support all drivers.
Otherwise you'll for example miss the pcc driver which supports
latest/upcoming Intel CPUs and which does IO based switching which needs not
to run on the cpu that gets switched.
Thomas
next prev parent reply other threads:[~2010-03-18 20:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 13:17 Robert Schöne
2010-03-12 14:52 ` Arjan van de Ven
2010-03-12 15:41 ` Robert Schöne
2010-03-15 10:51 ` Thomas Renninger
2010-03-16 7:13 ` Robert Schöne
2010-03-16 9:57 ` Ingo Molnar
2010-03-16 10:59 ` Thomas Renninger
2010-03-16 14:19 ` Arjan van de Ven
2010-03-16 14:50 ` Thomas Renninger
2010-03-16 16:40 ` Arjan van de Ven
2010-03-17 16:36 ` Thomas Renninger
2010-03-17 16:41 ` Arjan van de Ven
2010-03-18 20:43 ` Thomas Renninger [this message]
2010-03-19 8:01 ` Robert Schöne
2010-03-20 21:37 ` Thomas Renninger
2010-03-22 0:42 ` Arjan van de Ven
2010-03-22 7:04 ` Robert Schöne
2010-03-22 13:57 ` Arjan van de Ven
2010-03-23 16:28 ` Robert Schöne
2010-03-23 16:57 ` Thomas Renninger
2010-03-23 16:58 ` Arjan van de Ven
2010-03-24 7:07 ` Robert Schöne
2010-03-30 5:46 ` Robert Schöne
2010-03-30 8:56 ` Thomas Renninger
2010-03-31 6:40 ` Robert Schöne
2010-04-12 6:53 ` Robert Schöne
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=201003182143.22929.trenn@suse.de \
--to=trenn@suse.de \
--cc=arjan@linux.intel.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robert.schoene@tu-dresden.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome