linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yu, Fenghua" <fenghua.yu@intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"Anvin, H Peter" <h.peter.anvin@intel.com>,
	Ingo Molnar <mingo@elte.hu>, "Luck, Tony" <tony.luck@intel.com>,
	Stephane Eranian <eranian@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Vikas Shivappa <vikas.shivappa@linux.intel.com>,
	"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: RE: [PATCH v2 0/3] Cache id
Date: Fri, 8 Jul 2016 03:13:07 +0000	[thread overview]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712205DFD2DD5@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <20160707162102.GD15924@pd.tnic>

> From: Borislav Petkov [mailto:bp@suse.de]
> Sent: Thursday, July 07, 2016 9:21 AM
> On Wed, Jul 06, 2016 at 03:07:15PM -0700, Fenghua Yu wrote:
> > From: Fenghua Yu <fenghua.yu@intel.com>
> >
> > This patch set introduces cache id to identify a cache in platform. It
> > can be useful in such areas as Cach Allocation Technology (CAT) where
> > user needs to specify how much cache is allocated on which cache.
> > Cache id provides a concise way to identify the cache. CAT patches
> > will be released separately.
> >
> > Changes:
> > v2: Split one patch into three patches and add ABI documentation.
> >
> > Fenghua Yu (3):
> >   cacheinfo: Introduce cache id
> >   Documentation, ABI: Add a document entry for cache id
> >   x86, intel_cacheinfo: Enable cache id in x86
> >
> >  Documentation/ABI/testing/sysfs-devices-system-cpu | 13
> +++++++++++++
> >  arch/x86/kernel/cpu/intel_cacheinfo.c              | 20
> ++++++++++++++++++++
> >  drivers/base/cacheinfo.c                           |  5 +++++
> >  include/linux/cacheinfo.h                          |  3 +++
> >  4 files changed, 41 insertions(+)
> 
> All 3:
> 
> Acked-by: Borislav Petkov <bp@suse.de>

That's great!

Is it possible to merge the patches to 4.8? Then I don't need to carry these patches with upcoming CAT enabling patches:)

Thanks.

-Fenghua

      reply	other threads:[~2016-07-08  3:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 22:07 [PATCH v2 0/3] Cache id Fenghua Yu
2016-07-06 22:07 ` [PATCH v2 1/3] cacheinfo: Introduce cache id Fenghua Yu
2016-07-06 22:07 ` [PATCH v2 2/3] Documentation, ABI: Add a document entry for " Fenghua Yu
2016-07-08  8:41   ` Ingo Molnar
2016-07-08 17:06     ` Yu, Fenghua
2016-07-08 17:29       ` Luck, Tony
2016-07-08 18:07         ` Ingo Molnar
2016-07-08 18:41           ` Borislav Petkov
2016-07-08 18:47             ` Luck, Tony
2016-07-08 18:55               ` Borislav Petkov
2016-07-08 19:34                 ` Ingo Molnar
2016-07-09  8:17                   ` Borislav Petkov
2016-07-08 18:06       ` Ingo Molnar
2016-07-06 22:07 ` [PATCH v2 3/3] x86, intel_cacheinfo: Enable cache id in x86 Fenghua Yu
2016-07-07 16:21 ` [PATCH v2 0/3] Cache id Borislav Petkov
2016-07-08  3:13   ` Yu, Fenghua [this message]

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=3E5A0FA7E9CA944F9D5414FEC6C712205DFD2DD5@ORSMSX106.amr.corp.intel.com \
    --to=fenghua.yu@intel.com \
    --cc=bp@suse.de \
    --cc=eranian@google.com \
    --cc=h.peter.anvin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=vikas.shivappa@linux.intel.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).