From: Boris Ostrovsky <boris.ostrovsky@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] AMD, powernow: Update P-state directly when _PSD's CoordType is DOMAIN_COORD_TYPE_HW_ALL
Date: Fri, 17 Aug 2012 09:50:50 -0400 [thread overview]
Message-ID: <502E4C3A.5050409@amd.com> (raw)
In-Reply-To: <502E399B0200007800095DA1@nat28.tlf.novell.com>
On 08/17/2012 06:31 AM, Jan Beulich wrote:
>>>> On 16.08.12 at 18:41, Boris Ostrovsky <boris.ostrovsky@amd.com> wrote:
>> @@ -137,26 +122,28 @@ static int powernow_cpufreq_target(struc
>> return 0;
>> }
>>
>> - if (policy->shared_type != CPUFREQ_SHARED_TYPE_ANY)
>> - cmd.mask = &online_policy_cpus;
>> - else
>> - cmd.mask = cpumask_of(policy->cpu);
>> + if (policy->shared_type == CPUFREQ_SHARED_TYPE_HW &&
>> + likely(policy->cpu == smp_processor_id())) {
>> + transition_pstate(&next_perf_state);
>> + cpufreq_statistic_update(policy->cpu, perf->state, next_perf_state);
>
> Actually - is this enough? Doesn't this also need to be done based
> on policy->cpus?
With HW-coordinated transitions there is a policy structure per CPU so
policy->cpus is always 1 and policy->cpu is the same as policy->cpus.
You can see this in cpufreq_add_cpu(), when hw_all is set.
(This is consistent with ACPI spec:
When hardware coordinates transitions, OSPM continues to
initiate state transitions as it would if there were no
dependencies.
)
-boris
>
> Jan
>
>> + } else {
>> + cpumask_and(&online_policy_cpus, policy->cpus, &cpu_online_map);
>>
>> - freqs.old = perf->states[perf->state].core_frequency * 1000;
>> - freqs.new = data->freq_table[next_state].frequency;
>> + if (policy->shared_type == CPUFREQ_SHARED_TYPE_ALL ||
>> + unlikely(policy->cpu != smp_processor_id()))
>> + on_selected_cpus(&online_policy_cpus, transition_pstate,
>> + &next_perf_state, 1);
>> + else
>> + transition_pstate(&next_perf_state);
>>
>> - cmd.val = next_perf_state;
>> - cmd.turbo = policy->turbo;
>> -
>> - on_selected_cpus(cmd.mask, transition_pstate, &cmd, 1);
>> -
>> - for_each_cpu(j, &online_policy_cpus)
>> - cpufreq_statistic_update(j, perf->state, next_perf_state);
>> + for_each_cpu(j, &online_policy_cpus)
>> + cpufreq_statistic_update(j, perf->state, next_perf_state);
>> + }
>>
>> perf->state = next_perf_state;
>> - policy->cur = freqs.new;
>> + policy->cur = data->freq_table[next_state].frequency;
>>
>> - return result;
>> + return 0;
>> }
>>
>> static int powernow_cpufreq_verify(struct cpufreq_policy *policy)
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
>
>
>
next prev parent reply other threads:[~2012-08-17 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 16:41 [PATCH] AMD, powernow: Update P-state directly when _PSD's CoordType is DOMAIN_COORD_TYPE_HW_ALL Boris Ostrovsky
2012-08-17 10:19 ` Jan Beulich
2012-08-17 13:44 ` Boris Ostrovsky
2012-08-17 10:31 ` Jan Beulich
2012-08-17 13:50 ` Boris Ostrovsky [this message]
2012-08-17 14:01 ` 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=502E4C3A.5050409@amd.com \
--to=boris.ostrovsky@amd.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.