xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Wei Wang <wei.w.wang@intel.com>
Cc: andrew.cooper3@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v4 03/11] x86/intel_pstate: add new policy fields and a new driver interface
Date: Fri, 24 Jul 2015 07:26:28 -0600	[thread overview]
Message-ID: <55B259240200007800095331@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1435230903-21989-1-git-send-email-wei.w.wang@intel.com>

>>> On 25.06.15 at 13:15, <wei.w.wang@intel.com> wrote:
> --- a/xen/include/acpi/cpufreq/cpufreq.h
> +++ b/xen/include/acpi/cpufreq/cpufreq.h
> @@ -41,6 +41,24 @@ struct cpufreq_cpuinfo {
>      unsigned int        transition_latency; /* in 10^(-9) s = nanoseconds */
>  };
>  
> +struct perf_limits {
> +    bool_t no_turbo;
> +    bool_t turbo_disabled;

Considering that struct cpufreq_policy already has a turbo field,
and without seeing how the fields get initialized or used, I can't
really judge whether they're rightfully being added here. If you
want to keep them, please defer their addition to this structure
until the patch actually using them. (I wonder whether that
wouldn't be better for most/all of the other fields too.)

> +struct internal_governor {
> +    char *avail_gov;
> +    uint32_t gov_num;
> +    uint32_t cur_gov;

Same here - how should a reviewer of this patch judge whether
these fields make sens when they aren't being used anywhere?
I can somehow guess the meaning of the last field...

Jan

      reply	other threads:[~2015-07-24 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 11:15 [PATCH v4 03/11] x86/intel_pstate: add new policy fields and a new driver interface Wei Wang
2015-07-24 13:26 ` Jan Beulich [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=55B259240200007800095331@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.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 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).