Received: by 10.223.185.116 with SMTP id b49csp524863wrg; Wed, 14 Feb 2018 02:53:46 -0800 (PST) X-Google-Smtp-Source: AH8x224zSEttEi4WkbfOcQ62rhxBrrfPhjxm3pR7Ywyl2l6uHrQ0709xDXzvCPLxyb0QypC17Wx/ X-Received: by 2002:a17:902:aa5:: with SMTP id 34-v6mr4139078plp.429.1518605626042; Wed, 14 Feb 2018 02:53:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518605626; cv=none; d=google.com; s=arc-20160816; b=oNbsE/i3C/GHMTduEXxi/Jqx0leWu5/k0n2Abrf4byWAPjnRTZEll0+b2XHvRDimV/ wMkbPApkSaNMHw5V8oZwIWQ0dCy7lf4/4WR/MMY6frv5qex4dHKJ3VOSDhIsQGwcutSI HXCOq+C502419yo0V59R3GT6bkIfBN4CB7Ly2qD1IsSijzqwwAE+Mkg4Ak+BjaNwfpVS WY5NRSozp5IqgLRka3ETtn375lqt6Uewq/uoniQZ3hNPLoK/6uM0X2BtrJproScdHfRI CEENfb4Z2zZOhdueYURLKX9T2kpE+mv2627iTZYwWxmPVY8LtTjy+V8D64Mr8cuonTq4 CurA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=NYd8SLje3r3LRClJAnAY7uBO1MdMjfEimxfaMU5w1yY=; b=dIronIrt/tHmjHUF79WyuZn2ypNco2ZkHyJBxTQ4hddl5kL1SXtQ9sGTHn8S+6294A GUJ88+3WIMHjbxYNTYzKEMfgIAAnfa2XmEElx3fhLaxr+IcOUMpeLi3dqa0zh3tGHGUh 1OZn889KCWP1oGI3Gad2NC/d4Dx+5vdssd6W8bk/oHmVZsy4D8tJPjl3zaUMvpMy4CaX IoNRmwhs4naeBZn9PcPKA61Dx6qszHsN0rzQfMFU2q2KuD+UvMGVKjSmbVKFjX4EKC5n fds2LqMYhSOadUfvDl4ak0YE/ka5wRIGxhsoNf+pqaOLgah5v02adu7M6pdjmClWmIu0 2JyQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v185si1169615pgb.185.2018.02.14.02.53.31; Wed, 14 Feb 2018 02:53:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967206AbeBNKww (ORCPT + 99 others); Wed, 14 Feb 2018 05:52:52 -0500 Received: from cloudserver094114.home.pl ([79.96.170.134]:50918 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967114AbeBNKwu (ORCPT ); Wed, 14 Feb 2018 05:52:50 -0500 Received: from 79.184.255.223.ipv4.supernova.orange.pl (79.184.255.223) (HELO aspire.rjw.lan) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83) id 476578bc9629f2b1; Wed, 14 Feb 2018 11:52:48 +0100 From: "Rafael J. Wysocki" To: Aishwarya Pant Cc: Daniel Lezcano , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Jonathan Corbet , Greg KH , Julia Lawall Subject: Re: [PATCH v5] Documentation/ABI: update cpuidle sysfs documentation Date: Wed, 14 Feb 2018 11:51:00 +0100 Message-ID: <6470168.Bc58CWhkOs@aspire.rjw.lan> In-Reply-To: <20180207133436.GA7440@mordor.localdomain> References: <20180207133436.GA7440@mordor.localdomain> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, February 7, 2018 2:34:36 PM CET Aishwarya Pant wrote: > Update cpuidle documentation using git logs and existing documentation > in Documentation/cpuidle/sysfs.txt. This might be useful for scripting > and tracking changes in the ABI. > > Signed-off-by: Aishwarya Pant > --- > Changes in v5: > - Update contact information- LKML -> power management mailing list > v4: > - Fix patch formatting > v3: > - Fix subject line > v2: > - Merge cpuidle_sysfs_switch attributes' description with the previous > entry. > > Documentation/ABI/testing/sysfs-devices-system-cpu | 77 +++++++++++++++++++++- > 1 file changed, 75 insertions(+), 2 deletions(-) > > diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu > index bfd29bc8d37a..4ed63b6cfb15 100644 > --- a/Documentation/ABI/testing/sysfs-devices-system-cpu > +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu > @@ -108,6 +108,8 @@ Description: CPU topology files that describe a logical CPU's relationship > > What: /sys/devices/system/cpu/cpuidle/current_driver > /sys/devices/system/cpu/cpuidle/current_governer_ro > + /sys/devices/system/cpu/cpuidle/available_governors > + /sys/devices/system/cpu/cpuidle/current_governor > Date: September 2007 > Contact: Linux kernel mailing list > Description: Discover cpuidle policy and mechanism > @@ -119,13 +121,84 @@ Description: Discover cpuidle policy and mechanism > Idle policy (governor) is differentiated from idle mechanism > (driver) > > - current_driver: displays current idle mechanism > + current_driver: (RO) displays current idle mechanism > > - current_governor_ro: displays current idle policy > + current_governor_ro: (RO) displays current idle policy > + > + With the cpuidle_sysfs_switch boot option enabled (meant for > + developer testing), the following three attributes are visible > + instead: > + > + current_driver: same as described above > + > + available_governors: (RO) displays a space separated list of > + available governors > + > + current_governor: (RW) displays current idle policy. Users can > + switch the governor at runtime by writing to this file. > > See files in Documentation/cpuidle/ for more information. > > > +What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/name > + /sys/devices/system/cpu/cpuX/cpuidle/stateN/latency > + /sys/devices/system/cpu/cpuX/cpuidle/stateN/power > + /sys/devices/system/cpu/cpuX/cpuidle/stateN/time > + /sys/devices/system/cpu/cpuX/cpuidle/stateN/usage > +Date: September 2007 > +KernelVersion: v2.6.24 > +Contact: Linux power management list > +Description: > + The directory /sys/devices/system/cpu/cpuX/cpuidle contains per > + logical CPU specific cpuidle information for each online cpu X. > + The processor idle states which are available for use have the > + following attributes: > + > + name: (RO) Name of the idle state (string). > + > + latency: (RO) The latency to exit out of this idle state (in > + microseconds). > + > + power: (RO) The power consumed while in this idle state (in > + milliwatts). > + > + time: (RO) The total time spent in this idle state (in microseconds). > + > + usage: (RO) Number of times this state was entered (a count). > + > + > +What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/desc > +Date: February 2008 > +KernelVersion: v2.6.25 > +Contact: Linux power management list > +Description: > + (RO) A small description about the idle state (string). > + > + > +What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/disable > +Date: March 2012 > +KernelVersion: v3.10 > +Contact: Linux power management list > +Description: > + (RW) Option to disable this idle state (bool). The behavior and > + the effect of the disable variable depends on the implementation > + of a particular governor. In the ladder governor, for example, > + it is not coherent, i.e. if one is disabling a light state, then > + all deeper states are disabled as well, but the disable variable > + does not reflect it. Likewise, if one enables a deep state but a > + lighter state still is disabled, then this has no effect. > + > + > +What: /sys/devices/system/cpu/cpuX/cpuidle/stateN/residency > +Date: March 2014 > +KernelVersion: v3.15 > +Contact: Linux power management list > +Description: > + (RO) Display the target residency i.e. the minimum amount of > + time (in microseconds) this cpu should spend in this idle state > + to make the transition worth the effort. > + > + > What: /sys/devices/system/cpu/cpu#/cpufreq/* > Date: pre-git history > Contact: linux-pm@vger.kernel.org > Applied, thanks!