[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [PATCH v4 12/15] tools/xenpm: Print CPPC parameters for amd-cppc driver


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Penny, Zheng" <penny.zheng@xxxxxxx>
  • Date: Tue, 20 May 2025 09:39:24 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=W7cIxaU2MzYQ8UAcknvikbu/La2Z5BfuQvvrMNXyH70=; b=Gt67cVwfqkVYOZIsmEWKSCcoY2gj5laoJGiWOZU2zuC8OiNqCOsKx16aNynoiGhOdzP93e0i5QkeacqydZJ1m/RDcc47gi40WuCnxUSbGwh6PmnbCOm5CPsCObk8X1P1QxzLPECmq9pcsT/LCK+B1WEZPs4edg6Nt19sTbOLV/xIBXsbze43J5NIaTzJaTj+mh+tknvVrLlbwM558G63U5JZwPWR/ruLTQ5gLl/TF4FrPud7H4KAnyRbUojFS0fazhyl1uiaWPG6gXM/8BxKXCm2Zo8U+ZsS3tGmzeui3OQMnR7WuIBsE5cdgVTwiyo5RetTnihwkAByMLnGyRIllA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=khpucjU/1tw+VdX57xl6BzsNWGejTFZ4ysonXrwRRgy9SER9nAJ5o2jaO5vJgamzJAXVwo/GypvC/13VjxfjG5uGFt/Lc1kYS2tOYevwOpaxPJZwXN+w1RJ07oHK0HrmtFgPILpH8FDT3UdWkfE3V8gVN0kCbvTeATLoNoI6CUhZOnN9PJdWMY3iS949GozbUYamsLtIitMM8/RzZuApa08D13e8fqvngljXMtsbeDEMGQEvKsOKXIfdqp/WXkOcRG4dHzy11RyqqZ9NQMmJqOZlhId+xx2QlEUC3WJgpDb/urRFckRd/GGHTqCDxWJEydrhspfhKEbchC8bNHdu8w==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Cc: "Huang, Ray" <Ray.Huang@xxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 20 May 2025 09:39:38 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Msip_labels: MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_ActionId=76eb52f0-92d7-4b33-b17a-a123cb5fdf07;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_ContentBits=0;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_Enabled=true;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_Method=Privileged;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_Name=Open Source;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_SetDate=2025-05-20T09:34:01Z;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_SiteId=3dd8961f-e488-4e60-8e11-a82d994e183d;MSIP_Label_f265efc6-e181-49d6-80f4-fae95cf838a0_Tag=10, 0, 1, 1;
  • Thread-index: AQHbrRCuBHJz/5ZpqUqHhc0gdq6hGrO8VLYAgA1zbxCABpifAIAK/PXggAAYTwCAAAAz8A==
  • Thread-topic: [PATCH v4 12/15] tools/xenpm: Print CPPC parameters for amd-cppc driver

[Public]

> -----Original Message-----
> From: Jan Beulich <jbeulich@xxxxxxxx>
> Sent: Tuesday, May 20, 2025 5:18 PM
> To: Penny, Zheng <penny.zheng@xxxxxxx>
> Cc: Huang, Ray <Ray.Huang@xxxxxxx>; Anthony PERARD
> <anthony.perard@xxxxxxxxxx>; xen-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [PATCH v4 12/15] tools/xenpm: Print CPPC parameters for amd-cppc
> driver
>
> On 20.05.2025 10:22, Penny, Zheng wrote:
> >> -----Original Message-----
> >> From: Jan Beulich <jbeulich@xxxxxxxx>
> >> Sent: Tuesday, May 13, 2025 4:03 PM
> >>
> >> On 09.05.2025 08:36, Penny, Zheng wrote:
> >>>> -----Original Message-----
> >>>> From: Jan Beulich <jbeulich@xxxxxxxx>
> >>>> Sent: Wednesday, April 30, 2025 9:55 PM
> >>>>
> >>>> On 14.04.2025 09:40, Penny Zheng wrote:
> >>>>> HWP, amd-cppc, amd-cppc-epp are all the implementation of ACPI
> >>>>> CPPC (Collaborative Processor Performace Control), so we introduce
> >>>>> cppc_mode flag to print CPPC-related para.
> >>>>>
> >>>>> And HWP and amd-cppc-epp are both governor-less driver, so we
> >>>>> introduce hw_auto flag to bypass governor-related print.
> >>>>
> >>>> But in the EPP driver you use the information which governor is active.
> >>>
> >>> We want to have a one-one mapping between governor and epp value,
> >>> such as, If users choose performance governor, no matter via "xenpm"
> >>> or cmdline, users want maximum performance, We set epp with 0 to
> >>> meet the
> >> expectation.
> >>> And if users choose powersave governor, users want the least power
> >>> consumption, then we shall set epp with 255 to meet the expectation.
> >>
> >> That's all fine, but completely misses the point of my question: If
> >> the governor is relevant, why would you bypass respective printing?
> >>
> >
> > The only useful info in governor for epp mode, IMO, is its name.
> > I deduce which performance policy user wants to apply through which governor
> they choose.
> > If user chooses performance governor, they want maximum performance.
> > If user chooses powersave governor, they want the least power
> > consumption I could only provide appropriate epp value in above two 
> > scenarios.
> > ondemand and userspace are forbidden choices, and if users specify
> > such options in cmdline, I shall give warning message to say  that
> > amd-cppc in active mode is governor-less, and users could set epp values on
> runtime to specify bias towards performance or efficiency.
> >
> > If above is messy, I could also totally forbid governor thing for active 
> > mode...
> wdyt?
>
> Then how would one pick between performance and powersave?

In hwp, we defined
"
#define CPPC_ENERGY_PERF_BALANCE         0x80
"
to provide the balanced value. Users could run "xenpm set-cpufreq-cppc balance" 
to achieve on runtime
Any other specific epp value, users shall run "xenpm set-cpufreq-cppc 
energy-perf:N" to achieve
We didn't provide any options in cmdline, so I tried to re-use the governor to 
achieve a few. hmmm,
now it seems it brings confusion....

>
> Jan

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.