public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Weilin Wang <weilin.wang@intel.com>, Song Liu <song@kernel.org>
Subject: Re: [PATCH v1] perf vendor events: SKX, CLX, SNR uncore cache event fixes
Date: Mon, 12 Aug 2024 17:11:18 -0300	[thread overview]
Message-ID: <ZrpsZmksSJBrOJz7@x1> (raw)
In-Reply-To: <6947c956-2ba6-4fec-8d8b-79c5bbd3d725@linux.intel.com>

On Mon, Aug 12, 2024 at 10:26:36AM -0400, Liang, Kan wrote:
> 
> 
> On 2024-08-11 12:20 a.m., Ian Rogers wrote:
> > Cache home agent (CHA) events were setting the low rather than high
> > config1 bits. SNR was using CLX CHA events, however its CHA is similar
> > to ICX so remove the events.
> > 
> > Incorporate the updates in:
> > https://github.com/intel/perfmon/pull/215
> > https://github.com/intel/perfmon/pull/216
> > 
> > Co-authored-by: Weilin Wang <weilin.wang@intel.com>
> > Reported-by: Song Liu <song@kernel.org>
> > Closes: https://lore.kernel.org/linux-perf-users/CAPhsuW4nem9XZP+b=sJJ7kqXG-cafz0djZf51HsgjCiwkGBA+A@mail.gmail.com/
> > Fixes: 4cc49942444e ("perf vendor events: Update cascadelakex events/metrics")
> > Signed-off-by: Ian Rogers <irogers@google.com>
> 
> Thanks Ian and Weilin
> 
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>

Thanks, applied to perf-tools-next,

- Arnaldo

      reply	other threads:[~2024-08-12 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11  4:20 [PATCH v1] perf vendor events: SKX, CLX, SNR uncore cache event fixes Ian Rogers
2024-08-12 14:26 ` Liang, Kan
2024-08-12 20:11   ` Arnaldo Carvalho de Melo [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=ZrpsZmksSJBrOJz7@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=song@kernel.org \
    --cc=weilin.wang@intel.com \
    /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