Message ID | 20221117024955.3319484-5-Perry.Yuan@amd.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp182091wrr; Wed, 16 Nov 2022 18:54:00 -0800 (PST) X-Google-Smtp-Source: AA0mqf7LUmNZrDPHrKjGL4aI2z8h4Vq5dkcvDvyM2GfocTCT6A0eQ1AQniE+JBh7++E68dd8qaCg X-Received: by 2002:a17:906:1c52:b0:780:bd74:f960 with SMTP id l18-20020a1709061c5200b00780bd74f960mr497115ejg.701.1668653640482; Wed, 16 Nov 2022 18:54:00 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1668653640; cv=pass; d=google.com; s=arc-20160816; b=A6LLDjjGjFFCY+FkxgN7BeyRKP8RrUji/ombMKJRqDUewjdcnP/xDp4dvjroMWNCCS XIY19i6TxMmMdAbXJXM1dBpEgb/sRnvbfZexExcGrUMws3xsGqSySdSplvGE9lK36wa8 au78XjhrEFO2VSAMb5WpBCtUTNJMST+UmNUBlOEJV47OQNlZA0tuxphAa81Wvbqs0Q1I dOULHbANxLy3g4UmfqkyIUF096U6eQDIN3uMo1BcFnCiCNnIuej0Wwb1S9t0An1qDXlK F7ZYs5s4FZBFVVtw1CaVCdgBDo5z6Ed/p+AX3gdp4PiUMRjlysz0W5qUqD8B31Rv/7lU 8nBQ== ARC-Message-Signature: i=2; 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:message-id:date:subject:cc:to:from :dkim-signature; bh=WOaTYCi7NB3f7zqVf4NrguCJferwo6NNYNHoyElxFQ0=; b=CNrXD6xuawLnFSmdaSy10ZnHuw/043eWN5XTeuOHzzxYlCVb9lffvG/lQeHjQqNw8J KvcLWLwVgbOJVHLDDTJ42bgynh8pNzovaLeRnOaeiKYx6hVvfsesIhGAYo8LbwseqUgP eMmJ3zvtaOgE6YUm8zDphPJ7VAPVDVsAFzNvx/HnUAN8TGNVywion8BLGm6Z1TpbSbii KqmR7hwTaYE7r2/pAP9W3fc8B/wiP1DIE6ehMCozhZx2PrKCw30IQP8HFdy+VHhLlrN2 Ur79BiXXPd3rmxn/0h52EaSAwng1kbsAfDNShttU3bHp3JU0oCPADhEYCsqxvzLoqj52 nlYg== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@amd.com header.s=selector1 header.b=JgwZ5WVy; arc=pass (i=1 spf=pass spfdomain=amd.com dmarc=pass fromdomain=amd.com); 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amd.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d25-20020a1709067f1900b0078df2f22f80si13282072ejr.647.2022.11.16.18.53.37; Wed, 16 Nov 2022 18:54:00 -0800 (PST) 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=@amd.com header.s=selector1 header.b=JgwZ5WVy; arc=pass (i=1 spf=pass spfdomain=amd.com dmarc=pass fromdomain=amd.com); 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amd.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239022AbiKQCwl (ORCPT <rfc822;just.gull.subs@gmail.com> + 99 others); Wed, 16 Nov 2022 21:52:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35874 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238978AbiKQCwc (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 16 Nov 2022 21:52:32 -0500 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2040.outbound.protection.outlook.com [40.107.236.40]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8362A43AF7; Wed, 16 Nov 2022 18:52:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jkWLJmmt1drKHO6jEoqGJ/EcRhYAb93/FgL8G/SDaQ/ilDQU6qFxhmu6AVIGDDiXJQDcyUILcfh+8NvZLt0mmq4Xeq2oncJbZnxH9xXCM7ZKctgA6Ou4WY1nUx1NsH9e4C39dUy5ukW7Lzc2L4zK0Xr71c4hgeYJCE+ch7FD3ITDl+NLnZQ/sl0se/6H2rDW5AAwotz5g8mRRtlgzxMtBEqfvUZpcCZBUaKtp+2D1C2tQ1WfqAxnHKHqanOl9rCIAJFOBTRJgtyzj9xJa1ktpkxhTKOfSzgyxQ65M7qKfmSHNw8kuTl2sxzwuPY/rkwguofqIOjGTmngmz9wYNshOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=WOaTYCi7NB3f7zqVf4NrguCJferwo6NNYNHoyElxFQ0=; b=O7YEBvdQW0VLurrRADmzjyxNGR4t01EcABf31pF5+GVV9i1K0IP9iTqu/6DGf5JEXIACu92l+Cogi51jTbS6k1XMm295TilVSrHFB2LGQ2sDUmevGKVgasV5XToVR7gtKgv+7EQa5urIdSKeVn/2yQo9mZz/+0HhY/iPjOrLIv3T3LsXZS9khwfNiQJbHc9TV//c8WWBoS7/EmKjDv4FyHmqCV3arms102GI/pCAHGH93DrCX8tun4uzw6Qpw1d+JdB+n9Trhsm8SBu6oNyoCBlJoHV8WJwLHKsfcasuWBoKpHDRh50Maql3jRQzMHClbFOeg0HeI6gCDJvOHFJyeQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=intel.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WOaTYCi7NB3f7zqVf4NrguCJferwo6NNYNHoyElxFQ0=; b=JgwZ5WVyaOedb2u4Yxn3RxM68CjKxDucKJjrzdUuzXDqxYKUCzx0jVTxhfja/UXOdPDHZtmNsjGSYsxzTxXf3RcsEj1PYqM6EIBsOB49XIsn0ZCovWXDS9c3oE9UMzvp10deGIdVLtGIzMBDDAsgERZ4OVGHCS0S2My6uTOOTX4= Received: from BN0PR02CA0058.namprd02.prod.outlook.com (2603:10b6:408:e5::33) by SA1PR12MB5657.namprd12.prod.outlook.com (2603:10b6:806:234::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5813.19; Thu, 17 Nov 2022 02:52:21 +0000 Received: from BL02EPF0000EE3E.namprd05.prod.outlook.com (2603:10b6:408:e5:cafe::a4) by BN0PR02CA0058.outlook.office365.com (2603:10b6:408:e5::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5813.19 via Frontend Transport; Thu, 17 Nov 2022 02:52:21 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 165.204.84.17) smtp.mailfrom=amd.com; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=amd.com; Received-SPF: Pass (protection.outlook.com: domain of amd.com designates 165.204.84.17 as permitted sender) receiver=protection.outlook.com; client-ip=165.204.84.17; helo=SATLEXMB04.amd.com; pr=C Received: from SATLEXMB04.amd.com (165.204.84.17) by BL02EPF0000EE3E.mail.protection.outlook.com (10.167.241.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.5813.11 via Frontend Transport; Thu, 17 Nov 2022 02:52:21 +0000 Received: from pyuan-Cloudripper.amd.com (10.180.168.240) by SATLEXMB04.amd.com (10.181.40.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.34; Wed, 16 Nov 2022 20:52:01 -0600 From: Perry Yuan <Perry.Yuan@amd.com> To: <rafael.j.wysocki@intel.com>, <ray.huang@amd.com>, <viresh.kumar@linaro.org>, <Mario.Limonciello@amd.com> CC: <Nathan.Fontenot@amd.com>, <Alexander.Deucher@amd.com>, <Deepak.Sharma@amd.com>, <Shimmer.Huang@amd.com>, <Li.Meng@amd.com>, <Xiaojian.Du@amd.com>, <wyes.karny@amd.com>, <gautham.shenoy@amd.com>, <ananth.narayan@amd.com>, <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>, Perry Yuan <Perry.Yuan@amd.com> Subject: [PATCH 4/5] Documentation: amd-pstate: add driver working mode introduction Date: Thu, 17 Nov 2022 10:49:54 +0800 Message-ID: <20221117024955.3319484-5-Perry.Yuan@amd.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221117024955.3319484-1-Perry.Yuan@amd.com> References: <20221117024955.3319484-1-Perry.Yuan@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain X-Originating-IP: [10.180.168.240] X-ClientProxiedBy: SATLEXMB03.amd.com (10.181.40.144) To SATLEXMB04.amd.com (10.181.40.145) X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: BL02EPF0000EE3E:EE_|SA1PR12MB5657:EE_ X-MS-Office365-Filtering-Correlation-Id: dbbf3f15-94a4-4423-fad0-08dac846bf73 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: tvQKM1SMlaEu+8B9gZUMGx59EQPuXvz1FSh8tww8HScfh7ZoHU9/SWQiW4Njqb7XGdkvRg/ZzaHp4a8HCtYZvwJRbbhYojwF4ESMDKl7dZUwtVfVNj11NM6Wa9MR63YaQStw7JvajbRnoJCfhrA85bLyZ7Jogci+z8oUHppfsqdZ85fMViL1w0yz/UB02uGkZxmqFQWnswfNIS6JT+McErU+YuTcxG3n1D7rsWWJlXweUfYImeRBg9ueGVW3YpKgm/Xeyux7BlRULc5UmIilt/ELPl8IS1UZvxQPOl462H7hDladEOLl9qmAn84u/CTMmKUH+kmhiwcU4u/3d7XZBInt75MI5Z85bgsPlZlXGfUusuqb8OMvvIRLl4wJpSK9c1400WX/r+RfHiA6hxy+xueKhvo3w1v1o9Lsa9cRmiqTL5MrxWbuyEfqsqmJMPpOyhzhf71UHkwOAqpu6yssNzrIXAtTzcprb9DowheG198BQoawcbYaDvFyn5D49j5A1V16WESHVG4ArhuO5u5aeXHAfnJwSXYzMicNJC0QmNZZyyEoSD2lzdpDoYelxLHwfrgnNhQ0K9vMq62qRhI0ONZLOsKnN6kynsoQ2S3Ff4u5stGUgPsCBsJtw6jV283TXPS1I1Q7jmYKbafdXyX+Pp0sMtDH4h78G1Duv5vsur0nKdoocbYLKZmBVHJ4jJT7JxStTenk9K4qmkJ7gYMMB2TeiyYTwUYHkSDWFOKzdPVj6LHLTajREOC8CEAJaE5sT8Fy5ekbu4NXv6WeKsuaSXDMQ2cyURI4RQ8GzIJQchd9jD0hGLaK5Dgld4Zm/tGlyU7aBYpNFppkI3jDmnxFeg2C08R8BtB63s4v6h1/RNk= X-Forefront-Antispam-Report: CIP:165.204.84.17;CTRY:US;LANG:en;SCL:1;SRV:;IPV:CAL;SFV:NSPM;H:SATLEXMB04.amd.com;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(13230022)(4636009)(376002)(346002)(396003)(39860400002)(136003)(451199015)(40470700004)(46966006)(36840700001)(16526019)(36756003)(426003)(336012)(1076003)(186003)(2616005)(41300700001)(70586007)(110136005)(82740400003)(86362001)(82310400005)(40460700003)(83380400001)(70206006)(4326008)(8676002)(47076005)(40480700001)(36860700001)(8936002)(2906002)(26005)(5660300002)(54906003)(316002)(478600001)(81166007)(6666004)(7696005)(356005)(6636002)(2101003)(36900700001)(473944003);DIR:OUT;SFP:1101; X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Nov 2022 02:52:21.1192 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: dbbf3f15-94a4-4423-fad0-08dac846bf73 X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3dd8961f-e488-4e60-8e11-a82d994e183d;Ip=[165.204.84.17];Helo=[SATLEXMB04.amd.com] X-MS-Exchange-CrossTenant-AuthSource: BL02EPF0000EE3E.namprd05.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA1PR12MB5657 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1749710159543760504?= X-GMAIL-MSGID: =?utf-8?q?1749710159543760504?= |
Series |
AMD Pstate driver Urgent Change
|
|
Commit Message
Yuan, Perry
Nov. 17, 2022, 2:49 a.m. UTC
Introduce the `amd-pstate` driver new working mode with
`amd-pstate=passive` added to kernel command line.
If there is no passive mode enabled by user, amd-pstate driver will be
disabled by default for now.
Signed-off-by: Perry Yuan <Perry.Yuan@amd.com>
---
Documentation/admin-guide/pm/amd-pstate.rst | 30 +++++++++------------
1 file changed, 13 insertions(+), 17 deletions(-)
Comments
Hello Perry, On Thu, Nov 17, 2022 at 10:49:54AM +0800, Perry Yuan wrote: > Introduce the `amd-pstate` driver new working mode with > `amd-pstate=passive` added to kernel command line. It should be `amd_pstate=passive` here to be consistent with the early parameter and the rest of the documentation. > If there is no passive mode enabled by user, amd-pstate driver will be > disabled by default for now. > > Signed-off-by: Perry Yuan <Perry.Yuan@amd.com> > --- > Documentation/admin-guide/pm/amd-pstate.rst | 30 +++++++++------------ > 1 file changed, 13 insertions(+), 17 deletions(-) > > diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst > index 8f3d30c5a0d8..06e23538f79c 100644 > --- a/Documentation/admin-guide/pm/amd-pstate.rst > +++ b/Documentation/admin-guide/pm/amd-pstate.rst > @@ -283,23 +283,19 @@ efficiency frequency management method on AMD processors. > Kernel Module Options for ``amd-pstate`` > ========================================= > > -.. _shared_mem: > - > -``shared_mem`` > -Use a module param (shared_mem) to enable related processors manually with > -**amd_pstate.shared_mem=1**. > -Due to the performance issue on the processors with `Shared Memory Support > -<perf_cap_>`_, we disable it presently and will re-enable this by default > -once we address performance issue with this solution. > - > -To check whether the current processor is using `Full MSR Support <perf_cap_>`_ > -or `Shared Memory Support <perf_cap_>`_ : :: > - > - ray@hr-test1:~$ lscpu | grep cppc > - Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm > - > -If the CPU flags have ``cppc``, then this processor supports `Full MSR Support > -<perf_cap_>`_. Otherwise, it supports `Shared Memory Support <perf_cap_>`_. > +Passive Mode > +------------ > + > +``amd_pstate=passive`` > + > +It will be enabled if the ``amd_pstate=passive`` is passed to the kernel in the command line. > +In this mode, ``amd_pstate`` driver software specifies a desired QoS target in the CPPC > +performance scale as a relative number. This can be expressed as percentage of nominal > +performance (infrastructure max). Below the nominal sustained performance level, > +desired performance expresses the average performance level of the processor subject > +to the Performance Reduction Tolerance register. Above the nominal performance level, > +processor must provide at least nominal performance requested and go higher if current > +operating conditions allow. Otherwise looks good to me. Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com> -- Thanks and Regards gautham.
[AMD Official Use Only - General] Hi Gautham > -----Original Message----- > From: Shenoy, Gautham Ranjal <gautham.shenoy@amd.com> > Sent: Thursday, November 17, 2022 12:16 PM > To: Yuan, Perry <Perry.Yuan@amd.com> > Cc: rafael.j.wysocki@intel.com; Huang, Ray <Ray.Huang@amd.com>; > viresh.kumar@linaro.org; Limonciello, Mario <Mario.Limonciello@amd.com>; > Fontenot, Nathan <Nathan.Fontenot@amd.com>; Deucher, Alexander > <Alexander.Deucher@amd.com>; Sharma, Deepak > <Deepak.Sharma@amd.com>; Huang, Shimmer > <Shimmer.Huang@amd.com>; Meng, Li (Jassmine) <Li.Meng@amd.com>; > Du, Xiaojian <Xiaojian.Du@amd.com>; Karny, Wyes > <Wyes.Karny@amd.com>; Narayan, Ananth <Ananth.Narayan@amd.com>; > linux-pm@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH 4/5] Documentation: amd-pstate: add driver working > mode introduction > > Hello Perry, > > On Thu, Nov 17, 2022 at 10:49:54AM +0800, Perry Yuan wrote: > > Introduce the `amd-pstate` driver new working mode with > > `amd-pstate=passive` added to kernel command line. > > It should be `amd_pstate=passive` here to be consistent with the early > parameter and the rest of the documentation. Thank you help to review, Will fix this with V2 Perry. > > > > If there is no passive mode enabled by user, amd-pstate driver will be > > disabled by default for now. > > > > Signed-off-by: Perry Yuan <Perry.Yuan@amd.com> > > --- > > Documentation/admin-guide/pm/amd-pstate.rst | 30 > > +++++++++------------ > > 1 file changed, 13 insertions(+), 17 deletions(-) > > > > diff --git a/Documentation/admin-guide/pm/amd-pstate.rst > > b/Documentation/admin-guide/pm/amd-pstate.rst > > index 8f3d30c5a0d8..06e23538f79c 100644 > > --- a/Documentation/admin-guide/pm/amd-pstate.rst > > +++ b/Documentation/admin-guide/pm/amd-pstate.rst > > @@ -283,23 +283,19 @@ efficiency frequency management method on > AMD processors. > > Kernel Module Options for ``amd-pstate`` > > ========================================= > > > > -.. _shared_mem: > > - > > -``shared_mem`` > > -Use a module param (shared_mem) to enable related processors > manually > > with -**amd_pstate.shared_mem=1**. > > -Due to the performance issue on the processors with `Shared Memory > > Support -<perf_cap_>`_, we disable it presently and will re-enable > > this by default -once we address performance issue with this solution. > > - > > -To check whether the current processor is using `Full MSR Support > > <perf_cap_>`_ -or `Shared Memory Support <perf_cap_>`_ : :: > > - > > - ray@hr-test1:~$ lscpu | grep cppc > > - Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid > extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 > sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy > svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit > wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 > cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep > bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni > xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total > cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv > svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists > pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku > ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm > > - > > -If the CPU flags have ``cppc``, then this processor supports `Full > > MSR Support -<perf_cap_>`_. Otherwise, it supports `Shared Memory > Support <perf_cap_>`_. > > +Passive Mode > > +------------ > > + > > +``amd_pstate=passive`` > > + > > +It will be enabled if the ``amd_pstate=passive`` is passed to the kernel in > the command line. > > +In this mode, ``amd_pstate`` driver software specifies a desired QoS > > +target in the CPPC performance scale as a relative number. This can > > +be expressed as percentage of nominal performance (infrastructure > > +max). Below the nominal sustained performance level, desired > > +performance expresses the average performance level of the processor > > +subject to the Performance Reduction Tolerance register. Above the > > +nominal performance level, processor must provide at least nominal > performance requested and go higher if current operating conditions allow. > > Otherwise looks good to me. > > Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com> > > -- > Thanks and Regards > gautham.
On 11/17/2022 8:19 AM, Perry Yuan wrote: > Introduce the `amd-pstate` driver new working mode with > `amd-pstate=passive` added to kernel command line. > If there is no passive mode enabled by user, amd-pstate driver will be > disabled by default for now. > > Signed-off-by: Perry Yuan <Perry.Yuan@amd.com> Tested-by: Wyes Karny <wyes.karny@amd.com> > --- > Documentation/admin-guide/pm/amd-pstate.rst | 30 +++++++++------------ > 1 file changed, 13 insertions(+), 17 deletions(-) > > diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst > index 8f3d30c5a0d8..06e23538f79c 100644 > --- a/Documentation/admin-guide/pm/amd-pstate.rst > +++ b/Documentation/admin-guide/pm/amd-pstate.rst > @@ -283,23 +283,19 @@ efficiency frequency management method on AMD processors. > Kernel Module Options for ``amd-pstate`` > ========================================= > > -.. _shared_mem: > - > -``shared_mem`` > -Use a module param (shared_mem) to enable related processors manually with > -**amd_pstate.shared_mem=1**. > -Due to the performance issue on the processors with `Shared Memory Support > -<perf_cap_>`_, we disable it presently and will re-enable this by default > -once we address performance issue with this solution. > - > -To check whether the current processor is using `Full MSR Support <perf_cap_>`_ > -or `Shared Memory Support <perf_cap_>`_ : :: > - > - ray@hr-test1:~$ lscpu | grep cppc > - Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm > - > -If the CPU flags have ``cppc``, then this processor supports `Full MSR Support > -<perf_cap_>`_. Otherwise, it supports `Shared Memory Support <perf_cap_>`_. > +Passive Mode > +------------ > + > +``amd_pstate=passive`` > + > +It will be enabled if the ``amd_pstate=passive`` is passed to the kernel in the command line. > +In this mode, ``amd_pstate`` driver software specifies a desired QoS target in the CPPC > +performance scale as a relative number. This can be expressed as percentage of nominal > +performance (infrastructure max). Below the nominal sustained performance level, > +desired performance expresses the average performance level of the processor subject > +to the Performance Reduction Tolerance register. Above the nominal performance level, > +processor must provide at least nominal performance requested and go higher if current > +operating conditions allow. > > > ``cpupower`` tool support for ``amd-pstate``
diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst index 8f3d30c5a0d8..06e23538f79c 100644 --- a/Documentation/admin-guide/pm/amd-pstate.rst +++ b/Documentation/admin-guide/pm/amd-pstate.rst @@ -283,23 +283,19 @@ efficiency frequency management method on AMD processors. Kernel Module Options for ``amd-pstate`` ========================================= -.. _shared_mem: - -``shared_mem`` -Use a module param (shared_mem) to enable related processors manually with -**amd_pstate.shared_mem=1**. -Due to the performance issue on the processors with `Shared Memory Support -<perf_cap_>`_, we disable it presently and will re-enable this by default -once we address performance issue with this solution. - -To check whether the current processor is using `Full MSR Support <perf_cap_>`_ -or `Shared Memory Support <perf_cap_>`_ : :: - - ray@hr-test1:~$ lscpu | grep cppc - Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm - -If the CPU flags have ``cppc``, then this processor supports `Full MSR Support -<perf_cap_>`_. Otherwise, it supports `Shared Memory Support <perf_cap_>`_. +Passive Mode +------------ + +``amd_pstate=passive`` + +It will be enabled if the ``amd_pstate=passive`` is passed to the kernel in the command line. +In this mode, ``amd_pstate`` driver software specifies a desired QoS target in the CPPC +performance scale as a relative number. This can be expressed as percentage of nominal +performance (infrastructure max). Below the nominal sustained performance level, +desired performance expresses the average performance level of the processor subject +to the Performance Reduction Tolerance register. Above the nominal performance level, +processor must provide at least nominal performance requested and go higher if current +operating conditions allow. ``cpupower`` tool support for ``amd-pstate``