From: Borislav Petkov <bp@alien8.de>
To: Jacob Shin <jacob.shin@amd.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCH V4 2/2] cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor
Date: Thu, 4 Apr 2013 21:23:23 +0200 [thread overview]
Message-ID: <20130404192323.GI32271@pd.tnic> (raw)
In-Reply-To: <1365092344-11310-3-git-send-email-jacob.shin@amd.com>
On Thu, Apr 04, 2013 at 11:19:04AM -0500, Jacob Shin wrote:
> Future AMD processors, starting with Family 16h, can provide software
> with feedback on how the workload may respond to frequency change --
> memory-bound workloads will not benefit from higher frequency, where
> as compute-bound workloads will. This patch enables this "frequency
> sensitivity feedback" to aid the ondemand governor to make better
> frequency change decisions by hooking into the powersave bias.
>
> Signed-off-by: Jacob Shin <jacob.shin@amd.com>
Looks good to me.
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-04-04 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:19 [PATCH V4 0/2] cpufreq: ondemand: add AMD specific powersave bias Jacob Shin
2013-04-04 16:19 ` [PATCH V4 1/2] cpufreq: ondemand: allow custom powersave_bias_target handler to be registered Jacob Shin
2013-04-04 16:36 ` Viresh Kumar
2013-04-04 17:18 ` Jacob Shin
2013-04-04 19:12 ` Borislav Petkov
2013-04-04 20:28 ` Jacob Shin
2013-04-04 21:32 ` Borislav Petkov
2013-04-04 16:19 ` [PATCH V4 2/2] cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor Jacob Shin
2013-04-04 19:23 ` Borislav Petkov [this message]
2013-04-04 20:29 ` Jacob Shin
2013-04-04 16:42 ` [PATCH V4 0/2] cpufreq: ondemand: add AMD specific powersave bias Thomas Renninger
2013-04-05 4:49 ` Viresh Kumar
2013-04-05 6:49 ` Viresh Kumar
2013-04-05 11:55 ` Rafael J. Wysocki
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=20130404192323.GI32271@pd.tnic \
--to=bp@alien8.de \
--cc=cpufreq@vger.kernel.org \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
--cc=viresh.kumar@linaro.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