From: Ingo Molnar <mingo@kernel.org>
To: David Wang <davidwang@zhaoxin.com>
Cc: rjw@rjwysocki.net, len.brown@intel.com, pavel@ucw.cz,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-pm@kernel.org,
linux-kernel@vger.kernel.org, brucechang@via-alliance.com,
cooperyan@zhaoxin.com, qiyuanwang@zhaoxin.com,
benjaminpan@viatech.com, lukelin@viacpu.com, timguo@zhaoxin.com,
cobechen@zhaoxin.com, jiangbowang@zhaoxin.com
Subject: Re: [PATCH] Delete some unusefull operations for centaur CPU/platform
Date: Sun, 4 Mar 2018 10:31:46 +0100 [thread overview]
Message-ID: <20180304093146.rujp4f62fv6xotb7@gmail.com> (raw)
In-Reply-To: <1519963908-4359-1-git-send-email-davidwang@zhaoxin.com>
* David Wang <davidwang@zhaoxin.com> wrote:
> For Centaur CPU, the ucode will make sure that each CPU core can keep cache
> coherency with each other when the CPU core entering to any C state. So the
> cache flush operations when enter C3 is not necessary and will cause large
> C3 enter/exit latency.
> And the bus master disable operation when CPU core entering C3 state is not
> needed too. Because the chipset will automatically do this operation.
>
> Signed-off-by: David Wang <davidwang@zhaoxin.com>
> ---
> arch/x86/kernel/acpi/cstate.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/x86/kernel/acpi/cstate.c b/arch/x86/kernel/acpi/cstate.c
> index dde437f..1cd357b 100644
> --- a/arch/x86/kernel/acpi/cstate.c
> +++ b/arch/x86/kernel/acpi/cstate.c
> @@ -51,6 +51,18 @@ void acpi_processor_power_init_bm_check(struct acpi_processor_flags *flags,
> if (c->x86_vendor == X86_VENDOR_INTEL &&
> (c->x86 > 0xf || (c->x86 == 6 && c->x86_model >= 0x0f)))
> flags->bm_control = 0;
> +
> + if (c->x86_vendor == X86_VENDOR_CENTAUR) {
> + /*
> + * on all centaur CPUs, sw need not execute cache flush operation
> + * when entering C3 type State.
> + *
> + * On all Centaur platforms, sw need not execute ARB_DISABLE while
> + * entering C3 type state.
> + */
> + flags->bm_check = 1;
> + flags->bm_control = 0;
> + }
Please clean up capitalization and spelling of the comment, and please also
explain the ACPI-idle settings a bit better, i.e. something like:
/*
* On all Centaur CPUs the kernel does not have to
* execute a cache flush operation (WBINVD) when
* entering C3 state.
*
* On all Centaur platforms the kernel does not have to
* disable bus-master arbitration (ARB_DISABLE) when
* entering C3 state.
*/
Also, two questions:
1)
I'm wondering about this logic in acpi_processor_power_verify_c3():
if (pr->flags.bm_check) {
if (!pr->flags.bm_control) {
if (pr->flags.has_cst != 1) {
/* bus mastering control is necessary */
ACPI_DEBUG_PRINT((ACPI_DB_INFO,
"C3 support requires BM control\n"));
return;
So ->has_cst is set on Centaur CPUs?
2)
There's this comment in acpi_idle_enter_bm():
/*
* disable bus master
* bm_check implies we need ARB_DIS
* bm_control implies whether we can do ARB_DIS
*
* That leaves a case where bm_check is set and bm_control is
* not set. In that case we cannot do much, we enter C3
* without doing anything.
*/
if (pr->flags.bm_control) {
It says 'bm_check == 1 implies we need ARB_DIS' - but we do the opposite in the
Centaur case? It it me who is confused or the comment?
Thanks,
Ingo
next prev parent reply other threads:[~2018-03-04 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 4:11 [PATCH] Delete some unusefull operations for centaur CPU/platform David Wang
2018-03-02 11:31 ` Rafael J. Wysocki
2018-03-04 9:31 ` Ingo Molnar [this message]
[not found] ` <efc93496e4ba46958b7b09eff54c2ce2@zhaoxin.com>
2018-03-12 8:40 ` 答复: " Ingo Molnar
2018-03-12 9:27 ` Rafael J. Wysocki
2018-03-12 9:46 ` Ingo Molnar
[not found] ` <0230c32412474e97bf7d2ef45cc64c4d@zhaoxin.com>
2018-03-29 11:03 ` 答复: " 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=20180304093146.rujp4f62fv6xotb7@gmail.com \
--to=mingo@kernel.org \
--cc=benjaminpan@viatech.com \
--cc=brucechang@via-alliance.com \
--cc=cobechen@zhaoxin.com \
--cc=cooperyan@zhaoxin.com \
--cc=davidwang@zhaoxin.com \
--cc=hpa@zytor.com \
--cc=jiangbowang@zhaoxin.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@kernel.org \
--cc=lukelin@viacpu.com \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=qiyuanwang@zhaoxin.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=timguo@zhaoxin.com \
--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