All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: "nakamura.shun@fujitsu.com" <nakamura.shun@fujitsu.com>
Cc: "will@kernel.org" <will@kernel.org>,
	"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
	"leo.yan@linaro.org" <leo.yan@linaro.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] perf vendor events: Add Fujitsu A64FX V1.2 pmu event
Date: Mon, 25 Jan 2021 12:46:02 +0000	[thread overview]
Message-ID: <59c31515-8275-5dfe-0276-ed9353bceb6c@huawei.com> (raw)
In-Reply-To: <OSBPR01MB4600A7B761F965C443D92DCFF7A00@OSBPR01MB4600.jpnprd01.prod.outlook.com>

On 22/01/2021 08:37, nakamura.shun@fujitsu.com wrote:
>> I think that we need to the same here as the IMPDEF recommended events - add a
>> common JSON to reduce the duplication.
>>
>> I had done work on this for current CPUs, but never got it finished. Let me check
>> the status.
> If you let me know the result, I will resend the patch according to the policy.

I just sent this:
https://lore.kernel.org/lkml/1611575600-2440-1-git-send-email-john.garry@huawei.com/T/#u

And now I have noticed that I did not cc arm64 reviewers :(

Anyway, it should be ok to base on that series.

And please add guys under "PERFORMANCE EVENTS SUBSYSTEM" for sending 
patches for perf, and not just the arm64 guys.

Thanks,
John

WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.garry@huawei.com>
To: "nakamura.shun@fujitsu.com" <nakamura.shun@fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"will@kernel.org" <will@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
	"leo.yan@linaro.org" <leo.yan@linaro.org>
Subject: Re: [PATCH v2 3/3] perf vendor events: Add Fujitsu A64FX V1.2 pmu event
Date: Mon, 25 Jan 2021 12:46:02 +0000	[thread overview]
Message-ID: <59c31515-8275-5dfe-0276-ed9353bceb6c@huawei.com> (raw)
In-Reply-To: <OSBPR01MB4600A7B761F965C443D92DCFF7A00@OSBPR01MB4600.jpnprd01.prod.outlook.com>

On 22/01/2021 08:37, nakamura.shun@fujitsu.com wrote:
>> I think that we need to the same here as the IMPDEF recommended events - add a
>> common JSON to reduce the duplication.
>>
>> I had done work on this for current CPUs, but never got it finished. Let me check
>> the status.
> If you let me know the result, I will resend the patch according to the policy.

I just sent this:
https://lore.kernel.org/lkml/1611575600-2440-1-git-send-email-john.garry@huawei.com/T/#u

And now I have noticed that I did not cc arm64 reviewers :(

Anyway, it should be ok to base on that series.

And please add guys under "PERFORMANCE EVENTS SUBSYSTEM" for sending 
patches for perf, and not just the arm64 guys.

Thanks,
John

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-01-26 17:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 10:54 [PATCH v2 0/3] perf vendor events: Support PMU events for A64FX Shunsuke Nakamura
2021-01-21 10:54 ` Shunsuke Nakamura
2021-01-21 10:54 ` [PATCH v2 1/3] perf vendor events: Add cache refill and DCZVA events Shunsuke Nakamura
2021-01-21 10:54   ` Shunsuke Nakamura
2021-01-21 11:39   ` Shaokun Zhang
2021-01-21 11:39     ` Shaokun Zhang
2021-01-21 17:43     ` John Garry
2021-01-21 17:43       ` John Garry
2021-01-22  8:35       ` nakamura.shun
2021-01-22  8:35         ` nakamura.shun
2021-01-21 10:54 ` [PATCH v2 2/3] perf tools: Fix lexical definition of event name Shunsuke Nakamura
2021-01-21 10:54   ` Shunsuke Nakamura
2021-01-21 10:54 ` [PATCH v2 3/3] perf vendor events: Add Fujitsu A64FX V1.2 pmu event Shunsuke Nakamura
2021-01-21 10:54   ` Shunsuke Nakamura
2021-01-21 17:41   ` John Garry
2021-01-21 17:41     ` John Garry
2021-01-22  8:37     ` nakamura.shun
2021-01-22  8:37       ` nakamura.shun
2021-01-25 12:46       ` John Garry [this message]
2021-01-25 12:46         ` John Garry
2021-01-26  8:03         ` nakamura.shun
2021-01-26  8:03           ` nakamura.shun

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=59c31515-8275-5dfe-0276-ed9353bceb6c@huawei.com \
    --to=john.garry@huawei.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=nakamura.shun@fujitsu.com \
    --cc=will@kernel.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.