linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
	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: Wed, 21 Nov 2018 09:54:08 -0300	[thread overview]
Message-ID: <20181121125408.GE6248@kernel.org> (raw)
In-Reply-To: <20181121125130.GD6248@kernel.org>

Em Wed, Nov 21, 2018 at 09:51:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Nov 15, 2018 at 04:14:42PM +0100, Jiri Olsa escreveu:
> > On Thu, Nov 15, 2018 at 08:33:27AM -0500, Liang, Kan wrote:
> > > 
> > > 
> > > On 11/15/2018 8:21 AM, Jiri Olsa wrote:
> > > > 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
> > > > 
> > > 
> > > The patch is attached. Can it be applied?
> > 
> > yep, that one works
> 
> Can I have your reviewed-by for this one as well?

I turned the "yep, that one works" into an Acked-by, please let me know
if that is enough.

- Arnaldo

  reply	other threads:[~2018-11-21 12:54 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   ` [PATCH 2/2] perf vendor events: Add JSON metrics for Cascadelake server Jiri Olsa
     [not found]     ` <3ab97c73-c197-8555-1a35-b54636e667e6@linux.intel.com>
2018-11-15 15:14       ` Jiri Olsa
2018-11-21 12:51         ` Arnaldo Carvalho de Melo
2018-11-21 12:54           ` Arnaldo Carvalho de Melo [this message]
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=20181121125408.GE6248@kernel.org \
    --to=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@redhat.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;
as well as URLs for NNTP newsgroup(s).