[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191210144737.GB3975980@kroah.com>
Date: Tue, 10 Dec 2019 15:47:37 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Thomas Renninger <trenn@...e.de>
Cc: Will Deacon <will@...nel.org>,
Felix Schnizlein <fschnizlein@...e.com>,
linux-kernel@...r.kernel.org,
Felix Schnizlein <fschnizlein@...e.de>,
linux-arch@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux@...linux.org.uk, will.deacon@....com, x86@...nel.org
Subject: Re: [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64
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@...e.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?
thanks,
greg k-h
Powered by blists - more mailing lists