From: Thomas Renninger <trenn@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Felix Schnizlein <FSchnizlein@suse.com>,
yanmin.zhang@intel.com, linux-kernel@vger.kernel.org,
x86@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] Implement sysfs based cpuinfo for x86 cpus.
Date: Fri, 09 Jun 2017 15:28:45 +0200 [thread overview]
Message-ID: <1956244.ag6eOoJRYo@skinner> (raw)
In-Reply-To: <20170608182401.GC13995@kroah.com>
On Thursday, June 08, 2017 08:24:01 PM Greg KH wrote:
> On Thu, Jun 08, 2017 at 06:56:14PM +0200, Felix Schnizlein wrote:
> > ---
> > arch/x86/kernel/Makefile | 1 +
> > arch/x86/kernel/cpuinfo_sysfs.c | 166
++++++++++++++++++++++++++++++++++++++++
> > drivers/base/cpuinfo.c | 4 -
> > 3 files changed, 167 insertions(+), 4 deletions(-)
> > create mode 100644 arch/x86/kernel/cpuinfo_sysfs.c
> >
>
> When you add new sysfs entries, you have to also add new
> Documentation/ABI/ entries.
This one seem to be rather unmaintained?
There even is:
Documentation/ABI/stable/sysfs-devices-system-cpu
this patchset would have to add:
Documentation/ABI/stable/sysfs-devices-system-cpu-cpuinfo
then.
But:
Documentation/ABI/stable/sysfs-devices-system-cpu
describes
/sys/devices/system/cpu/dscr_default
and
/sys/devices/system/cpu/cpu[0-9]+/dscr
which I have never seen.
Much more important values in there like:
/sys/devices/system/cpu/topology
/sys/devices/system/cpu/microcode
/sys/devices/system/cpu/cpuidle
/sys/devices/system/cpu/cpufreq
/sys/devices/system/cpu/{online,offline}
are not described there at all.
I wonder whether .../cpu/dscr_default still exists in the
kernel, a quick grep did not reveal anything.
A
Source:
tag would be a nice non-optional addition in the README.
We can also send definitions for topology/microcode/cache/..
to catch up a bit there again, not sure that makes much sense.
Be aware that the output of /proc/cpuinfo is rather arbitrary
depending on architecure and some build options.
Thomas
next prev parent reply other threads:[~2017-06-09 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1496940975-9164-1-git-send-email-fschnizlein@suse.com>
[not found] ` <1496940975-9164-3-git-send-email-fschnizlein@suse.com>
2017-06-08 18:24 ` [RFC PATCH 2/3] Implement sysfs based cpuinfo for x86 cpus Greg KH
2017-06-09 13:28 ` Thomas Renninger [this message]
2017-06-09 15:22 ` Brice Goglin
2017-06-08 18:26 ` Greg KH
[not found] ` <1496940975-9164-4-git-send-email-fschnizlein@suse.com>
2017-06-08 18:25 ` [RFC PATCH 3/3] Add deprecation warning to cpuinfo proc Greg KH
[not found] ` <1496940975-9164-2-git-send-email-fschnizlein@suse.com>
2017-06-08 18:22 ` [RFC PATCH 1/3] Add sysfs based cpuinfo structure Greg KH
2017-06-08 18:25 ` Greg KH
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=1956244.ag6eOoJRYo@skinner \
--to=trenn@suse.de \
--cc=FSchnizlein@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@vger.kernel.org \
--cc=yanmin.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox