From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@linux.intel.com
Cc: acme@kernel.org, mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, namhyung@kernel.org,
ak@linux.intel.com
Subject: Re: [PATCH 2/2] perf vendor events: Add JSON metrics for Cascadelake server
Date: Thu, 15 Nov 2018 14:21:16 +0100 [thread overview]
Message-ID: <20181115132116.GH9600@krava> (raw)
In-Reply-To: <20181114212416.15665-2-kan.liang@linux.intel.com>
On Wed, Nov 14, 2018 at 01:24:16PM -0800, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> Add JSON metrics (based on event list v1) for Cascadelake server
hum mail server probably crippled the email so it won't apply:
patching file pmu-events/arch/x86/cascadelakex/cache.json
patching file pmu-events/arch/x86/cascadelakex/clx-metrics.json
patching file pmu-events/arch/x86/cascadelakex/floating-point.json
patching file pmu-events/arch/x86/cascadelakex/frontend.json
patching file pmu-events/arch/x86/cascadelakex/memory.json
patching file pmu-events/arch/x86/cascadelakex/other.json
patching file pmu-events/arch/x86/cascadelakex/pipeline.json
patch: **** malformed patch at line 29879: ow status bit and resets the counter to less than MAX. The reset value to the counter is not clocked immediately so the overflow status bit will flip 'high (1)' and generate another PMI (if enabled) after which the reset value gets clocked into the counter. Therefore, software will get the interrupt, read the overflow status bit '1 for bit 34 while the counter value is less than MAX. Software should ignore this case.",
I've similar error before and it was because of the 998 chars size
limit for line.. I guess you could either post it as attachment or
change the transfer encoding
jirka
next prev parent reply other threads:[~2018-11-15 13:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 21:24 [PATCH 1/2] perf vendor events: Add stepping in CPUID string for x86 kan.liang
[not found] ` <20181114212416.15665-2-kan.liang@linux.intel.com>
2018-11-15 13:21 ` Jiri Olsa [this message]
[not found] ` <3ab97c73-c197-8555-1a35-b54636e667e6@linux.intel.com>
2018-11-15 15:14 ` [PATCH 2/2] perf vendor events: Add JSON metrics for Cascadelake server Jiri Olsa
2018-11-21 12:51 ` Arnaldo Carvalho de Melo
2018-11-21 12:54 ` Arnaldo Carvalho de Melo
2018-11-21 13:02 ` Jiri Olsa
2018-11-21 13:10 ` Arnaldo Carvalho de Melo
2018-11-15 13:53 ` [PATCH 1/2] perf vendor events: Add stepping in CPUID string for x86 Jiri Olsa
2018-11-15 14:26 ` Liang, Kan
2018-11-15 15:18 ` Liang, Kan
2018-11-15 15:33 ` Jiri Olsa
2018-11-15 15:25 ` Jiri Olsa
2018-11-15 15:53 ` Liang, Kan
2018-11-15 20:02 ` Jiri Olsa
2018-11-15 20:44 ` Jiri Olsa
2018-11-15 21:01 ` Liang, Kan
2018-11-16 2:14 ` Arnaldo Carvalho de Melo
2018-11-20 13:55 ` Liang, Kan
2018-11-21 12:22 ` Arnaldo Carvalho de Melo
2018-11-22 7:14 ` [tip:perf/core] " tip-bot 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=20181115132116.GH9600@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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