From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 1/2] cpufreq: intel_pstate: Expose global sysfs attributes upfront
Date: Tue, 10 Jan 2017 12:48:55 -0800 [thread overview]
Message-ID: <1484081335.28749.11.camel@linux.intel.com> (raw)
In-Reply-To: <2389828.jxMzLa8mev@aspire.rjw.lan>
On Thu, 2017-01-05 at 02:51 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Expose the intel_pstate's global sysfs attributes before registering
> the driver to prepare for the addition of an attribute that also will
> have to work if the driver is not registered.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
>
[...]
> #ifdef CONFIG_ACPI
> @@ -1055,12 +1058,22 @@ static ssize_t show_turbo_pct(struct kob
> int total, no_turbo, turbo_pct;
> uint32_t turbo_fp;
>
> + mutex_lock(&intel_pstate_driver_lock);
> +
> + if (!driver_registered) {
> + mutex_unlock(&intel_pstate_limits_lock);
It should be
mutex_unlock(&intel_pstate_driver_lock);
> + return -EAGAIN;
> + }
> +
> cpu = all_cpu_data[0];
>
>
[...]
> @@ -1070,8 +1083,18 @@ static ssize_t show_num_pstates(struct k
> struct cpudata *cpu;
> int total;
>
> + mutex_lock(&intel_pstate_driver_lock);
> +
> + if (!driver_registered) {
> + mutex_unlock(&intel_pstate_limits_lock);
Change to
mutex_unlock(&intel_pstate_driver_lock);
> + return -EAGAIN;
> + }
> +
> cpu = all_cpu_data[0];
> total = cpu->pstate.turbo_pstate - cpu->pstate.min_pstate +
> 1;
> +
> + mutex_unlock(&intel_pstate_driver_lock);
> +
> return sprintf(buf, "%u\n", total);
> }
>
> @@ -1080,12 +1103,21 @@ static ssize_t show_no_turbo(struct kobj
> {
> ssize_t ret;
>
> + mutex_lock(&intel_pstate_driver_lock);
> +
> + if (!driver_registered) {
> + mutex_unlock(&intel_pstate_limits_lock);
Same here
mutex_unlock(&intel_pstate_driver_lock);
> + return -EAGAIN;
> + }
> +
> update_turbo_state();
> if (limits->turbo_disabled)
> ret = sprintf(buf, "%u\n", limits->turbo_disabled);
> else
> ret = sprintf(buf, "%u\n", limits->no_turbo);
>
> + mutex_unlock(&intel_pstate_driver_lock);
> +
> return ret;
> }
>
> @@ -1099,6 +1131,13 @@ static ssize_t store_no_turbo(struct kob
> if (ret != 1)
> return -EINVAL;
>
> + mutex_lock(&intel_pstate_driver_lock);
> +
> + if (!driver_registered) {
> + mutex_unlock(&intel_pstate_driver_lock);
> + return -EAGAIN;
> + }
> +
> mutex_lock(&intel_pstate_limits_lock); if (limits-
> >turbo_disabled) {
> pr_warn("Turbo disabled by BIOS or unavailable on
> processor\n");
> mutex_unlock(&intel_pstate_limits_lock);
Also
mutex_unlock(&intel_pstate_driver_lock);>
> return -EPERM;
> }
>
> update_turbo_state();
> @@ -1114,6 +1153,8 @@ static ssize_t store_no_turbo(struct kob
>
> intel_pstate_update_policies();
>
> + mutex_unlock(&intel_pstate_driver_lock);
> +
> return count;
> }
>
Thanks,
Srinivas
next prev parent reply other threads:[~2017-01-10 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 1:50 [RFC][PATCH 0/2] cpufreq: intel_pstate: Make it possible to change operation mode on the fly Rafael J. Wysocki
2017-01-05 1:51 ` [RFC][PATCH 1/2] cpufreq: intel_pstate: Expose global sysfs attributes upfront Rafael J. Wysocki
2017-01-10 20:48 ` Srinivas Pandruvada [this message]
2017-01-11 2:32 ` Rafael J. Wysocki
2017-01-11 3:12 ` [RFC][Update][PATCH " Rafael J. Wysocki
2017-01-05 1:53 ` [RFC][PATCH 2/2] cpufreq: intel_pstate: Operation mode control from sysfs Rafael J. Wysocki
2017-01-05 21:29 ` [RFC][PATCH 0/2] cpufreq: intel_pstate: Make it possible to change operation mode on the fly Srinivas Pandruvada
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=1484081335.28749.11.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.