From: Thomas Renninger <trenn@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Will Deacon <will@kernel.org>,
Felix Schnizlein <fschnizlein@suse.com>,
linux-kernel@vger.kernel.org,
Felix Schnizlein <fschnizlein@suse.de>,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux@armlinux.org.uk, will.deacon@arm.com, x86@kernel.org
Subject: Re: [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64
Date: Tue, 10 Dec 2019 17:24:29 +0100 [thread overview]
Message-ID: <2363489.ZvMXcgbkLu@skinner.arch.suse.de> (raw)
In-Reply-To: <20191210144737.GB3975980@kroah.com>
On Tuesday, December 10, 2019 3:47:37 PM CET Greg KH wrote:
> On Tue, Dec 10, 2019 at 02:33:07PM +0100, Thomas Renninger wrote:
> > On Monday, December 9, 2019 6:38:05 PM CET Will Deacon wrote:
> > > On Mon, Dec 09, 2019 at 12:28:44PM +0100, Thomas Renninger wrote:
> > > > On Monday, December 9, 2019 11:31:11 AM CET Will Deacon wrote:
> > > > > On Fri, Dec 06, 2019 at 05:24:21PM +0100, Thomas Renninger wrote:
> > > > > > From: Felix Schnizlein <fschnizlein@suse.de>
> > > > > >
> > > > > > Export all information from /proc/cpuinfo to sysfs:
> > > > > > implementer, architecture, variant, part, revision,
> > > > > > bogomips and flags are exported.
> > > > > >
> > > > > > Example:
> > > > > > /sys/devices/system/cpu/cpu1/info/:[0]# head *
> > > >
> > > > ...
> > > >
> > > > > > ==> flags <==
> > > > > > fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid asimdrdm
> > > >
> > > > ...
> > > >
> > > > > I don't understand why we need this on arm64
> >
> > Again: proc is moving to sys.
>
> No. New stuff is to be added to /sys/, don't add new things to /proc
> unless it deals with processes.
>
> There is no mass-migration of existing /proc files to sysfs for no good
> reason.
>
> > You probably export feature flags in /proc/cpuinfo for a good reason.
> > So where in sysfs should this show up?
>
> Why does it have to live in sysfs if it is already in /proc and parsed
> properly by tools?
Parsing /proc/cpuinfo is the best example why we have sysfs...
Most important things have already been ported:
microcode : 0x10
cat /sys/devices/system/cpu/cpu1/microcode/version
0x10
physical id : 0
siblings : 8
core id : 1
cpu cores : 4
...
/sys/devices/system/cpu/cpu1/topology/
clflush size : 64
cache_alignment : 64
...
/sys/devices/system/cpu/cpu1/cache/
Only missing important info which still is needed is family/model/stepping,
name, bugs and flags
cpufreq also got ported to sysfs quite some time ago already.
I am aware that /proc/cpuinfo won't vanish...
...the next decade. Still I am confident I will still see this.
Still relevant info which is accessed by (newly written) userspace tools
should read out info via sysfs.
Beside microcode, topology, cache, cpufreq,...
info, there now is also family, model, stepping, bugs, flags and name
There rest is (from my perspective) really old ugly stuff and not needed
anymore by recent tools.
Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Renninger <trenn@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-arch@vger.kernel.org,
Felix Schnizlein <fschnizlein@suse.de>,
Felix Schnizlein <fschnizlein@suse.com>,
x86@kernel.org, will.deacon@arm.com,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64
Date: Tue, 10 Dec 2019 17:24:29 +0100 [thread overview]
Message-ID: <2363489.ZvMXcgbkLu@skinner.arch.suse.de> (raw)
In-Reply-To: <20191210144737.GB3975980@kroah.com>
On Tuesday, December 10, 2019 3:47:37 PM CET Greg KH wrote:
> On Tue, Dec 10, 2019 at 02:33:07PM +0100, Thomas Renninger wrote:
> > On Monday, December 9, 2019 6:38:05 PM CET Will Deacon wrote:
> > > On Mon, Dec 09, 2019 at 12:28:44PM +0100, Thomas Renninger wrote:
> > > > On Monday, December 9, 2019 11:31:11 AM CET Will Deacon wrote:
> > > > > On Fri, Dec 06, 2019 at 05:24:21PM +0100, Thomas Renninger wrote:
> > > > > > From: Felix Schnizlein <fschnizlein@suse.de>
> > > > > >
> > > > > > Export all information from /proc/cpuinfo to sysfs:
> > > > > > implementer, architecture, variant, part, revision,
> > > > > > bogomips and flags are exported.
> > > > > >
> > > > > > Example:
> > > > > > /sys/devices/system/cpu/cpu1/info/:[0]# head *
> > > >
> > > > ...
> > > >
> > > > > > ==> flags <==
> > > > > > fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid asimdrdm
> > > >
> > > > ...
> > > >
> > > > > I don't understand why we need this on arm64
> >
> > Again: proc is moving to sys.
>
> No. New stuff is to be added to /sys/, don't add new things to /proc
> unless it deals with processes.
>
> There is no mass-migration of existing /proc files to sysfs for no good
> reason.
>
> > You probably export feature flags in /proc/cpuinfo for a good reason.
> > So where in sysfs should this show up?
>
> Why does it have to live in sysfs if it is already in /proc and parsed
> properly by tools?
Parsing /proc/cpuinfo is the best example why we have sysfs...
Most important things have already been ported:
microcode : 0x10
cat /sys/devices/system/cpu/cpu1/microcode/version
0x10
physical id : 0
siblings : 8
core id : 1
cpu cores : 4
...
/sys/devices/system/cpu/cpu1/topology/
clflush size : 64
cache_alignment : 64
...
/sys/devices/system/cpu/cpu1/cache/
Only missing important info which still is needed is family/model/stepping,
name, bugs and flags
cpufreq also got ported to sysfs quite some time ago already.
I am aware that /proc/cpuinfo won't vanish...
...the next decade. Still I am confident I will still see this.
Still relevant info which is accessed by (newly written) userspace tools
should read out info via sysfs.
Beside microcode, topology, cache, cpufreq,...
info, there now is also family, model, stepping, bugs, flags and name
There rest is (from my perspective) really old ugly stuff and not needed
anymore by recent tools.
Thomas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-10 16:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 16:24 [PATCH v5 0/3] sysfs: add sysfs based cpuinfo Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:24 ` [PATCH 1/3] cpuinfo: add sysfs based arch independent cpuinfo framework Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:33 ` Greg KH
2019-12-06 16:33 ` Greg KH
2019-12-06 16:33 ` Greg KH
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:24 ` [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86 Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:36 ` Greg KH
2019-12-06 16:36 ` Greg KH
2019-12-10 20:48 ` Thomas Gleixner
2019-12-10 20:48 ` Thomas Gleixner
2019-12-10 20:53 ` Greg KH
2019-12-10 20:53 ` Greg KH
2019-12-11 10:42 ` Thomas Renninger
2019-12-11 10:42 ` Thomas Renninger
2019-12-11 13:56 ` Greg KH
2019-12-11 13:56 ` Greg KH
2019-12-11 14:12 ` Thomas Renninger
2019-12-11 14:12 ` Thomas Renninger
2019-12-11 14:26 ` Greg KH
2019-12-11 14:26 ` Greg KH
2019-12-11 14:52 ` Thomas Renninger
2019-12-11 14:52 ` Thomas Renninger
2019-12-11 14:57 ` Greg KH
2019-12-11 14:57 ` Greg KH
2019-12-06 16:24 ` [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64 Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:37 ` Greg KH
2019-12-06 16:37 ` Greg KH
2019-12-09 10:31 ` Will Deacon
2019-12-09 10:31 ` Will Deacon
2019-12-09 11:28 ` Thomas Renninger
2019-12-09 11:28 ` Thomas Renninger
2019-12-09 17:38 ` Will Deacon
2019-12-09 17:38 ` Will Deacon
2019-12-10 13:33 ` Thomas Renninger
2019-12-10 13:33 ` Thomas Renninger
2019-12-10 14:47 ` Greg KH
2019-12-10 14:47 ` Greg KH
2019-12-10 16:24 ` Thomas Renninger [this message]
2019-12-10 16:24 ` Thomas Renninger
2019-12-06 16:58 ` [PATCH v5 0/3] sysfs: add sysfs based cpuinfo Mark Rutland
2019-12-06 16:58 ` Mark Rutland
2019-12-06 17:29 ` Thomas Renninger
2019-12-06 17:29 ` Thomas Renninger
2019-12-06 18:16 ` Mark Rutland
2019-12-06 18:16 ` Mark Rutland
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=2363489.ZvMXcgbkLu@skinner.arch.suse.de \
--to=trenn@suse.de \
--cc=fschnizlein@suse.com \
--cc=fschnizlein@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=will.deacon@arm.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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.