Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp753216ioo; Thu, 26 May 2022 14:06:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJypZa4symci69dlJTpUk106mBfVuhyEUctEtesyRMcrmz9uSzR7WthCRkecJ4BwVBUaMRJO X-Received: by 2002:a17:902:988e:b0:161:8750:480b with SMTP id s14-20020a170902988e00b001618750480bmr40448492plp.154.1653599174067; Thu, 26 May 2022 14:06:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1653599174; cv=none; d=google.com; s=arc-20160816; b=Gb0U/Zon8NLqEFh/MU+oHC37DwfjoaJwxIXVNn7MmA5ADsQoLx+me+BmF4JvZSuYg8 jvnCqxKgA5Hj6zwu+1FFao45dhEwXkewavPdQspGUtPGTsjbv39lR7UaKMvV275lSCxK iQ/+u+0PZ9wzCR+jHVnf/9U25WjOA4UX4NKM6lnddrCRhl3jj8sOMJufAd0Sd04s2umL 2B395a5QLt7Iqa2Rh2v4V6DrUiaTQ3CvwiDkFiTqUQX5ONxjHce3DHozQjiq/bMbY3mr WRB1LZP7nFyV045EJ70jbs6htkPtatnEA38+q1BQjEEh1uxRh6OhUEIv88TSVqEBTjIC bn5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=v7/OiPNczp/oyedYEANRvphRT7YfTE6ledCh6J79qz4=; b=kk3/CrdhsXPWgwyPC2PqRxK0QsUpvQxB3lTDbXnAcXPbN3C0Mokx5DItf5jgYHvET9 tR11JdZNmeIc+kTgjoPovr29QBclrRe569R8aGCNO/YnN6xlN0qzi9H0n/C/M2si3+4q Wc5ZQeyyzXwzfrWR6z79dD9kRl1uPBEbkFDKBrFtYj5R/wdbgUB/pPnmk76bDDk1GtPl xWahkECAJwagQBpbOyT89taJQ0PSoyn0iYCllIBeZXYYv9X+eKBAnnpby99hMKZUqc3h 7Lpb2TN0GtvOBYUpaX0w5bP+mm25cb7lpv4RkWziD0jWnIZ4KYPfbI64mmgvrHU9BXXM Hx9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=h06TDkkP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c16-20020a056a00009000b0050d28930dbcsi413015pfj.192.2022.05.26.14.05.49; Thu, 26 May 2022 14:06:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=h06TDkkP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234458AbiEYIGg (ORCPT + 99 others); Wed, 25 May 2022 04:06:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229706AbiEYIGf (ORCPT ); Wed, 25 May 2022 04:06:35 -0400 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B7094EA for ; Wed, 25 May 2022 01:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1653465993; x=1685001993; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=rCCPV0jY6YmFI9vNW2kaDuWUgLcql2tkiu12s2vTpoA=; b=h06TDkkPaDB8uU9nB/5Sqz7xda22DWu/QgV5Clh4mSlNBenUpz1JQtSp zs9Fuzd43JzSHh4QKihhQBWYFTpdbUFAjNyWiVvddBeb3YOdD5N+15LSf Q/KH5zeAERfHoVCNzPeXCoE4h++zBmX/zxzAgpSR2Kp4oIcr14SSppW1n UlSNBz3rOU/uB+STQy/4Dxu6gBvzTQD+syNpCDRzcjVKSuh6TCo1qnhlo NyyUtDn1FvZ9mK77y0vwnaoSVwQ35p4FE7BWXFTQtPowDpGfTAwxxyqTR 1qYH8VAasoDcnEaWDvmPtDEQKOjYkmzMj5Y8X90x8e6yw2wRjUwFda4Rj Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10357"; a="255813796" X-IronPort-AV: E=Sophos;i="5.91,250,1647327600"; d="scan'208";a="255813796" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 May 2022 01:06:33 -0700 X-IronPort-AV: E=Sophos;i="5.91,250,1647327600"; d="scan'208";a="703807408" Received: from she1-mobl2.ccr.corp.intel.com ([10.255.29.30]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 May 2022 01:06:26 -0700 Message-ID: <9dde86ab8773ddf3f9d88a85ed9ee010cdcf50a8.camel@intel.com> Subject: Re: [PATCH v4 1/3] x86: Handle idle=nomwait cmdline properly for x86_idle From: Zhang Rui To: Wyes Karny , 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 Date: Wed, 25 May 2022 16:06:24 +0800 In-Reply-To: <7e5a66c4d383652c89a0b5ec0f57e0a95902f810.1653324016.git-series.wyes.karny@amd.com> References: <7e5a66c4d383652c89a0b5ec0f57e0a95902f810.1653324016.git-series.wyes.karny@amd.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > --- > 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") thanks, rui