From: Zhang Rui <rui.zhang@intel.com>
To: Wyes Karny <wyes.karny@amd.com>, linux-kernel@vger.kernel.org
Cc: Lewis.Carroll@amd.com, Mario.Limonciello@amd.com,
gautham.shenoy@amd.com, Ananth.Narayan@amd.com, bharata@amd.com,
len.brown@intel.com, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, peterz@infradead.org, chang.seok.bae@intel.com,
keescook@chromium.org, metze@samba.org,
zhengqi.arch@bytedance.com, mark.rutland@arm.com, puwen@hygon.cn,
rafael.j.wysocki@intel.com, andrew.cooper3@citrix.com,
jing2.liu@intel.com, jmattson@google.com,
pawan.kumar.gupta@linux.intel.com
Subject: Re: [PATCH v4 1/3] x86: Handle idle=nomwait cmdline properly for x86_idle
Date: Sun, 05 Jun 2022 20:32:51 +0800 [thread overview]
Message-ID: <a1cf42aeb221a857661abc7ac6833bfcedfd7873.camel@intel.com> (raw)
In-Reply-To: <f0e481c0-809b-a78a-6cbb-187e27bb9197@amd.com>
On Thu, 2022-06-02 at 21:11 +0530, Wyes Karny wrote:
> >
>
> Hi Rui,
>
> On 5/25/2022 1:36 PM, Zhang Rui wrote:
> > On Mon, 2022-05-23 at 22:25 +0530, Wyes Karny wrote:
> > > When kernel is booted with idle=nomwait do not use MWAIT as the
> > > default idle state.
> > >
> > > If the user boots the kernel with idle=nomwait, it is a clear
> > > direction to not use mwait as the default idle state.
> > > However, the current code does not take this into consideration
> > > while selecting the default idle state on x86.
> > >
> > > This patch fixes it by checking for the idle=nomwait boot option
> > > in
> > > prefer_mwait_c1_over_halt().
> > >
> > > Also update the documentation around idle=nomwait appropriately.
> > >
> > > Signed-off-by: Wyes Karny <wyes.karny@amd.com>
> > > ---
> > > Changes in v4:
> > > - Update documentation around idle=nomwait
> > > - Rename patch subject
> > >
> > > Documentation/admin-guide/pm/cpuidle.rst | 15 +++++++++------
> > > arch/x86/kernel/process.c | 6 +++++-
> > > 2 files changed, 14 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/Documentation/admin-guide/pm/cpuidle.rst
> > > b/Documentation/admin-guide/pm/cpuidle.rst
> > > index aec2cd2aaea7..19754beb5a4e 100644
> > > --- a/Documentation/admin-guide/pm/cpuidle.rst
> > > +++ b/Documentation/admin-guide/pm/cpuidle.rst
> > > @@ -612,8 +612,8 @@ the ``menu`` governor to be used on the
> > > systems
> > > that use the ``ladder`` governor
> > > by default this way, for example.
> > >
> > > The other kernel command line parameters controlling CPU idle
> > > time
> > > management
> > > -described below are only relevant for the *x86* architecture and
> > > some of
> > > -them affect Intel processors only.
> > > +described below are only relevant for the *x86* architecture and
> > > references
> > > +to ``intel_idle`` affect Intel processors only.
> > >
> > > The *x86* architecture support code recognizes three kernel
> > > command
> > > line
> > > options related to CPU idle time management: ``idle=poll``,
> > > ``idle=halt``,
> > > @@ -635,10 +635,13 @@ idle, so it very well may hurt single-
> > > thread
> > > computations performance as well as
> > > energy-efficiency. Thus using it for performance reasons may
> > > not be
> > > a good idea
> > > at all.]
> > >
> > > -The ``idle=nomwait`` option disables the ``intel_idle`` driver
> > > and
> > > causes
> > > -``acpi_idle`` to be used (as long as all of the information
> > > needed
> > > by it is
> > > -there in the system's ACPI tables), but it is not allowed to use
> > > the
> > > -``MWAIT`` instruction of the CPUs to ask the hardware to enter
> > > idle
> > > states.
> > > +The ``idle=nomwait`` option prevents the use of ``MWAIT``
> > > instruction of
> > > +the CPU to enter idle states. When this option is used, the
> > > ``acpi_idle``
> > > +driver will use the ``HLT`` instruction instead of ``MWAIT``. On
> > > systems
> > > +running Intel processors, this option disables the
> > > ``intel_idle``
> > > driver
> > > +and forces the use of the ``acpi_idle`` driver instead. Note
> > > that in
> > > either
> > > +case, ``acpi_idle`` driver will function only if all the
> > > information
> > > needed
> > > +by it is in the system's ACPI tables.
> > >
> > > In addition to the architecture-level kernel command line
> > > options
> > > affecting CPU
> > > idle time management, there are parameters affecting individual
> > > ``CPUIdle``
> > > diff --git a/arch/x86/kernel/process.c
> > > b/arch/x86/kernel/process.c
> > > index b370767f5b19..4e0178b066c5 100644
> > > --- a/arch/x86/kernel/process.c
> > > +++ b/arch/x86/kernel/process.c
> > > @@ -824,6 +824,10 @@ static void amd_e400_idle(void)
> > > */
> > > static int prefer_mwait_c1_over_halt(const struct cpuinfo_x86
> > > *c)
> > > {
> > > + /* User has disallowed the use of MWAIT. Fallback to HALT */
> > > + if (boot_option_idle_override == IDLE_NOMWAIT)
> > > + return 0;
> > > +
> > > if (c->x86_vendor != X86_VENDOR_INTEL)
> > > return 0;
> > >
> > > @@ -932,7 +936,7 @@ static int __init idle_setup(char *str)
> > > } else if (!strcmp(str, "nomwait")) {
> > > /*
> > > * If the boot option of "idle=nomwait" is added,
> > > - * it means that mwait will be disabled for CPU C2/C3
> > > + * it means that mwait will be disabled for CPU
> > > C1/C2/C3
> > > * states. In such case it won't touch the variable
> > > * of boot_option_idle_override.
> >
> > the code didn't change boot_option_idle_override when it was
> > introduced, but this has changed since commit d18960494f65 ("ACPI,
> > intel_idle: Cleanup idle= internal variables")
>
> Could you please clarify bit more why the commit you mentioned is
> related to this patch?
>
The comment "In such case it won't touch the variable of
boot_option_idle_override." has been broken for some time, it is not
related with this patch. But given that this patch "Also update the
documentation around idle=nomwait appropriately", so my suggestion is
to update it altogether, by deleting the last sentence.
thanks,
rui
next prev parent reply other threads:[~2022-06-05 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 16:55 [PATCH v4 0/3] x86: Prefer MWAIT over HLT on AMD processors Wyes Karny
2022-05-23 16:55 ` [PATCH v4 1/3] x86: Handle idle=nomwait cmdline properly for x86_idle Wyes Karny
2022-05-25 8:06 ` Zhang Rui
2022-06-02 15:41 ` Wyes Karny
2022-06-05 12:32 ` Zhang Rui [this message]
2022-06-06 9:13 ` Wyes Karny
2022-05-23 16:55 ` [PATCH v4 2/3] x86: Remove vendor checks from prefer_mwait_c1_over_halt Wyes Karny
2022-05-25 16:55 ` Peter Zijlstra
2022-06-06 12:50 ` Zhang Rui
2022-06-06 15:37 ` Dave Hansen
2022-06-07 1:16 ` Zhang Rui
2022-05-23 16:55 ` [PATCH v4 3/3] x86: Fix comment for X86_FEATURE_ZEN Wyes Karny
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=a1cf42aeb221a857661abc7ac6833bfcedfd7873.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=Ananth.Narayan@amd.com \
--cc=Lewis.Carroll@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=bharata@amd.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gautham.shenoy@amd.com \
--cc=hpa@zytor.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=keescook@chromium.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=metze@samba.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=wyes.karny@amd.com \
--cc=x86@kernel.org \
--cc=zhengqi.arch@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox