All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"jbeulich@suse.com" <jbeulich@suse.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v3 10/11] x86/intel_pstate: support the use of intel_pstate in pmstat.c
Date: Fri, 12 Jun 2015 07:13:45 -0400	[thread overview]
Message-ID: <557ABEE9.5050801@citrix.com> (raw)
In-Reply-To: <286AC319A985734F985F78AFA26841F798D1CD@shsmsx102.ccr.corp.intel.com>

Hi,

On 11/06/2015 23:03, Wang, Wei W wrote:
> On 11/06/2015 22:02, Julien Grall wrote:
>> On 11/06/2015 04:31, Wei Wang wrote:
>>> -    list_for_each(pos, &cpufreq_governor_list)
>>> +    if (policy->policy)
>>
>> What if another cpufreq decides to use policy->policy?
>
> What is "another cpufreq"? The "policy" is per-CPU struct.

I mean another cpufreq driver. Correct me if I'm wrong but from the name 
policy is not intel pstate specific. That means that a new cpufreq 
driver can decide to use the field his own purpose..

>   > > +        gov_num = INTEL_PSTATE_INTERNAL_GOV_NUM;
>>
>> Why not using cpufreq_governor_list?
>
> That's used by the old driver. We are not going through that old governor layer.

This is common code, it's used by different cpufreq driver for both x86 
and ARM (not yet supported). We should not relying on any other cpufreq 
driver won't use the field policy.

Regards,

-- 
Julien Grall

  parent reply	other threads:[~2015-06-12 11:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  8:31 [PATCH v3 10/11] x86/intel_pstate: support the use of intel_pstate in pmstat.c Wei Wang
2015-06-11 14:10 ` Julien Grall
2015-06-12  3:03   ` Wang, Wei W
2015-06-12  8:39     ` Jan Beulich
2015-06-12 11:13     ` Julien Grall [this message]
2015-06-15  0:30       ` Wang, Wei W
2015-06-15  9:15         ` Jan Beulich
2015-06-15 12:28           ` Wang, Wei W
2015-06-15 12:36             ` Jan Beulich
2015-06-15 14:11               ` Wang, Wei W
2015-06-16  7:09               ` Wang, Wei W
2015-06-16  7:53                 ` Jan Beulich
2015-06-17  5:01                   ` Wang, Wei W
2015-06-23  1:40 ` Wang, Wei W
2015-06-23  8:45   ` Wang, Wei W
2015-06-23  8:48   ` 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=557ABEE9.5050801@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wei.w.wang@intel.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.