From: Dave Jones <davej@redhat.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
stefano.stabellini@eu.citrix.com, Ian.Jackson@eu.citrix.com,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Is: drivers/cpufreq/cpufreq-xen.c Was:Re: [PATCH 2 of 2] linux-xencommons: Load processor-passthru
Date: Tue, 6 Mar 2012 12:59:48 -0500 [thread overview]
Message-ID: <20120306175948.GA6656@redhat.com> (raw)
In-Reply-To: <CAPbh3ru2wGLiGC7FxZGUP59CiqaEim-7_-iT-BYwoOgB2QTG=g@mail.gmail.com>
On Tue, Mar 06, 2012 at 12:40:08PM -0500, Konrad Rzeszutek Wilk wrote:
> I think what you are suggesting is that to write a driver in drivers/cpufreq/
> that gets either started before the other ones (if built-in) or if as
> a module gets
> loaded from xencommons. That driver would then make the call
> to acpi_processor_preregister_performance(),
> acpi_processor_register_performance() and acpi_processor_notify_smm().
> It would function as a cpufreq-scaling driver but
> in reality all calls to it from cpufreq gov-* drivers would end up with nop.
>
> Dave, would you be Ok with a driver like that in your tree?
I joined this thread half-way through, so I'm not sure what the original problem was.
How is a driver that does nothing better than just masking out the cpufreq capabilities to guests ?
Dave
next prev parent reply other threads:[~2012-03-06 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:40 Is: drivers/cpufreq/cpufreq-xen.c Was:Re: [PATCH 2 of 2] linux-xencommons: Load processor-passthru Konrad Rzeszutek Wilk
2012-03-06 17:59 ` Dave Jones [this message]
2012-03-08 2:12 ` Konrad Rzeszutek Wilk
2012-03-13 16:46 ` Konrad Rzeszutek Wilk
2012-03-07 8:18 ` Jan Beulich
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=20120306175948.GA6656@redhat.com \
--to=davej@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).