linux-kernel - Re: [PATCH RFC/RFT v2 1/8] drivers: base: support cpu cache information interface to userspace via sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140207192925.GB18771@kroah.com>
Date:	Fri, 7 Feb 2014 11:29:25 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Sudeep Holla <sudeep.holla@....com>
Cc:	linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH RFC/RFT v2 1/8] drivers: base: support cpu cache
 information interface to userspace via sysfs

On Fri, Feb 07, 2014 at 04:49:16PM +0000, Sudeep Holla wrote:
> From: Sudeep Holla <sudeep.holla@....com>
> 
> This patch adds initial support for providing processor cache information
> to userspace through sysfs interface. This is based on already existing
> implementations(x86, ia64, s390 and powerpc) and hence the interface is
> intended to be fully compatible.
> 
> The main purpose of this generic support is to avoid further code
> duplication to support new architectures and also to unify all the existing
> different implementations.
> 
> This implementation maintains the hierarchy of cache objects which reflects
> the system's cache topology. Cache objects are instantiated as needed as
> CPUs come online. The cache objects are replicated per-cpu even if they are
> shared. A per-cpu array of cache information maintained is used mainly for
> sysfs-related book keeping.

I thought I asked that you not use "raw" kobjects for this, instead
using 'struct device' or just an attribute group?

Using a kobject means that userspace tools that use libudev have no
chance to see these attributes at all, which is not good, right?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/