From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Renninger <trenn@suse.de>
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 15:47:37 +0100 [thread overview]
Message-ID: <20191210144737.GB3975980@kroah.com> (raw)
In-Reply-To: <11195456.EmMzWPVPDU@skinner.arch.suse.de>
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?
thanks,
greg k-h
_______________________________________________
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 14:47 UTC|newest]
Thread overview: 25+ 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 ` [PATCH 1/3] cpuinfo: add sysfs based arch independent cpuinfo framework Thomas Renninger
2019-12-06 16:33 ` Greg KH
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:36 ` Greg KH
2019-12-10 20:48 ` Thomas Gleixner
2019-12-10 20:53 ` Greg KH
2019-12-11 10:42 ` Thomas Renninger
2019-12-11 13:56 ` Greg KH
2019-12-11 14:12 ` Thomas Renninger
2019-12-11 14:26 ` Greg KH
2019-12-11 14:52 ` Thomas Renninger
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:37 ` Greg KH
2019-12-09 10:31 ` Will Deacon
2019-12-09 11:28 ` Thomas Renninger
2019-12-09 17:38 ` Will Deacon
2019-12-10 13:33 ` Thomas Renninger
2019-12-10 14:47 ` Greg KH [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 17:29 ` Thomas Renninger
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=20191210144737.GB3975980@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fschnizlein@suse.com \
--cc=fschnizlein@suse.de \
--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=trenn@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).