mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	ak@linux.intel.com, eranian@google.com
Subject: Re: [PATCH 1/3] perf/x86/intel: Add Granite Rapids
Date: Mon, 20 Mar 2023 11:32:30 +0100	[thread overview]
Message-ID: <20230320103230.GG2194297@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230314170041.2967712-1-kan.liang@linux.intel.com>

On Tue, Mar 14, 2023 at 10:00:39AM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
> 
> From core PMU's perspective, Granite Rapids is similar to the Sapphire
> Rapids. The key differences include:
> - Doesn't need the AUX event workaround for the mem load event.
>   (Implement in this patch).
> - Support Retire Latency (Has been implemented in the commit
>   c87a31093c70 ("perf/x86: Support Retire Latency"))
> - The event list, which will be supported in the perf tool later.
> 
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>

Thanks!

  parent reply	other threads:[~2023-03-20 10:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 17:00 kan.liang
2023-03-14 17:00 ` [PATCH 2/3] perf/x86/msr: " kan.liang
2023-03-22  9:14   ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-03-14 17:00 ` [PATCH 3/3] perf/x86/cstate: Add Granite Rapids support kan.liang
2023-03-22  9:14   ` [tip: perf/core] " tip-bot2 for Artem Bityutskiy
2023-03-20 10:32 ` Peter Zijlstra [this message]
2023-03-22  9:14 ` [tip: perf/core] perf/x86/intel: Add Granite Rapids tip-bot2 for Kan Liang

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=20230320103230.GG2194297@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.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 \
    /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
all inboxes | Powered by JetHome®