From: Thomas Renninger <trenn@suse.de>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: problem about ACPI processor procfs
Date: Tue, 27 Feb 2007 15:45:47 +0100 [thread overview]
Message-ID: <1172587547.10619.429.camel@d36.suse.de> (raw)
In-Reply-To: <58A36151585E4047913F40517D307BAE43BDE8@pdsmsx404.ccr.corp.intel.com>
On Tue, 2007-02-27 at 17:33 +0800, Zhang, Rui wrote:
> Hello, list
>
> I met some problems when duplicating ACPI processor procfs interface in sysfs.
> #cat /proc/acpi/processor/CPU0/limit
> Active limit: P0:T0
> User limit: P0:T0
> Thermal limit: P0,T0
>
> IMO, "Tx" is easy to understand. It indicates the active T-state, T-state set by user and T-state set by thermal (in passive mode).
>
> But what does the "Px" stand for? After reading the code in processor_thermal.c, I don't think user or thermal will change its value.
> And I don't know if it's still needed when porting to sysfs.
Px are P-states, this is cpufreq.
Writing to it will probably interfere with /sys/devices/../cpufreq/*.
x should correspond to the amount of entries in
/sys/devices/../cpufreq/scaling_available_frequencies.
Can't we just get rid of this? Is there any userspace prog that made use
of this in /proc and if was it really useful in any way?
Thomas
next prev parent reply other threads:[~2007-02-27 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 9:33 problem about ACPI processor procfs Zhang, Rui
2007-02-27 14:45 ` Thomas Renninger [this message]
2007-02-27 15:19 ` Pallipadi, Venkatesh
2007-03-06 8:00 ` Zhang Rui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172587547.10619.429.camel@d36.suse.de \
--to=trenn@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.