Re: [PATCH v4 04/11] drivers: base: support cpu cache information interface to userspace via sysfs

[Sudeep Holla]

Hi Stephen,

On 19/09/14 23:24, Stephen Boyd wrote:
> On 09/03/14 10:00, 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 devices are instantiated as needed as
> > CPUs come online. The cache information is replicated per-cpu even if they are
> > shared. A per-cpu array of cache information maintained is used mainly for
> > sysfs-related book keeping.
> >
> > It also implements the shared_cpu_map attribute, which is essential for
> > enabling both kernel and user-space to discover the system's overall cache
> > topology.
> >
> > This patch also add the missing ABI documentation for the cacheinfo sysfs
> > interface already, which is well defined and widely used.
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@xxxxxxx>
> > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > Cc: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
> > Cc: linux-api@xxxxxxxxxxxxxxx
> > Cc: linux390@xxxxxxxxxx
> > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
> > Cc: linux-ia64@xxxxxxxxxxxxxxx
> > Cc: linuxppc-dev@xxxxxxxxxxxxxxxx
> > Cc: linux-s390@xxxxxxxxxxxxxxx
> > Cc: x86@xxxxxxxxxx
>
> Reviewed-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>
> Tested-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx>

Thanks for all the reviews and testings of the series.

Regards,
Sudeep

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