From: David C Niemi <dniemi@verisign.com>
Cc: Jacob Shin <jacob.shin@amd.com>, cpufreq@vger.kernel.org
Subject: Re: New governor?
Date: Wed, 23 Jan 2013 15:42:45 -0500 [thread overview]
Message-ID: <51004B45.70209@verisign.com> (raw)
In-Reply-To: <2365004.JupvNoxXgf@vostro.rjw.lan>
On 01/23/13 14:15, Rafael J. Wysocki wrote:
> On Wednesday, January 23, 2013 01:07:12 PM Jacob Shin wrote:
>> Rafael, cpufreq list,
>>
>> I was wondering ..
>>
>> - Is hardware architecture specific governor acceptable in upstream?
>> i.e. drivers/cpufreq/cpufreq_amd_governor.c
> It generally is, although the details of implementation matter too.
>
> Thanks,
> Rafael
>
>
Intel has also been talking about hardware-specific driver/governor bundles. For now, I'd say go ahead, try to make it backwards compatible if that makes sense, and regard it as experimental. In the long run we will need to generalize what it is doing so we can once again have a higher-level, hardware-independent configuration API over the hardware-specific governors. Linux Distributions aren't going to want to use hardware-specific APIs to configure a machine, so they will likely ignore your (and Intel's) governor until there is a generic interface.
DCN
prev parent reply other threads:[~2013-01-23 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:07 New governor? Jacob Shin
2013-01-23 19:15 ` Rafael J. Wysocki
2013-01-23 20:42 ` David C Niemi [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=51004B45.70209@verisign.com \
--to=dniemi@verisign.com \
--cc=cpufreq@vger.kernel.org \
--cc=jacob.shin@amd.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