From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: tglx@linutronix.de, mingo@redhat.com,
linux-kernel@vger.kernel.org, acme@kernel.org,
eranian@google.com, ak@linux.intel.com
Subject: Re: [RESEND PATCH 0/6] Perf uncore support for Snow Ridge server
Date: Mon, 3 Jun 2019 18:34:20 +0200 [thread overview]
Message-ID: <20190603163420.GD3402@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1556672028-119221-1-git-send-email-kan.liang@linux.intel.com>
On Tue, Apr 30, 2019 at 05:53:42PM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> The patch series intends to enable perf uncore support for Snow Ridge
> server.
>
> Here is the link for the uncore document.
> https://cdrdv2.intel.com/v1/dl/getContent/611319
>
> Patch 1: Fixes a generic issue for uncore free-running counter, which
> also impacts the Snow Ridge server.
>
> Patch 2-6: Perf uncore support for Snow Ridge server.
>
> Kan Liang (6):
> perf/x86/intel/uncore: Handle invalid event coding for free-running
> counter
> perf/x86/intel/uncore: Add uncore support for Snow Ridge server
> perf/x86/intel/uncore: Extract codes of box ref/unref
> perf/x86/intel/uncore: Support MMIO type uncore blocks
> perf/x86/intel/uncore: Clean up client IMC
> perf/x86/intel/uncore: Add IMC uncore support for Snow Ridge
>
> arch/x86/events/intel/uncore.c | 122 +++++--
> arch/x86/events/intel/uncore.h | 41 ++-
> arch/x86/events/intel/uncore_snb.c | 16 +-
> arch/x86/events/intel/uncore_snbep.c | 601 +++++++++++++++++++++++++++++++++++
> 4 files changed, 737 insertions(+), 43 deletions(-)
Kan, we had horrible conflicts between this set and the topology
s/pkg/die/ thing. I've attempted a rebase here:
https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/log/?h=perf/core
can you please double check?
next prev parent reply other threads:[~2019-06-03 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 0:53 [RESEND PATCH 0/6] Perf uncore support for Snow Ridge server kan.liang
2019-05-01 0:53 ` [RESEND PATCH 1/6] perf/x86/intel/uncore: Handle invalid event coding for free-running counter kan.liang
2019-06-17 14:36 ` [tip:perf/core] " tip-bot for Kan Liang
2019-05-01 0:53 ` [RESEND PATCH 2/6] perf/x86/intel/uncore: Add uncore support for Snow Ridge server kan.liang
2019-06-17 14:36 ` [tip:perf/core] " tip-bot for Kan Liang
2019-05-01 0:53 ` [RESEND PATCH 3/6] perf/x86/intel/uncore: Extract codes of box ref/unref kan.liang
2019-05-08 11:51 ` Peter Zijlstra
2019-06-17 14:37 ` [tip:perf/core] perf/x86/intel/uncore: Factor out box ref/unref functions tip-bot for Kan Liang
2019-05-01 0:53 ` [RESEND PATCH 4/6] perf/x86/intel/uncore: Support MMIO type uncore blocks kan.liang
2019-06-17 14:38 ` [tip:perf/core] " tip-bot for Kan Liang
2019-05-01 0:53 ` [RESEND PATCH 5/6] perf/x86/intel/uncore: Clean up client IMC kan.liang
2019-06-17 14:39 ` [tip:perf/core] " tip-bot for Kan Liang
2019-05-01 0:53 ` [RESEND PATCH 6/6] perf/x86/intel/uncore: Add IMC uncore support for Snow Ridge kan.liang
2019-06-17 14:39 ` [tip:perf/core] " tip-bot for Kan Liang
2019-05-08 11:59 ` [RESEND PATCH 0/6] Perf uncore support for Snow Ridge server Peter Zijlstra
2019-06-03 16:34 ` Peter Zijlstra [this message]
2019-06-03 17:19 ` Liang, Kan
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=20190603163420.GD3402@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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