From: Huang Rui <ray.huang@amd.com>
To: Borislav Petkov <bp@alien8.de>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
<linux-pm@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Giovanni Gherdovich <ggherdovich@suse.cz>,
Alex Deucher <alexander.deucher@amd.com>,
"Deepak Sharma" <deepak.sharma@amd.com>,
Jinzhou Su <Jinzhou.Su@amd.com>, Perry Yuan <Perry.Yuan@amd.com>,
Jassmine Meng <li.meng@amd.com>, Huang Rui <ray.huang@amd.com>
Subject: [PATCH 0/4] x86/acpi/cppc: Minor clean up for x86 CPPC implementation
Date: Mon, 14 Feb 2022 18:14:46 +0800 [thread overview]
Message-ID: <20220214101450.356047-1-ray.huang@amd.com> (raw)
Hi all,
While we were fixing the legacy issue below, we found the dependencies
between smpboot and CPPC were not very good. But due to urgent fix for
5.17-rc1, I didn't have much time to provide a complete solution.
https://lore.kernel.org/lkml/YdeWDDCwBQAYnlKb@amd.com/
In these series, I expand the scope of acpi/cppc_msr to acpi/cppc to cover
the all the CPPC helper functions for x86 ACPI. And then clean up the
smpboot and move CPPC related functions into the acpi/cppc.c. This design
is more straightforward and more clear to handle the CPPC in x86 and
resolve dependency issues between CPPC and smpboot.c.
Thanks,
Ray
Huang Rui (4):
x86/acpi: Expand the CPPC MSR file to cover the whole CPPC
implementation
x86, sched: Move AMD maximum frequency ratio setting function into x86
CPPC
x86, sched: Expose init_freq_invariance to topology header
x86/acpi: Move init_freq_invariance_cppc into x86 CPPC
arch/x86/include/asm/topology.h | 13 +++-
arch/x86/kernel/acpi/Makefile | 2 +-
arch/x86/kernel/acpi/cppc.c | 103 ++++++++++++++++++++++++++++++++
arch/x86/kernel/acpi/cppc_msr.c | 49 ---------------
arch/x86/kernel/smpboot.c | 72 +---------------------
5 files changed, 118 insertions(+), 121 deletions(-)
create mode 100644 arch/x86/kernel/acpi/cppc.c
delete mode 100644 arch/x86/kernel/acpi/cppc_msr.c
--
2.25.1
next reply other threads:[~2022-02-14 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 10:14 Huang Rui [this message]
2022-02-14 10:14 ` [PATCH 1/4] x86/acpi: Expand the CPPC MSR file to cover the whole CPPC implementation Huang Rui
2022-02-14 10:14 ` [PATCH 2/4] x86, sched: Move AMD maximum frequency ratio setting function into x86 CPPC Huang Rui
2022-02-14 10:14 ` [PATCH 3/4] x86, sched: Expose init_freq_invariance to topology header Huang Rui
2022-02-14 10:14 ` [PATCH 4/4] x86/acpi: Move init_freq_invariance_cppc into x86 CPPC Huang Rui
2022-03-01 19:20 ` [PATCH 0/4] x86/acpi/cppc: Minor clean up for x86 CPPC implementation Rafael J. Wysocki
2022-03-08 18:18 ` 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=20220214101450.356047-1-ray.huang@amd.com \
--to=ray.huang@amd.com \
--cc=Jinzhou.Su@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=deepak.sharma@amd.com \
--cc=ggherdovich@suse.cz \
--cc=li.meng@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.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).