public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Felix Schnizlein <fschnizlein@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@vger.kernel.org,
	yanmin.zhang@intel.com, trenn@suse.com
Subject: Re: [RFC PATCH 1/3] Add sysfs based cpuinfo structure.
Date: Thu, 8 Jun 2017 20:25:31 +0200	[thread overview]
Message-ID: <20170608182531.GE13995@kroah.com> (raw)
In-Reply-To: <1496940975-9164-2-git-send-email-fschnizlein@suse.com>

On Thu, Jun 08, 2017 at 06:56:13PM +0200, Felix Schnizlein wrote:
> Create a new sysfs attribute group called 'cpuinfo' for each
> online cpu. The cleaned up cpuinfo shows up in a sysfs
> subdirectory here: /sys/devices/system/cpu/cpu*/cpuinfo.
> 
> Define preprocessor macros (CPUINFO_DEFINE_* and CPUINFO_ATTR) to make
> defining new sysfs attributes for cpuinfo more easy.
> 
> Signed-off-by: Thomas Renninger <trenn@suse.com>
> ---
>  drivers/base/Kconfig       |  7 ++++++
>  drivers/base/Makefile      |  1 +
>  drivers/base/cpuinfo.c     | 57 ++++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/cpuhotplug.h |  1 +
>  include/linux/cpuinfo.h    | 47 ++++++++++++++++++++++++++++++++++++++
>  5 files changed, 113 insertions(+)
>  create mode 100644 drivers/base/cpuinfo.c
>  create mode 100644 include/linux/cpuinfo.h
> 
> diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
> index d718ae4..7900e31 100644
> --- a/drivers/base/Kconfig
> +++ b/drivers/base/Kconfig
> @@ -224,6 +224,13 @@ config DEBUG_TEST_DRIVER_REMOVE
>  	  unusable. You should say N here unless you are explicitly looking to
>  	  test this functionality.
>  
> +config CPUINFO_SYSFS
> +	bool "Enable sysfs based cpuinfo"
> +	depends on SYSFS && X86
> +	default y
> +	help
> +	  This option enables cpuinfo in sysfs.

Why would you not want this?  Why make it an option at all?

  parent reply	other threads:[~2017-06-08 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1496940975-9164-1-git-send-email-fschnizlein@suse.com>
     [not found] ` <1496940975-9164-4-git-send-email-fschnizlein@suse.com>
2017-06-08 18:25   ` [RFC PATCH 3/3] Add deprecation warning to cpuinfo proc Greg KH
     [not found] ` <1496940975-9164-2-git-send-email-fschnizlein@suse.com>
2017-06-08 18:22   ` [RFC PATCH 1/3] Add sysfs based cpuinfo structure Greg KH
2017-06-08 18:25   ` Greg KH [this message]
     [not found] ` <1496940975-9164-3-git-send-email-fschnizlein@suse.com>
2017-06-08 18:24   ` [RFC PATCH 2/3] Implement sysfs based cpuinfo for x86 cpus Greg KH
2017-06-09 13:28     ` Thomas Renninger
2017-06-09 15:22       ` Brice Goglin
2017-06-08 18:26   ` Greg KH

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