Message ID | 20230201065823.189828-1-wyes.karny@amd.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:2388:b0:96:219d:e725 with SMTP id i8csp231330dyf; Tue, 31 Jan 2023 23:01:23 -0800 (PST) X-Google-Smtp-Source: AK7set+GEce9nb3k5uA4riJHP7H7DQaynqEcvPtBc6UP69QBLg20eMJ5s7l5xXtI/OWQDyfAhhZl X-Received: by 2002:a17:90b:390a:b0:22e:5ffa:2a34 with SMTP id ob10-20020a17090b390a00b0022e5ffa2a34mr1141139pjb.36.1675234883104; Tue, 31 Jan 2023 23:01:23 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1675234883; cv=pass; d=google.com; s=arc-20160816; b=NJbWacoVWMmzfyOBkdVre5yZ6M8V8oGl5CvBMGUeyM8rQNnLuM2y8r+H9aHCP0X+Z3 jGbdubEu8gaYDc9J7SuDoFBVggIuXlifD8fdzs+Mf6NgBVn/MTeeH6h+C22W13fmJHzJ TzsOleDjWoN+XiVWAP30HRf2UShzJ27z99vco5KKrd2OO0EJOg9DcaGGRtwyAjEqaSO4 r9eE72dRc+FF3ELvBROs99yNEkW7EgHKrdd/jzNjegteX8P+TRaynqh97Rbh2hSHVGLv HQGuTDsgHa//UAtu0oblF73IEz/N5wGpoBtCp6sd8/E9is8SNoyiPl9jPbJ72+8/tcHe IfBA== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=AehbTQ2DArCaQU3TfzmWFSynk1AFGfsQpnZNtBQ7c+k=; b=DbqP00VyfTBpNZ23Rxwt5mHyDTt5UbvIXcImsO9MOMeRCUTbMaL9L2vGSCw2blot5m 91OM5ye1SnShxgoUH1ZcPqNGZWmgbF5/041Pn8hQ4vjR7NgiLS907dGXJ3P1owCqWae+ PHjBZqRVPk7ox43+yXAEy8MM9FZ+6mFvJZjaeL59A9n2MwN7cZMGrHqo8Lt3duv3vrC4 akJsvpkBhDMNLHyOiP22ZZHoEgyg5d6KoSyRVq/Po9xg/taCegD246aW67pRDTuiN4cG HTlOF54YhWMiaqaZZHHeLwcto4TcUG+E77XR+mElSP4SsGW6I4nC5F1IBdlMbaK+Laqe 1Tjw== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@amd.com header.s=selector1 header.b=ge7VKm+Z; 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 n20-20020a17090aab9400b0022645e2a88csi992968pjq.56.2023.01.31.23.01.10; Tue, 31 Jan 2023 23:01:23 -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=ge7VKm+Z; 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 S231582AbjBAG7R (ORCPT <rfc822;duw91626@gmail.com> + 99 others); Wed, 1 Feb 2023 01:59:17 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40862 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231671AbjBAG6t (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 1 Feb 2023 01:58:49 -0500 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2051.outbound.protection.outlook.com [40.107.223.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F7783C19; Tue, 31 Jan 2023 22:58:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lRsYgpSmpQJqFuPITjr+rz6PeLg3+7L0M+fOca6z7lsbnsV+twck6w40bDOGG2pzf2Q4/9x2/N9vMHTc3dJ8M32YEIuOe+klEG2mRETFaRjg0oU/HizTUAvFYJ2Z0JJZ9onQ82Ie3syvYvvnL/XoLMnCAe6YLTXYYzJMRu62Nb/7vJ4Fm79mE0HPUOVWVc8PZlXYsR2xTHhkyjluZGZoFIZeykoTbuLtnrUmnmQ48jZccmiEVcN464tk5ZLAoqFsMxqXoz9drHn+Ep9LXUc87yfX6H+QwL1KNMS3kYDc4dl/uG1ST74hwsh/4gZQA3MGqa5JDepCmIk0osLBsb6rKw== 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=AehbTQ2DArCaQU3TfzmWFSynk1AFGfsQpnZNtBQ7c+k=; b=F9m/DwGjVis6FANQ1ctLe0yRALCdUn5wRxfvH1gW85z+vYgrqkMFpngi5CnUS/QjneLjNvqkV+mfVW6yiGkcH4yNwct8wh/U95kpo8sv6wkovgeOmlw4ugD7n9E0TfU1Y+qfURegpd8/4XA6H9X110+4XWkPCWyZ2zxjFENMxkOOA/yBf1fozGYebucMwrUC5XELXnDvuvR/XIfnVPtfqHpIzc2ChEtjvTZBdhd+v+aJ7X5kLp2C8JujdTWQDthDUlVmAMNcW5qKcBdgFmprQjZuA9UY3bdULLWcdOeY9XSdCdUYnCgUy0KISLEz6VEJYXwhjALFKJbQ8K69y1Cx8A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=kernel.org 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=AehbTQ2DArCaQU3TfzmWFSynk1AFGfsQpnZNtBQ7c+k=; b=ge7VKm+ZazD6vIyqD8ZKzGNl6ZJLkg7rdNvUOR8A1Hjb017T065Ptf9jku4arCCfVVv+sV8aUIv+ivKZkq/KrFmittqO5OyFp+xYmJEGhNLAe+I6aq8GDApCYA2XEUt9uaxQx0MI6MX8NcJeRukWxs9Vfi5hxkmrqOpS0SDAjuY= Received: from DS7PR03CA0117.namprd03.prod.outlook.com (2603:10b6:5:3b7::32) by CY8PR12MB7291.namprd12.prod.outlook.com (2603:10b6:930:54::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6043.36; Wed, 1 Feb 2023 06:58:43 +0000 Received: from DS1PEPF0000E65D.namprd02.prod.outlook.com (2603:10b6:5:3b7:cafe::b8) by DS7PR03CA0117.outlook.office365.com (2603:10b6:5:3b7::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6043.38 via Frontend Transport; Wed, 1 Feb 2023 06:58:43 +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 DS1PEPF0000E65D.mail.protection.outlook.com (10.167.18.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.6064.21 via Frontend Transport; Wed, 1 Feb 2023 06:58:43 +0000 Received: from beas.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, 1 Feb 2023 00:58:37 -0600 From: Wyes Karny <wyes.karny@amd.com> To: Rafael J Wysocki <rafael@kernel.org>, Huang Rui <ray.huang@amd.com>, Jonathan Corbet <corbet@lwn.net>, Viresh Kumar <viresh.kumar@linaro.org>, <Mario.Limonciello@amd.com>, <Perry.Yuan@amd.com> CC: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>, Bagas Sanjaya <bagasdotme@gmail.com>, <santosh.shukla@amd.com>, Len Brown <lenb@kernel.org>, Robert Moore <robert.moore@intel.com>, Borislav Petkov <bp@alien8.de>, Ananth Narayan <ananth.narayan@amd.com>, <gautham.shenoy@amd.com>, Tor Vic <torvic9@mailbox.org>, Wyes Karny <wyes.karny@amd.com> Subject: [PATCH v5 0/6] amd_pstate: Add guided autonomous mode support Date: Wed, 1 Feb 2023 06:58:17 +0000 Message-ID: <20230201065823.189828-1-wyes.karny@amd.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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: DS1PEPF0000E65D:EE_|CY8PR12MB7291:EE_ X-MS-Office365-Filtering-Correlation-Id: 9f71f3eb-553c-44b3-02cd-08db0421c1c5 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: fWJIfx0bxpE5y40soW4x4zuoWC51JOjeAQgrfsvOGwnWWo0VNYqKLon4WOXSUSQ/F+WF3EvXGtXxCg1H7Hr4RqbNrrq0M3CYndOCcNK2wjwUL4xd+YN5lYNwkx66xV2Gq894ALV6IhG9JtRbqAJg01bj6TgBcFiH7IsEeJr++PmTUsnXm6NzumTg07x5BOlpco7d5gIUAzMV5l0dZMI8RL5P7uxOHllaf7VWTj18g2l1hpoM/gU5BdoYgMPOKYMbgRskEw8JQv1saoJRyPUEQpHZNEqRIrT3rtOFMW9KiYSEAPjZvhGcc8H6J+V91i3xe8LcHK29R8AtHWy63awbtakwsWUmvGdML+OfDtUsrRFYmZAkUxlwYvHh5AFShiSgy9WR1IUW0eEIpiqI3aidKtbr0xCv5Z64WRuOdSSSnwzqr6YIaEYNJjaz36ReHjx5OLi0ImPkiLBFNq9ONIcRM2wXtlnUvNTVmrlgaoKXo4Y3IvqOfNYSKskTzb1DSc+NYRDDIk2pS5zyBgYRpyKvL/867PElQ6rgFriiaaSFfneI1bfhfsP72Oij6ysLxTjaWkUgY2QRrRzML6EhgxyyB4SoRqD4ptkbEWEsESr5ORiLNzRuD7LcjHVawP4BOkYwz0hz3z1/sFQDG04Pcgu5CljP6AcatifmeV1bGCGZP9lyC4MIHqR5awSi4lwI0auWohUm4ji4Psj4d4FeEyHFf9r+MCFLZPaINneJuiXxeaxDr1sjx3/Ja0gnApFjgPE/bnDjp6jrLinTkTBIv/zp4uhiJUC101OFX1++DvV43qXeHTqs8Z+1/1tlCaAAdp2C 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:(13230025)(4636009)(39860400002)(396003)(136003)(346002)(376002)(451199018)(40470700004)(36840700001)(46966006)(2906002)(82740400003)(36860700001)(356005)(186003)(26005)(81166007)(6636002)(16526019)(316002)(40460700003)(6666004)(110136005)(54906003)(478600001)(70206006)(36756003)(86362001)(82310400005)(40480700001)(2616005)(966005)(8936002)(8676002)(4326008)(70586007)(7696005)(1076003)(47076005)(41300700001)(44832011)(7416002)(83380400001)(336012)(5660300002)(426003)(36900700001);DIR:OUT;SFP:1101; X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Feb 2023 06:58:43.3621 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 9f71f3eb-553c-44b3-02cd-08db0421c1c5 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: DS1PEPF0000E65D.namprd02.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY8PR12MB7291 X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FORGED_SPF_HELO, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_NONE autolearn=no 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?1756611092801399749?= X-GMAIL-MSGID: =?utf-8?q?1756611092801399749?= |
Series |
amd_pstate: Add guided autonomous mode support
|
|
Message
Wyes Karny
Feb. 1, 2023, 6:58 a.m. UTC
From ACPI spec[1] below 3 modes for CPPC can be defined: 1. Non autonomous: OS scaling governor specifies operating frequency/ performance level through `Desired Performance` register and platform follows that. 2. Guided autonomous: OS scaling governor specifies min and max frequencies/ performance levels through `Minimum Performance` and `Maximum Performance` register, and platform can autonomously select an operating frequency in this range. 3. Fully autonomous: OS only hints (via EPP) to platform for the required energy performance preference for the workload and platform autonomously scales the frequency. Currently (1) is supported by amd_pstate as passive mode, and (3) is implemented by EPP support[2]. This change is to support (2). In guided autonomous mode the min_perf is based on the input from the scaling governor. For example, in case of schedutil this value depends on the current utilization. And max_perf is set to max capacity. To activate guided auto mode ``amd_pstate=guided`` command line parameter has to be passed in the kernel. Below are the results (normalized) of benchmarks with this patch: System: Genoa 96C 192T Kernel: 6.2.0-rc2 + EPP v12 + patch Scaling governor: schedutil ================ dbench comparisons ================ dbench result comparison: Here results are throughput (MB/s) Clients: acpi-cpufreq amd_pst+passive amd_pst+guided 1 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) 2 1.07 (0.00 pct) 1.06 (-0.93 pct) 1.07 (0.00 pct) 4 1.68 (0.00 pct) 1.70 (1.19 pct) 1.72 (2.38 pct) 8 2.61 (0.00 pct) 2.68 (2.68 pct) 2.76 (5.74 pct) 16 4.16 (0.00 pct) 4.24 (1.92 pct) 4.53 (8.89 pct) 32 5.98 (0.00 pct) 6.17 (3.17 pct) 7.30 (22.07 pct) 64 8.67 (0.00 pct) 8.99 (3.69 pct) 10.71 (23.52 pct) 128 11.98 (0.00 pct) 12.52 (4.50 pct) 14.67 (22.45 pct) 256 15.73 (0.00 pct) 16.13 (2.54 pct) 17.81 (13.22 pct) 512 15.77 (0.00 pct) 16.32 (3.48 pct) 16.39 (3.93 pct) dbench power comparison: Clients: acpi-cpufreq amd_pst+passive amd_pst+guided 1 1.00 (0.00 pct) 1.00 (0.00 pct) 1.04 (4.00 pct) 2 0.99 (0.00 pct) 0.97 (-2.02 pct) 1.02 (3.03 pct) 4 0.98 (0.00 pct) 0.98 (0.00 pct) 1.02 (4.08 pct) 8 0.98 (0.00 pct) 0.99 (1.02 pct) 1.02 (4.08 pct) 16 0.99 (0.00 pct) 1.00 (1.01 pct) 1.04 (5.05 pct) 32 1.02 (0.00 pct) 1.02 (0.00 pct) 1.07 (4.90 pct) 64 1.05 (0.00 pct) 1.05 (0.00 pct) 1.11 (5.71 pct) 128 1.08 (0.00 pct) 1.08 (0.00 pct) 1.15 (6.48 pct) 256 1.12 (0.00 pct) 1.12 (0.00 pct) 1.20 (7.14 pct) 512 1.18 (0.00 pct) 1.17 (-0.84 pct) 1.26 (6.77 pct) ================ git-source comparisons ================ git-source result comparison: Here results are throughput (compilations per 1000 sec) Threads: acpi-cpufreq amd_pst+passive amd_pst+guided 192 1.00 (0.00 pct) 0.93 (-7.00 pct) 1.00 (0.00 pct) git-source power comparison: Threads: acpi-cpufreq amd_pst+passive amd_pst+guided 192 1.00 (0.00 pct) 1.00 (0.00 pct) 0.96 (-4.00 pct) ================ kernbench comparisons ================ kernbench result comparison: Here results are throughput (compilations per 1000 sec) Load: acpi-cpufreq amd_pst+passive amd_pst+guided 32 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) 48 1.26 (0.00 pct) 1.28 (1.58 pct) 1.25 (-0.79 pct) 64 1.39 (0.00 pct) 1.47 (5.75 pct) 1.43 (2.87 pct) 96 1.48 (0.00 pct) 1.50 (1.35 pct) 1.49 (0.67 pct) 128 1.29 (0.00 pct) 1.32 (2.32 pct) 1.33 (3.10 pct) 192 1.17 (0.00 pct) 1.20 (2.56 pct) 1.21 (3.41 pct) 256 1.17 (0.00 pct) 1.18 (0.85 pct) 1.20 (2.56 pct) 384 1.16 (0.00 pct) 1.17 (0.86 pct) 1.21 (4.31 pct) kernbench power comparison: Clients: acpi-cpufreq amd_pst+passive amd_pst+guided 32 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.00 (0.00 pct) 48 0.87 (0.00 pct) 0.81 (-6.89 pct) 0.88 (1.14 pct) 64 0.81 (0.00 pct) 0.73 (-9.87 pct) 0.77 (-4.93 pct) 96 0.75 (0.00 pct) 0.74 (-1.33 pct) 0.75 (0.00 pct) 128 0.83 (0.00 pct) 0.79 (-4.81 pct) 0.83 (0.00 pct) 192 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) 256 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) 384 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) ================ tbench comparisons ================ tbench result comparison: Here results are throughput (MB/s) Clients: acpi-cpufreq amd_pst+passive amd_pst+guided 1 1.00 (0.00 pct) 0.70 (-30.00 pct) 1.37 (37.00 pct) 2 2.64 (0.00 pct) 1.39 (-47.34 pct) 2.70 (2.27 pct) 4 4.89 (0.00 pct) 2.75 (-43.76 pct) 5.28 (7.97 pct) 8 9.46 (0.00 pct) 5.42 (-42.70 pct) 10.22 (8.03 pct) 16 19.05 (0.00 pct) 10.42 (-45.30 pct) 19.94 (4.67 pct) 32 37.50 (0.00 pct) 20.23 (-46.05 pct) 36.87 (-1.68 pct) 64 61.24 (0.00 pct) 43.08 (-29.65 pct) 62.96 (2.80 pct) 128 67.16 (0.00 pct) 69.08 (2.85 pct) 67.34 (0.26 pct) 256 154.59 (0.00 pct) 162.33 (5.00 pct) 156.78 (1.41 pct) 512 154.02 (0.00 pct) 156.74 (1.76 pct) 153.48 (-0.35 pct) tbench power comparison: Clients: acpi-cpufreq amd_pst+passive amd_pst+guided 1 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.08 (8.00 pct) 2 1.04 (0.00 pct) 0.97 (-6.73 pct) 1.11 (6.73 pct) 4 1.12 (0.00 pct) 0.99 (-11.60 pct) 1.18 (5.35 pct) 8 1.25 (0.00 pct) 1.04 (-16.80 pct) 1.31 (4.80 pct) 16 1.53 (0.00 pct) 1.13 (-26.14 pct) 1.58 (3.26 pct) 32 2.01 (0.00 pct) 1.36 (-32.33 pct) 2.03 (0.99 pct) 64 2.58 (0.00 pct) 2.14 (-17.05 pct) 2.61 (1.16 pct) 128 2.80 (0.00 pct) 2.81 (0.35 pct) 2.81 (0.35 pct) 256 3.39 (0.00 pct) 3.43 (1.17 pct) 3.42 (0.88 pct) 512 3.44 (0.00 pct) 3.44 (0.00 pct) 3.44 (0.00 pct) Note: this series is based on top of EPP v12 [3] series Change log: v4 -> v5: - Rebased on top of EPP v12 series - Addressed comments form Mario regarding documentation - Picked up RB flags from Mario and Bagas Sanjaya v3 -> v4: - Fixed active mode low frequency issue reported by Peter Jung and Tor Vic - Documentation modification suggested by Bagas Sanjaya v2 -> v3: - Addressed review comments form Mario. - Picked up RB tag from Mario. - Rebase on top of EPP v11 [3]. v1 -> v2: - Fix issue with shared mem systems. - Rebase on top of EPP series. [1]: https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf [2]: https://lore.kernel.org/lkml/20221110175847.3098728-1-Perry.Yuan@amd.com/ [3]: https://lore.kernel.org/linux-pm/20230131090016.3970625-1-perry.yuan@amd.com/ Wyes Karny (6): acpi: cppc: Add min and max perf reg writing support acpi: cppc: Add auto select register read/write support cpufreq: amd_pstate: Add guided autonomous mode Documentation: amd_pstate: Move amd_pstate param to alphabetical order cpufreq: amd_pstate: Add guided mode control support via sysfs Documentation: amd_pstate: Update amd_pstate status sysfs for guided .../admin-guide/kernel-parameters.txt | 41 ++-- Documentation/admin-guide/pm/amd-pstate.rst | 34 +++- drivers/acpi/cppc_acpi.c | 121 +++++++++++- drivers/cpufreq/amd-pstate.c | 183 +++++++++++++----- include/acpi/cppc_acpi.h | 11 ++ include/linux/amd-pstate.h | 2 + 6 files changed, 311 insertions(+), 81 deletions(-)
Comments
On 01.02.23 06:58, Wyes Karny wrote: > From ACPI spec[1] below 3 modes for CPPC can be defined: > 1. Non autonomous: OS scaling governor specifies operating frequency/ > performance level through `Desired Performance` register and platform > follows that. > 2. Guided autonomous: OS scaling governor specifies min and max > frequencies/ performance levels through `Minimum Performance` and > `Maximum Performance` register, and platform can autonomously select an > operating frequency in this range. > 3. Fully autonomous: OS only hints (via EPP) to platform for the required > energy performance preference for the workload and platform autonomously > scales the frequency. > > Currently (1) is supported by amd_pstate as passive mode, and (3) is > implemented by EPP support[2]. This change is to support (2). > > In guided autonomous mode the min_perf is based on the input from the > scaling governor. For example, in case of schedutil this value depends > on the current utilization. And max_perf is set to max capacity. > > To activate guided auto mode ``amd_pstate=guided`` command line > parameter has to be passed in the kernel. > > Below are the results (normalized) of benchmarks with this patch: > System: Genoa 96C 192T > Kernel: 6.2.0-rc2 + EPP v12 + patch > Scaling governor: schedutil > > ================ dbench comparisons ================ > dbench result comparison: > Here results are throughput (MB/s) > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > 1 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) > 2 1.07 (0.00 pct) 1.06 (-0.93 pct) 1.07 (0.00 pct) > 4 1.68 (0.00 pct) 1.70 (1.19 pct) 1.72 (2.38 pct) > 8 2.61 (0.00 pct) 2.68 (2.68 pct) 2.76 (5.74 pct) > 16 4.16 (0.00 pct) 4.24 (1.92 pct) 4.53 (8.89 pct) > 32 5.98 (0.00 pct) 6.17 (3.17 pct) 7.30 (22.07 pct) > 64 8.67 (0.00 pct) 8.99 (3.69 pct) 10.71 (23.52 pct) > 128 11.98 (0.00 pct) 12.52 (4.50 pct) 14.67 (22.45 pct) > 256 15.73 (0.00 pct) 16.13 (2.54 pct) 17.81 (13.22 pct) > 512 15.77 (0.00 pct) 16.32 (3.48 pct) 16.39 (3.93 pct) > dbench power comparison: > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > 1 1.00 (0.00 pct) 1.00 (0.00 pct) 1.04 (4.00 pct) > 2 0.99 (0.00 pct) 0.97 (-2.02 pct) 1.02 (3.03 pct) > 4 0.98 (0.00 pct) 0.98 (0.00 pct) 1.02 (4.08 pct) > 8 0.98 (0.00 pct) 0.99 (1.02 pct) 1.02 (4.08 pct) > 16 0.99 (0.00 pct) 1.00 (1.01 pct) 1.04 (5.05 pct) > 32 1.02 (0.00 pct) 1.02 (0.00 pct) 1.07 (4.90 pct) > 64 1.05 (0.00 pct) 1.05 (0.00 pct) 1.11 (5.71 pct) > 128 1.08 (0.00 pct) 1.08 (0.00 pct) 1.15 (6.48 pct) > 256 1.12 (0.00 pct) 1.12 (0.00 pct) 1.20 (7.14 pct) > 512 1.18 (0.00 pct) 1.17 (-0.84 pct) 1.26 (6.77 pct) > > ================ git-source comparisons ================ > git-source result comparison: > Here results are throughput (compilations per 1000 sec) > Threads: acpi-cpufreq amd_pst+passive amd_pst+guided > 192 1.00 (0.00 pct) 0.93 (-7.00 pct) 1.00 (0.00 pct) > git-source power comparison: > Threads: acpi-cpufreq amd_pst+passive amd_pst+guided > 192 1.00 (0.00 pct) 1.00 (0.00 pct) 0.96 (-4.00 pct) > > ================ kernbench comparisons ================ > kernbench result comparison: > Here results are throughput (compilations per 1000 sec) > Load: acpi-cpufreq amd_pst+passive amd_pst+guided > 32 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) > 48 1.26 (0.00 pct) 1.28 (1.58 pct) 1.25 (-0.79 pct) > 64 1.39 (0.00 pct) 1.47 (5.75 pct) 1.43 (2.87 pct) > 96 1.48 (0.00 pct) 1.50 (1.35 pct) 1.49 (0.67 pct) > 128 1.29 (0.00 pct) 1.32 (2.32 pct) 1.33 (3.10 pct) > 192 1.17 (0.00 pct) 1.20 (2.56 pct) 1.21 (3.41 pct) > 256 1.17 (0.00 pct) 1.18 (0.85 pct) 1.20 (2.56 pct) > 384 1.16 (0.00 pct) 1.17 (0.86 pct) 1.21 (4.31 pct) > kernbench power comparison: > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > 32 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.00 (0.00 pct) > 48 0.87 (0.00 pct) 0.81 (-6.89 pct) 0.88 (1.14 pct) > 64 0.81 (0.00 pct) 0.73 (-9.87 pct) 0.77 (-4.93 pct) > 96 0.75 (0.00 pct) 0.74 (-1.33 pct) 0.75 (0.00 pct) > 128 0.83 (0.00 pct) 0.79 (-4.81 pct) 0.83 (0.00 pct) > 192 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > 256 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > 384 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > > ================ tbench comparisons ================ > tbench result comparison: > Here results are throughput (MB/s) > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > 1 1.00 (0.00 pct) 0.70 (-30.00 pct) 1.37 (37.00 pct) > 2 2.64 (0.00 pct) 1.39 (-47.34 pct) 2.70 (2.27 pct) > 4 4.89 (0.00 pct) 2.75 (-43.76 pct) 5.28 (7.97 pct) > 8 9.46 (0.00 pct) 5.42 (-42.70 pct) 10.22 (8.03 pct) > 16 19.05 (0.00 pct) 10.42 (-45.30 pct) 19.94 (4.67 pct) > 32 37.50 (0.00 pct) 20.23 (-46.05 pct) 36.87 (-1.68 pct) > 64 61.24 (0.00 pct) 43.08 (-29.65 pct) 62.96 (2.80 pct) > 128 67.16 (0.00 pct) 69.08 (2.85 pct) 67.34 (0.26 pct) > 256 154.59 (0.00 pct) 162.33 (5.00 pct) 156.78 (1.41 pct) > 512 154.02 (0.00 pct) 156.74 (1.76 pct) 153.48 (-0.35 pct) > tbench power comparison: > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > 1 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.08 (8.00 pct) > 2 1.04 (0.00 pct) 0.97 (-6.73 pct) 1.11 (6.73 pct) > 4 1.12 (0.00 pct) 0.99 (-11.60 pct) 1.18 (5.35 pct) > 8 1.25 (0.00 pct) 1.04 (-16.80 pct) 1.31 (4.80 pct) > 16 1.53 (0.00 pct) 1.13 (-26.14 pct) 1.58 (3.26 pct) > 32 2.01 (0.00 pct) 1.36 (-32.33 pct) 2.03 (0.99 pct) > 64 2.58 (0.00 pct) 2.14 (-17.05 pct) 2.61 (1.16 pct) > 128 2.80 (0.00 pct) 2.81 (0.35 pct) 2.81 (0.35 pct) > 256 3.39 (0.00 pct) 3.43 (1.17 pct) 3.42 (0.88 pct) > 512 3.44 (0.00 pct) 3.44 (0.00 pct) 3.44 (0.00 pct) > > Note: this series is based on top of EPP v12 [3] series > > Change log: > > v4 -> v5: > - Rebased on top of EPP v12 series > - Addressed comments form Mario regarding documentation > - Picked up RB flags from Mario and Bagas Sanjaya > > v3 -> v4: > - Fixed active mode low frequency issue reported by Peter Jung and Tor Vic > - Documentation modification suggested by Bagas Sanjaya > > v2 -> v3: > - Addressed review comments form Mario. > - Picked up RB tag from Mario. > - Rebase on top of EPP v11 [3]. > > v1 -> v2: > - Fix issue with shared mem systems. > - Rebase on top of EPP series. > > [1]: https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf > [2]: https://lore.kernel.org/lkml/20221110175847.3098728-1-Perry.Yuan@amd.com/ > [3]: https://lore.kernel.org/linux-pm/20230131090016.3970625-1-perry.yuan@amd.com/ > > Wyes Karny (6): > acpi: cppc: Add min and max perf reg writing support > acpi: cppc: Add auto select register read/write support > cpufreq: amd_pstate: Add guided autonomous mode > Documentation: amd_pstate: Move amd_pstate param to alphabetical order > cpufreq: amd_pstate: Add guided mode control support via sysfs > Documentation: amd_pstate: Update amd_pstate status sysfs for guided > > .../admin-guide/kernel-parameters.txt | 41 ++-- > Documentation/admin-guide/pm/amd-pstate.rst | 34 +++- > drivers/acpi/cppc_acpi.c | 121 +++++++++++- > drivers/cpufreq/amd-pstate.c | 183 +++++++++++++----- > include/acpi/cppc_acpi.h | 11 ++ > include/linux/amd-pstate.h | 2 + > 6 files changed, 311 insertions(+), 81 deletions(-) > I tested "active" mode on a Zen2, using EPP v12 and this series on top. Here is the output of 'cpupower frequency-info' run as root under full load: analyzing CPU 0: driver: amd_pstate_epp CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 550 MHz - 4.67 GHz available cpufreq governors: performance powersave current policy: frequency should be within 550 MHz and 4.67 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 4.18 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Boost States: 0 Total States: 3 Pstate-P0: 3800MHz Pstate-P1: 2800MHz Pstate-P2: 2200MHz Changing EPP mode via sysfs works. ---- Live-switching to "guided" mode via sysfs also seems to work fine: analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 20.0 us hardware limits: 550 MHz - 4.67 GHz available cpufreq governors: ondemand powersave performance schedutil current policy: frequency should be within 550 MHz and 4.67 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.71 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.67 GHz. AMD PSTATE Nominal Performance: 135. Nominal Frequency: 3.80 GHz. AMD PSTATE Lowest Non-linear Performance: 62. Lowest Non-linear Frequency: 1.74 GHz. AMD PSTATE Lowest Performance: 20. Lowest Frequency: 550 MHz. ---- Seems to work fine so far. Hope this helps. I can test more in detail and give you a Tested-by tag if wanted. Thanks, Tor Vic
Hi Tor Vic, On 01 Feb 18:35, Tor Vic wrote: > > On 01.02.23 06:58, Wyes Karny wrote: > > From ACPI spec[1] below 3 modes for CPPC can be defined: > > 1. Non autonomous: OS scaling governor specifies operating frequency/ > > performance level through `Desired Performance` register and platform > > follows that. > > 2. Guided autonomous: OS scaling governor specifies min and max > > frequencies/ performance levels through `Minimum Performance` and > > `Maximum Performance` register, and platform can autonomously select an > > operating frequency in this range. > > 3. Fully autonomous: OS only hints (via EPP) to platform for the required > > energy performance preference for the workload and platform autonomously > > scales the frequency. > > > > Currently (1) is supported by amd_pstate as passive mode, and (3) is > > implemented by EPP support[2]. This change is to support (2). > > > > In guided autonomous mode the min_perf is based on the input from the > > scaling governor. For example, in case of schedutil this value depends > > on the current utilization. And max_perf is set to max capacity. > > > > To activate guided auto mode ``amd_pstate=guided`` command line > > parameter has to be passed in the kernel. > > > > Below are the results (normalized) of benchmarks with this patch: > > System: Genoa 96C 192T > > Kernel: 6.2.0-rc2 + EPP v12 + patch > > Scaling governor: schedutil > > > > ================ dbench comparisons ================ > > dbench result comparison: > > Here results are throughput (MB/s) > > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > > 1 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) > > 2 1.07 (0.00 pct) 1.06 (-0.93 pct) 1.07 (0.00 pct) > > 4 1.68 (0.00 pct) 1.70 (1.19 pct) 1.72 (2.38 pct) > > 8 2.61 (0.00 pct) 2.68 (2.68 pct) 2.76 (5.74 pct) > > 16 4.16 (0.00 pct) 4.24 (1.92 pct) 4.53 (8.89 pct) > > 32 5.98 (0.00 pct) 6.17 (3.17 pct) 7.30 (22.07 pct) > > 64 8.67 (0.00 pct) 8.99 (3.69 pct) 10.71 (23.52 pct) > > 128 11.98 (0.00 pct) 12.52 (4.50 pct) 14.67 (22.45 pct) > > 256 15.73 (0.00 pct) 16.13 (2.54 pct) 17.81 (13.22 pct) > > 512 15.77 (0.00 pct) 16.32 (3.48 pct) 16.39 (3.93 pct) > > dbench power comparison: > > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > > 1 1.00 (0.00 pct) 1.00 (0.00 pct) 1.04 (4.00 pct) > > 2 0.99 (0.00 pct) 0.97 (-2.02 pct) 1.02 (3.03 pct) > > 4 0.98 (0.00 pct) 0.98 (0.00 pct) 1.02 (4.08 pct) > > 8 0.98 (0.00 pct) 0.99 (1.02 pct) 1.02 (4.08 pct) > > 16 0.99 (0.00 pct) 1.00 (1.01 pct) 1.04 (5.05 pct) > > 32 1.02 (0.00 pct) 1.02 (0.00 pct) 1.07 (4.90 pct) > > 64 1.05 (0.00 pct) 1.05 (0.00 pct) 1.11 (5.71 pct) > > 128 1.08 (0.00 pct) 1.08 (0.00 pct) 1.15 (6.48 pct) > > 256 1.12 (0.00 pct) 1.12 (0.00 pct) 1.20 (7.14 pct) > > 512 1.18 (0.00 pct) 1.17 (-0.84 pct) 1.26 (6.77 pct) > > > > ================ git-source comparisons ================ > > git-source result comparison: > > Here results are throughput (compilations per 1000 sec) > > Threads: acpi-cpufreq amd_pst+passive amd_pst+guided > > 192 1.00 (0.00 pct) 0.93 (-7.00 pct) 1.00 (0.00 pct) > > git-source power comparison: > > Threads: acpi-cpufreq amd_pst+passive amd_pst+guided > > 192 1.00 (0.00 pct) 1.00 (0.00 pct) 0.96 (-4.00 pct) > > > > ================ kernbench comparisons ================ > > kernbench result comparison: > > Here results are throughput (compilations per 1000 sec) > > Load: acpi-cpufreq amd_pst+passive amd_pst+guided > > 32 1.00 (0.00 pct) 1.01 (1.00 pct) 1.02 (2.00 pct) > > 48 1.26 (0.00 pct) 1.28 (1.58 pct) 1.25 (-0.79 pct) > > 64 1.39 (0.00 pct) 1.47 (5.75 pct) 1.43 (2.87 pct) > > 96 1.48 (0.00 pct) 1.50 (1.35 pct) 1.49 (0.67 pct) > > 128 1.29 (0.00 pct) 1.32 (2.32 pct) 1.33 (3.10 pct) > > 192 1.17 (0.00 pct) 1.20 (2.56 pct) 1.21 (3.41 pct) > > 256 1.17 (0.00 pct) 1.18 (0.85 pct) 1.20 (2.56 pct) > > 384 1.16 (0.00 pct) 1.17 (0.86 pct) 1.21 (4.31 pct) > > kernbench power comparison: > > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > > 32 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.00 (0.00 pct) > > 48 0.87 (0.00 pct) 0.81 (-6.89 pct) 0.88 (1.14 pct) > > 64 0.81 (0.00 pct) 0.73 (-9.87 pct) 0.77 (-4.93 pct) > > 96 0.75 (0.00 pct) 0.74 (-1.33 pct) 0.75 (0.00 pct) > > 128 0.83 (0.00 pct) 0.79 (-4.81 pct) 0.83 (0.00 pct) > > 192 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > > 256 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > > 384 0.92 (0.00 pct) 0.88 (-4.34 pct) 0.92 (0.00 pct) > > > > ================ tbench comparisons ================ > > tbench result comparison: > > Here results are throughput (MB/s) > > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > > 1 1.00 (0.00 pct) 0.70 (-30.00 pct) 1.37 (37.00 pct) > > 2 2.64 (0.00 pct) 1.39 (-47.34 pct) 2.70 (2.27 pct) > > 4 4.89 (0.00 pct) 2.75 (-43.76 pct) 5.28 (7.97 pct) > > 8 9.46 (0.00 pct) 5.42 (-42.70 pct) 10.22 (8.03 pct) > > 16 19.05 (0.00 pct) 10.42 (-45.30 pct) 19.94 (4.67 pct) > > 32 37.50 (0.00 pct) 20.23 (-46.05 pct) 36.87 (-1.68 pct) > > 64 61.24 (0.00 pct) 43.08 (-29.65 pct) 62.96 (2.80 pct) > > 128 67.16 (0.00 pct) 69.08 (2.85 pct) 67.34 (0.26 pct) > > 256 154.59 (0.00 pct) 162.33 (5.00 pct) 156.78 (1.41 pct) > > 512 154.02 (0.00 pct) 156.74 (1.76 pct) 153.48 (-0.35 pct) > > tbench power comparison: > > Clients: acpi-cpufreq amd_pst+passive amd_pst+guided > > 1 1.00 (0.00 pct) 0.97 (-3.00 pct) 1.08 (8.00 pct) > > 2 1.04 (0.00 pct) 0.97 (-6.73 pct) 1.11 (6.73 pct) > > 4 1.12 (0.00 pct) 0.99 (-11.60 pct) 1.18 (5.35 pct) > > 8 1.25 (0.00 pct) 1.04 (-16.80 pct) 1.31 (4.80 pct) > > 16 1.53 (0.00 pct) 1.13 (-26.14 pct) 1.58 (3.26 pct) > > 32 2.01 (0.00 pct) 1.36 (-32.33 pct) 2.03 (0.99 pct) > > 64 2.58 (0.00 pct) 2.14 (-17.05 pct) 2.61 (1.16 pct) > > 128 2.80 (0.00 pct) 2.81 (0.35 pct) 2.81 (0.35 pct) > > 256 3.39 (0.00 pct) 3.43 (1.17 pct) 3.42 (0.88 pct) > > 512 3.44 (0.00 pct) 3.44 (0.00 pct) 3.44 (0.00 pct) > > > > Note: this series is based on top of EPP v12 [3] series > > > > Change log: > > > > v4 -> v5: > > - Rebased on top of EPP v12 series > > - Addressed comments form Mario regarding documentation > > - Picked up RB flags from Mario and Bagas Sanjaya > > > > v3 -> v4: > > - Fixed active mode low frequency issue reported by Peter Jung and Tor Vic > > - Documentation modification suggested by Bagas Sanjaya > > > > v2 -> v3: > > - Addressed review comments form Mario. > > - Picked up RB tag from Mario. > > - Rebase on top of EPP v11 [3]. > > > > v1 -> v2: > > - Fix issue with shared mem systems. > > - Rebase on top of EPP series. > > > > [1]: https://uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf > > [2]: https://lore.kernel.org/lkml/20221110175847.3098728-1-Perry.Yuan@amd.com/ > > [3]: https://lore.kernel.org/linux-pm/20230131090016.3970625-1-perry.yuan@amd.com/ > > > > Wyes Karny (6): > > acpi: cppc: Add min and max perf reg writing support > > acpi: cppc: Add auto select register read/write support > > cpufreq: amd_pstate: Add guided autonomous mode > > Documentation: amd_pstate: Move amd_pstate param to alphabetical order > > cpufreq: amd_pstate: Add guided mode control support via sysfs > > Documentation: amd_pstate: Update amd_pstate status sysfs for guided > > > > .../admin-guide/kernel-parameters.txt | 41 ++-- > > Documentation/admin-guide/pm/amd-pstate.rst | 34 +++- > > drivers/acpi/cppc_acpi.c | 121 +++++++++++- > > drivers/cpufreq/amd-pstate.c | 183 +++++++++++++----- > > include/acpi/cppc_acpi.h | 11 ++ > > include/linux/amd-pstate.h | 2 + > > 6 files changed, 311 insertions(+), 81 deletions(-) > > > > I tested "active" mode on a Zen2, using EPP v12 and this series on top. > > Here is the output of 'cpupower frequency-info' run as root under full load: > > analyzing CPU 0: > driver: amd_pstate_epp > CPUs which run at the same hardware frequency: 0 > CPUs which need to have their frequency coordinated by software: 0 > maximum transition latency: Cannot determine or is not supported. > hardware limits: 550 MHz - 4.67 GHz > available cpufreq governors: performance powersave > current policy: frequency should be within 550 MHz and 4.67 GHz. > The governor "powersave" may decide which speed to use > within this range. > current CPU frequency: Unable to call hardware > current CPU frequency: 4.18 GHz (asserted by call to kernel) > boost state support: > Supported: yes > Active: yes > Boost States: 0 > Total States: 3 > Pstate-P0: 3800MHz > Pstate-P1: 2800MHz > Pstate-P2: 2200MHz > > Changing EPP mode via sysfs works. > > ---- > > Live-switching to "guided" mode via sysfs also seems to work fine: > > analyzing CPU 0: > driver: amd-pstate > CPUs which run at the same hardware frequency: 0 > CPUs which need to have their frequency coordinated by software: 0 > maximum transition latency: 20.0 us > hardware limits: 550 MHz - 4.67 GHz > available cpufreq governors: ondemand powersave performance schedutil > current policy: frequency should be within 550 MHz and 4.67 GHz. > The governor "ondemand" may decide which speed to use > within this range. > current CPU frequency: Unable to call hardware > current CPU frequency: 3.71 GHz (asserted by call to kernel) > boost state support: > Supported: yes > Active: yes > AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.67 GHz. > AMD PSTATE Nominal Performance: 135. Nominal Frequency: 3.80 GHz. > AMD PSTATE Lowest Non-linear Performance: 62. Lowest Non-linear > Frequency: 1.74 GHz. > AMD PSTATE Lowest Performance: 20. Lowest Frequency: 550 MHz. > > ---- > > Seems to work fine so far. > Hope this helps. > I can test more in detail and give you a Tested-by tag if wanted. Thanks for testing this. Please feel free to add Tested-by tag after your testing done. Thanks, Wyes > > Thanks, > > Tor Vic