The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Felix Schnizlein <fschnizlein@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	yanmin.zhang@intel.com, mingo@redhat.com, trenn@suse.com
Subject: Re: [PATCH 1/2] Add sysfs based cpuinfo structure
Date: Wed, 2 Aug 2017 09:04:20 -0700	[thread overview]
Message-ID: <20170802160420.GA18507@kroah.com> (raw)
In-Reply-To: <1501686852-13692-2-git-send-email-fschnizlein@suse.com>

On Wed, Aug 02, 2017 at 05:14:11PM +0200, Felix Schnizlein wrote:
> Create a new sysfs attribute group called 'info' for each
> online cpu. The cleaned up cpuinfo shows up in a sysfs
> subdirectory here: /sys/devices/system/cpu/cpu#/info.
> 
> Define preprocessor macros (CPUINFO_DEFINE_* and CPUINFO_ATTR) to make
> defining new sysfs attributes for cpuinfo more easy.
> 
> Add basic documentation for the info sysfs tree.
> 
> Signed-off-by: Felix Schnizlein <fschnizlein@suse.com>
> Signed-off-by: Thomas Renninger <trenn@suse.com>
> ---
>  Documentation/ABI/testing/sysfs-devices-system-cpu | 17 ++++++++
>  arch/Kconfig                                       |  3 ++
>  drivers/base/Makefile                              |  1 +
>  drivers/base/cpuinfo.c                             | 48 ++++++++++++++++++++++
>  include/linux/cpuhotplug.h                         |  1 +
>  include/linux/cpuinfo.h                            | 43 +++++++++++++++++++
>  6 files changed, 113 insertions(+)
>  create mode 100644 drivers/base/cpuinfo.c
>  create mode 100644 include/linux/cpuinfo.h
> 
> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
> index f3d5817..fbaf165 100644
> --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
> +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
> @@ -373,3 +373,20 @@ Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
>  Description:	information about CPUs heterogeneity.
>  
>  		cpu_capacity: capacity of cpu#.
> +
> +What:		/sys/devices/system/cpu/cpu#/info/
> +Date:		June 2017
> +Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
> +Description:	Various information about the online cpu. Which attributes are
> +		available depends on the architecture, kernel configuration and
> +                cpu model.

tabs?

> +
> +What:		/sys/devices/system/cpu/cpu#/info/
> +		/sys/devices/system/cpu/cpu#/info/vendor_id
> +		/sys/devices/system/cpu/cpu#/info/cpu_family
> +		/sys/devices/system/cpu/cpu#/info/model
> +		/sys/devices/system/cpu/cpu#/info/model_name
> +		/sys/devices/system/cpu/cpu#/info/stepping
> +		/sys/devices/system/cpu/cpu#/info/flags
> +		/sys/devices/system/cpu/cpu#/info/bugs
> +		/sys/devices/system/cpu/cpu#/info/bogomips

Can you guarantee that all arches will be able to provide these?

thanks,

greg k-h

       reply	other threads:[~2017-08-02 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1501686852-13692-1-git-send-email-fschnizlein@suse.com>
     [not found] ` <1501686852-13692-2-git-send-email-fschnizlein@suse.com>
2017-08-02 16:04   ` Greg KH [this message]
2017-08-02 16:46     ` [PATCH 1/2] Add sysfs based cpuinfo structure Felix Schnizlein

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=20170802160420.GA18507@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=fschnizlein@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=trenn@suse.com \
    --cc=x86@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