From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com,
irogers@google.com
Subject: Re: [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08
Date: Mon, 28 Sep 2020 08:47:33 -0300 [thread overview]
Message-ID: <20200928114733.GD2883319@kernel.org> (raw)
In-Reply-To: <4db737f2-0705-5183-6971-9031acfd123b@linux.intel.com>
Em Wed, Sep 23, 2020 at 09:25:06AM +0800, Jin, Yao escreveu:
> Hi Arnaldo,
>
> On 9/23/2020 3:42 AM, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Sep 22, 2020 at 11:19:17AM +0800, Jin Yao escreveu:
> > > - Update CascadelakeX events to v1.08.
> > > - Update CascadelakeX JSON metrics from TMAM 4.0.
> > >
> > > Other fixes:
> > > - Add NO_NMI_WATCHDOG metric constraint to Backend_Bound
> > > - Change 'MB/sec' to 'MB' in UNC_M_PMM_BANDWIDTH.
Applied.
- Arnaldo
prev parent reply other threads:[~2020-09-28 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 3:19 [PATCH v2 0/2] perf: Update CascadelakeX and SkylakeX events list Jin Yao
2020-09-22 19:22 ` Andi Kleen
[not found] ` <20200922031918.3723-2-yao.jin@linux.intel.com>
2020-09-22 19:42 ` [PATCH v2 1/2] perf vendor events: Update CascadelakeX events to v1.08 Arnaldo Carvalho de Melo
[not found] ` <4db737f2-0705-5183-6971-9031acfd123b@linux.intel.com>
2020-09-23 21:04 ` Ian Rogers
2020-09-25 18:05 ` Arnaldo Carvalho de Melo
2020-09-25 18:36 ` Andi Kleen
2020-09-25 19:21 ` Arnaldo Carvalho de Melo
2020-09-25 19:43 ` Ian Rogers
2020-09-25 20:23 ` Konstantin Ryabitsev
2020-10-09 3:45 ` Jin, Yao
2020-09-28 11:47 ` 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=20200928114733.GD2883319@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.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