All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: William Cohen <wcohen@redhat.com>, acme@kernel.org
Cc: peterz@infradead.org, mingo@redhat.com, mpetlan@redhat.com,
	linux-kernel@vger.kernel.org, shriyak@linux.vnet.ibm.com,
	alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	namhyung@kernel.org,
	Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v4] Use more flexible pattern matching for CPU identification for mapfile.csv
Date: Tue, 5 Dec 2017 09:25:56 +0530	[thread overview]
Message-ID: <1a494349-2c85-bd09-73c3-fc5ed733d2ef@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171204145728.16792-1-wcohen@redhat.com>


On 12/04/2017 08:27 PM, William Cohen wrote:
> The powerpc cpuid information includes chip revision information.
> Changes between chip revisions are usually minor bug fixes and usually
> do not affect the operation of the performance monitoring hardware.
> The original mapfile.csv matching requires enumerating every possible
> cpuid string.  When a new minor chip revision is produced a new entry
> has to be added to the mapfile.csv and the code recompiled to allow
> perf to have the implementation specific perf events for this new
> minor revision.  For users of various distibutions of Linux having to
> wait for a new release of the kernel's perf tool to be built with
> these trivial patches is inconvenient.
>

Tested-by: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>

Thanks,
Ravi

  reply	other threads:[~2017-12-05  3:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 14:57 [PATCH v4] Use more flexible pattern matching for CPU identification for mapfile.csv William Cohen
2017-12-05  3:55 ` Ravi Bangoria [this message]
2017-12-05 13:45   ` Arnaldo Carvalho de Melo
2017-12-06 16:43 ` [tip:perf/core] perf vendor events: " tip-bot for William Cohen

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=1a494349-2c85-bd09-73c3-fc5ed733d2ef@linux.vnet.ibm.com \
    --to=ravi.bangoria@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shriyak@linux.vnet.ibm.com \
    --cc=wcohen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.