From: Thomas Renninger <trenn@suse.de> To: Will Deacon <will@kernel.org> Cc: Felix Schnizlein <fschnizlein@suse.com>, linux-kernel@vger.kernel.org, gregkh@linuxfoundation.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 14:33:07 +0100 [thread overview] Message-ID: <11195456.EmMzWPVPDU@skinner.arch.suse.de> (raw) In-Reply-To: <20191209173804.GD7489@willie-the-truck> 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. You probably export feature flags in /proc/cpuinfo for a good reason. So where in sysfs should this show up? > Even if we exposed them via sysfs, existing > software will continue to grep them out of /proc/cpuinfo because it's more > reliable and new software would still be encouraged to use either the HWCAPs > directly or, even better, our CPUID (MRS) emulation. Ok, so /proc/cpuinfo Features: is deprecated on arm64. Is that correct? Then it would indeed not make sense to port it/anything to sys. It is this comment you are referring to: arch/arm64/kernel/cpuinfo.c * Dump out the common processor features in a single line. * Userspace should read the hwcaps with getauxval(AT_HWCAP) * rather than attempting to parse this, but there's a body of * software which does already (at least for 32-bit). Then let's shorten this. Sorry for keep digging/asking. Felix made this up rather neat, so that other archs can implement to expose sysfs CPU info easy and consistent. While x86 also ported parts of cpuinfo, e.g. microcode version, most general info is still missing in sysfs. If I find the time, I may check for other archs like ppc64le or s390x to find data which still should show up in sysfs and could then be put in the same directory/file structure. ARM people may still want to make use of this at some point of time, if appropriate. I'll drop patch 3/3. Thanks for explaining me the ARM details, Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Renninger <trenn@suse.de> To: Will Deacon <will@kernel.org> Cc: linux-arch@vger.kernel.org, Felix Schnizlein <fschnizlein@suse.de>, Felix Schnizlein <fschnizlein@suse.com>, gregkh@linuxfoundation.org, x86@kernel.org, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64 Date: Tue, 10 Dec 2019 14:33:07 +0100 [thread overview] Message-ID: <11195456.EmMzWPVPDU@skinner.arch.suse.de> (raw) In-Reply-To: <20191209173804.GD7489@willie-the-truck> 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. You probably export feature flags in /proc/cpuinfo for a good reason. So where in sysfs should this show up? > Even if we exposed them via sysfs, existing > software will continue to grep them out of /proc/cpuinfo because it's more > reliable and new software would still be encouraged to use either the HWCAPs > directly or, even better, our CPUID (MRS) emulation. Ok, so /proc/cpuinfo Features: is deprecated on arm64. Is that correct? Then it would indeed not make sense to port it/anything to sys. It is this comment you are referring to: arch/arm64/kernel/cpuinfo.c * Dump out the common processor features in a single line. * Userspace should read the hwcaps with getauxval(AT_HWCAP) * rather than attempting to parse this, but there's a body of * software which does already (at least for 32-bit). Then let's shorten this. Sorry for keep digging/asking. Felix made this up rather neat, so that other archs can implement to expose sysfs CPU info easy and consistent. While x86 also ported parts of cpuinfo, e.g. microcode version, most general info is still missing in sysfs. If I find the time, I may check for other archs like ppc64le or s390x to find data which still should show up in sysfs and could then be put in the same directory/file structure. ARM people may still want to make use of this at some point of time, if appropriate. I'll drop patch 3/3. Thanks for explaining me the ARM details, 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 13:33 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 [this message] 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 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=11195456.EmMzWPVPDU@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: linkBe 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.