On Fri, Feb 07, 2014 at 04:49:16PM +0000, Sudeep Holla wrote: > From: Sudeep Holla <sudeep.holla@xxxxxxx> > > 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-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
