All of lore.kernel.org
 help / color / mirror / Atom feed
From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] perf utils: add support for arch standard events
Date: Fri, 9 Feb 2018 09:53:45 +0100	[thread overview]
Message-ID: <20180209085345.GA20449@krava> (raw)
In-Reply-To: <312796a3-9818-7793-9e28-7a686c990977@huawei.com>

On Thu, Feb 08, 2018 at 03:25:30PM +0000, John Garry wrote:
> On 08/02/2018 13:55, Jiri Olsa wrote:
> > On Wed, Feb 07, 2018 at 01:45:00AM +0800, John Garry wrote:
> > 
> > SNIP
> > 
> > > 
> > > +static int is_json_file(const char *name)
> > > +{
> > > +	const char *suffix;
> > > +
> > > +	if (strlen(name) < 5)
> > > +		return 0;
> > > +
> > > +	suffix = name + strlen(name) - 5;
> > > +
> > > +	if (strncmp(suffix, ".json", 5) == 0)
> > > +		return 1;
> > > +	return 0;
> > > +}
> > > +
> > > +static int preprocess_arch_std_files(const char *fpath, const struct stat *sb,
> > > +				int typeflag, struct FTW *ftwbuf)
> > > +{
> > > +	int level = ftwbuf->level;
> > > +	int is_file = typeflag == FTW_F;
> > > +
> > > +	if (level == 1 && is_file && is_json_file(fpath))
> > > +		return json_events(fpath, save_arch_std_events, (void *)sb);
> > 
> > so any .json file will pass..
> 
> Yes, so according to the scheme any architecture JSONs should be placed in
> the arch root folder.
> 
> just wondering you'd want to put
> > some name restriction for recomended events file like this -recomended
> > suffix you used later.. but that can be added later in case we'll
> > need some other json files in here ;-)
> 
> Sorry, but I don't see what the naming restriction would mean in practice.

now any file you add there will be treated as 'recomended' events file,
having them with '-recomended.json' suffix would separate them.. but
as I said it's ok for now

jirka

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Olsa <jolsa@redhat.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	alexander.shishkin@linux.intel.com, namhyung@kernel.org,
	ak@linux.intel.com, wcohen@redhat.com, will.deacon@arm.com,
	ganapatrao.kulkarni@cavium.com, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com, zhangshaokun@hisilicon.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/9] perf utils: add support for arch standard events
Date: Fri, 9 Feb 2018 09:53:45 +0100	[thread overview]
Message-ID: <20180209085345.GA20449@krava> (raw)
In-Reply-To: <312796a3-9818-7793-9e28-7a686c990977@huawei.com>

On Thu, Feb 08, 2018 at 03:25:30PM +0000, John Garry wrote:
> On 08/02/2018 13:55, Jiri Olsa wrote:
> > On Wed, Feb 07, 2018 at 01:45:00AM +0800, John Garry wrote:
> > 
> > SNIP
> > 
> > > 
> > > +static int is_json_file(const char *name)
> > > +{
> > > +	const char *suffix;
> > > +
> > > +	if (strlen(name) < 5)
> > > +		return 0;
> > > +
> > > +	suffix = name + strlen(name) - 5;
> > > +
> > > +	if (strncmp(suffix, ".json", 5) == 0)
> > > +		return 1;
> > > +	return 0;
> > > +}
> > > +
> > > +static int preprocess_arch_std_files(const char *fpath, const struct stat *sb,
> > > +				int typeflag, struct FTW *ftwbuf)
> > > +{
> > > +	int level = ftwbuf->level;
> > > +	int is_file = typeflag == FTW_F;
> > > +
> > > +	if (level == 1 && is_file && is_json_file(fpath))
> > > +		return json_events(fpath, save_arch_std_events, (void *)sb);
> > 
> > so any .json file will pass..
> 
> Yes, so according to the scheme any architecture JSONs should be placed in
> the arch root folder.
> 
> just wondering you'd want to put
> > some name restriction for recomended events file like this -recomended
> > suffix you used later.. but that can be added later in case we'll
> > need some other json files in here ;-)
> 
> Sorry, but I don't see what the naming restriction would mean in practice.

now any file you add there will be treated as 'recomended' events file,
having them with '-recomended.json' suffix would separate them.. but
as I said it's ok for now

jirka

  reply	other threads:[~2018-02-09  8:53 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 17:44 [PATCH 0/9] perf events patches for improved ARM64 support John Garry
2018-02-06 17:44 ` John Garry
2018-02-06 17:44 ` [PATCH 1/9] perf vendor events: drop incomplete multiple mapfile support John Garry
2018-02-06 17:44   ` John Garry
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-06 17:44 ` [PATCH 2/9] perf utils: add support for pmu events vendor sub-directory John Garry
2018-02-06 17:44   ` John Garry
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-06 17:44 ` [PATCH 3/9] perf vendor events arm64: Relocate ThunderX2 JSON John Garry
2018-02-06 17:44   ` John Garry
2018-02-06 17:44 ` [PATCH 4/9] perf vendor events arm64: Relocate Cortex A53 JSONs John Garry
2018-02-06 17:44   ` John Garry
2018-02-06 17:45 ` [PATCH 5/9] perf utils: add support for arch standard events John Garry
2018-02-06 17:45   ` John Garry
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 15:57     ` John Garry
2018-02-08 15:57       ` John Garry
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 14:02     ` Alan Cox
2018-02-08 14:02       ` Alan Cox
2018-02-08 15:31       ` John Garry
2018-02-08 15:31         ` John Garry
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 13:54   ` Jiri Olsa
2018-02-08 13:54     ` Jiri Olsa
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-08 14:45     ` John Garry
2018-02-08 14:45       ` John Garry
2018-02-08 14:54       ` Jiri Olsa
2018-02-08 14:54         ` Jiri Olsa
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-08 15:25     ` John Garry
2018-02-08 15:25       ` John Garry
2018-02-09  8:53       ` Jiri Olsa [this message]
2018-02-09  8:53         ` Jiri Olsa
2018-02-08 13:55   ` Jiri Olsa
2018-02-08 13:55     ` Jiri Olsa
2018-02-08 14:59     ` John Garry
2018-02-08 14:59       ` John Garry
2018-02-06 17:45 ` [PATCH 6/9] perf utils: add armv8-recommended.json John Garry
2018-02-06 17:45   ` John Garry
2018-02-06 17:45 ` [PATCH 7/9] perf utils: fixup Cavium ThunderX2 JSON to use ARMv8 recommended events John Garry
2018-02-06 17:45   ` John Garry
2018-02-06 17:45 ` [PATCH 8/9] perf utils: fixup ARM Cortex A53 JSONs " John Garry
2018-02-06 17:45   ` John Garry
2018-02-06 17:45 ` [PATCH 9/9] perf utils: add HiSilicon hip08 JSON file John Garry
2018-02-06 17:45   ` John Garry

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=20180209085345.GA20449@krava \
    --to=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.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 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.