From: Chen Yu <yu.c.chen@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <len.brown@intel.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
yu.chen.surf@gmail.com, Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][RFC v2] Update the cpuinfo.max when power supply changes
Date: Fri, 1 Mar 2019 02:06:54 +0800 [thread overview]
Message-ID: <cover.1551375162.git.yu.c.chen@intel.com> (raw)
On Dell Inc. XPS13 9333, the BIOS changes the value of
MSR_IA32_MISC_ENABLE_TURBO_DISABLE at runtime (e.g., when
the power source changes), the maximum frequency of the
CPU is not updated accordingly. This is due to the policy's
cpuinfo.max is not updated when _PPC notifier fires.
Firstly we should update the cpuinfo.max in this corner case,
secondly we should broadcast the _PPC notifier to all online
CPUs to keep information consistent.
Chen Yu (2):
ACPI: add "processor.broadcast_ppc" hook to broadcast _PPC
ACPI: Update cpuinfo.max after bootup if necessary
drivers/acpi/processor_perflib.c | 16 ++++++++++++++--
drivers/cpufreq/cpufreq.c | 2 ++
drivers/cpufreq/intel_pstate.c | 15 +++++++++++++--
3 files changed, 29 insertions(+), 4 deletions(-)
--
2.17.1
next reply other threads:[~2019-02-28 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 18:06 Chen Yu [this message]
2019-02-28 18:07 ` [PATCH 1/2][RFC v2] ACPI: add "processor.broadcast_ppc" hook to broadcast _PPC Chen Yu
2019-02-28 22:18 ` Rafael J. Wysocki
2019-03-01 9:34 ` Rafael J. Wysocki
2019-03-02 10:16 ` Yu Chen
2019-02-28 18:08 ` [PATCH 2/2][RFC v2] ACPI: Update cpuinfo.max after bootup if necessary Chen Yu
2019-02-28 22:56 ` Rafael J. Wysocki
2019-03-02 10:04 ` Yu Chen
2019-03-03 17:04 ` 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=cover.1551375162.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.org \
--cc=yu.chen.surf@gmail.com \
/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.