public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Sudeep Holla <Sudeep.Holla@arm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Subject: Re: [PATCH v5 00/11] drivers: cacheinfo support
Date: Mon, 20 Oct 2014 19:46:19 +0100	[thread overview]
Message-ID: <5445587B.8090203@arm.com> (raw)
In-Reply-To: <1412084912-2767-1-git-send-email-sudeep.holla@arm.com>

Hi Greg,

On 30/09/14 14:48, Sudeep Holla wrote:
> This series adds a generic cacheinfo support similar to topology. The
> implementation is based on x86 cacheinfo support. Currently x86, powerpc,
> ia64 and s390 have their own implementations. While adding similar support
> to ARM and ARM64, here is the attempt to make it generic quite similar to
> topology info support. It also adds the missing ABI documentation for
> the cacheinfo sysfs which is already being used.
>
> It moves all the existing different implementations on x86, ia64, powerpc
> and s390 to use the generic cacheinfo infrastructure introduced here.
> These changes on non-ARM platforms are only compile tested and tested on x86.
>
> This series also adds support for ARM and ARM64 architectures based on
> the generic support.
>
> The code can be fetched from:
>   git://linux-arm.org/linux-skn cacheinfo
>

I am hoping to target this for v3.19 if possible, it would be good if
you can review and provide feedback.

Regards,
Sudeep


  parent reply	other threads:[~2014-10-20 18:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 13:48 [PATCH v5 00/11] drivers: cacheinfo support Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 01/11] cpumask: factor out show_cpumap into separate helper function Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 02/11] topology: replace custom attribute macros with standard DEVICE_ATTR* Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 03/11] drivers: base: add cpu_device_create to support per-cpu devices Sudeep Holla
2014-11-07 19:22   ` Greg Kroah-Hartman
2014-09-30 13:48 ` [PATCH v5 04/11] drivers: base: support cpu cache information interface to userspace via sysfs Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 05/11] ia64: move cacheinfo sysfs to generic cacheinfo infrastructure Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 06/11] s390: " Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 07/11] x86: " Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 08/11] powerpc: " Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 09/11] ARM64: kernel: add support for cpu cache information Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 10/11] ARM: " Sudeep Holla
2014-09-30 13:48 ` [PATCH v5 11/11] ARM: kernel: add outer cache support for cacheinfo implementation Sudeep Holla
2014-10-20 18:46 ` Sudeep Holla [this message]
2014-10-20 18:49   ` [PATCH v5 00/11] drivers: cacheinfo support Greg Kroah-Hartman
2014-10-21  9:26     ` Sudeep Holla
2014-11-07 19:23       ` Greg Kroah-Hartman
2014-11-07 19:40         ` Sudeep Holla
2014-11-07 19:45           ` Greg Kroah-Hartman

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=5445587B.8090203@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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