public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: alexander.antonov@linux.intel.com
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	alexander.shishkin@linux.intel.com, kan.liang@linux.intel.com,
	ak@linux.intel.com, steve.wahl@hpe.com, kyle.meyer@hpe.com,
	alexey.v.bayduraev@linux.intel.com
Subject: Re: [PATCH 0/3] perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on SNR and ICX
Date: Wed, 12 May 2021 14:45:50 +0200	[thread overview]
Message-ID: <YJvN/ucSDFPII3ol@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210426131614.16205-1-alexander.antonov@linux.intel.com>

On Mon, Apr 26, 2021 at 04:16:11PM +0300, alexander.antonov@linux.intel.com wrote:
> Alexander Antonov (3):
>   perf/x86/intel/uncore: Generalize I/O stacks to PMON mapping procedure
>   perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on SNR
>   perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on ICX
> 
>  arch/x86/events/intel/uncore.h       |   1 +
>  arch/x86/events/intel/uncore_snbep.c | 173 ++++++++++++++++++++++++++-
>  2 files changed, 168 insertions(+), 6 deletions(-)

Thanks!

      parent reply	other threads:[~2021-05-12 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 13:16 [PATCH 0/3] perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on SNR and ICX alexander.antonov
2021-04-26 13:16 ` [PATCH 1/3] perf/x86/intel/uncore: Generalize I/O stacks to PMON mapping procedure alexander.antonov
2021-05-19  8:21   ` [tip: perf/core] " tip-bot2 for Alexander Antonov
2021-04-26 13:16 ` [PATCH 2/3] perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on SNR alexander.antonov
2021-05-19  8:21   ` [tip: perf/core] " tip-bot2 for Alexander Antonov
2021-04-26 13:16 ` [PATCH 3/3] perf/x86/intel/uncore: Enable I/O stacks to IIO PMON mapping on ICX alexander.antonov
2021-05-19  8:21   ` [tip: perf/core] " tip-bot2 for Alexander Antonov
2021-05-12 12:45 ` Peter Zijlstra [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=YJvN/ucSDFPII3ol@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.antonov@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexey.v.bayduraev@linux.intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kyle.meyer@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.wahl@hpe.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