Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 21/03/2018 02:37, William Cohen wrote: On 03/15/2018 12:47 PM, John Garry wrote: On 15/03/2018 15:53, William Cohen wrote: On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: On Thu, Mar 8, 2018 at 12:01 AM, William Cohenwrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. Then there are vendors who do not always properly implemenent MIDR or IIDRs (people who live in glass houses...). Btw, topic originally discussed here: https://lkml.org/lkml/2017/5/2/113 Thanks, John -Will Hi John, Attached is a patch that leaves the MIDR value unmodified and uses regular expressions in the mapfile.csv instead to ignore those bits. I have verified that the changes work on ARM Cortex a53 processor. Does it look reasonable? Hi Will, This looks ok. Personally I find the regular expression in the cpuid slightly difficult to read. I mean, for example, for the revision digit we are using a 12-char regular expression in place, which warps the cpuid string length. BTW, can you also update the pmu events README to mention that posix regular expressions in the CPUID are acceptable? Thanks, John -Will Cohen ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 21/03/2018 02:37, William Cohen wrote: On 03/15/2018 12:47 PM, John Garry wrote: On 15/03/2018 15:53, William Cohen wrote: On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. Then there are vendors who do not always properly implemenent MIDR or IIDRs (people who live in glass houses...). Btw, topic originally discussed here: https://lkml.org/lkml/2017/5/2/113 Thanks, John -Will Hi John, Attached is a patch that leaves the MIDR value unmodified and uses regular expressions in the mapfile.csv instead to ignore those bits. I have verified that the changes work on ARM Cortex a53 processor. Does it look reasonable? Hi Will, This looks ok. Personally I find the regular expression in the cpuid slightly difficult to read. I mean, for example, for the revision digit we are using a 12-char regular expression in place, which warps the cpuid string length. BTW, can you also update the pmu events README to mention that posix regular expressions in the CPUID are acceptable? Thanks, John -Will Cohen ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/15/2018 12:47 PM, John Garry wrote: > On 15/03/2018 15:53, William Cohen wrote: >> On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: >>> On Thu, Mar 8, 2018 at 12:01 AM, William Cohenwrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen, > > On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo > wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni >> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? >> >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should >>> be replaced with [[:xdigit:]] to allow for possible future revisions of >>> chip: > > for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. >>> >>> It is same for arm64 too, there is no need to add an entry for every >>> revision change, need to add when part number changes. >>> This patch is not intended to add entry for revision change, the fact >>> of the matter is that, there is complete MIDR change (vulcan to >>> thunderx2) in B0. >>> as per current arm64 >>> implementation(.tools/perf/arch/arm64/util/header.c), it is not >>> required to have any dontcare marking in mapfile for revision/variant >>> bits. >>> >>> thanks >>> Ganapat >> >> Hi Ganapat, >> >> Would it make more sense to pass the MIDR value unmodified and then use >> regular expressions in mapfile.csv to match the values? If an event on a >> particular processor revision is broken or unusable it can be excluded from >> the list of events with a corrected list of events. There certainly have >> been errata listing events that do not work on specific revisions of armv8 >> processor implementations. >> > > Then there are vendors who do not always properly implemenent MIDR or IIDRs > (people who live in glass houses...). > > Btw, topic originally discussed here: > https://lkml.org/lkml/2017/5/2/113 > > Thanks, > John > >> -Will Hi John, Attached is a patch that leaves the MIDR value unmodified and uses regular expressions in the mapfile.csv instead to ignore those bits. I have verified that the changes work on ARM Cortex a53 processor. Does it look reasonable? -Will Cohen >From b407d0bb7077b23675185a3e9a78f24e775f4e50 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Tue, 20 Mar 2018 22:20:24 -0400 Subject: [PATCH] perf vendor events arm64: Use regular expressions for matching MIDR The arm64 MIDR includes bits that identifying the silicon revision and patch version of the processor. Previously the identification code would mask out those bits making it impossible to have the map file address any errata related to particular pmu events being unavailable for a specific patch level of the silicon. Using the available regular expression matching allows handling of these special cases. Signed-off-by: William Cohen --- tools/perf/arch/arm64/util/header.c | 7 --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 9 - 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/perf/arch/arm64/util/header.c b/tools/perf/arch/arm64/util/header.c index 534cd2507d83..05d1439c2cff 100644 --- a/tools/perf/arch/arm64/util/header.c +++ b/tools/perf/arch/arm64/util/header.c @@ -5,9 +5,6 @@ #define MIDR "/regs/identification/midr_el1" #define MIDR_SIZE 19 -#define MIDR_REVISION_MASK 0xf -#define MIDR_VARIANT_SHIFT 20 -#define MIDR_VARIANT_MASK (0xf << MIDR_VARIANT_SHIFT) char *get_cpuid_str(struct perf_pmu *pmu) {
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/15/2018 12:47 PM, John Garry wrote: > On 15/03/2018 15:53, William Cohen wrote: >> On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: >>> On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen, > > On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo > wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni >> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? >> >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should >>> be replaced with [[:xdigit:]] to allow for possible future revisions of >>> chip: > > for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. >>> >>> It is same for arm64 too, there is no need to add an entry for every >>> revision change, need to add when part number changes. >>> This patch is not intended to add entry for revision change, the fact >>> of the matter is that, there is complete MIDR change (vulcan to >>> thunderx2) in B0. >>> as per current arm64 >>> implementation(.tools/perf/arch/arm64/util/header.c), it is not >>> required to have any dontcare marking in mapfile for revision/variant >>> bits. >>> >>> thanks >>> Ganapat >> >> Hi Ganapat, >> >> Would it make more sense to pass the MIDR value unmodified and then use >> regular expressions in mapfile.csv to match the values? If an event on a >> particular processor revision is broken or unusable it can be excluded from >> the list of events with a corrected list of events. There certainly have >> been errata listing events that do not work on specific revisions of armv8 >> processor implementations. >> > > Then there are vendors who do not always properly implemenent MIDR or IIDRs > (people who live in glass houses...). > > Btw, topic originally discussed here: > https://lkml.org/lkml/2017/5/2/113 > > Thanks, > John > >> -Will Hi John, Attached is a patch that leaves the MIDR value unmodified and uses regular expressions in the mapfile.csv instead to ignore those bits. I have verified that the changes work on ARM Cortex a53 processor. Does it look reasonable? -Will Cohen >From b407d0bb7077b23675185a3e9a78f24e775f4e50 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Tue, 20 Mar 2018 22:20:24 -0400 Subject: [PATCH] perf vendor events arm64: Use regular expressions for matching MIDR The arm64 MIDR includes bits that identifying the silicon revision and patch version of the processor. Previously the identification code would mask out those bits making it impossible to have the map file address any errata related to particular pmu events being unavailable for a specific patch level of the silicon. Using the available regular expression matching allows handling of these special cases. Signed-off-by: William Cohen --- tools/perf/arch/arm64/util/header.c | 7 --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 9 - 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/perf/arch/arm64/util/header.c b/tools/perf/arch/arm64/util/header.c index 534cd2507d83..05d1439c2cff 100644 --- a/tools/perf/arch/arm64/util/header.c +++ b/tools/perf/arch/arm64/util/header.c @@ -5,9 +5,6 @@ #define MIDR "/regs/identification/midr_el1" #define MIDR_SIZE 19 -#define MIDR_REVISION_MASK 0xf -#define MIDR_VARIANT_SHIFT 20 -#define MIDR_VARIANT_MASK (0xf << MIDR_VARIANT_SHIFT) char *get_cpuid_str(struct perf_pmu *pmu) { @@ -44,11 +41,7 @@ char *get_cpuid_str(struct perf_pmu *pmu) } fclose(file); - /* Ignore/clear
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 15/03/2018 15:53, William Cohen wrote: On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: On Thu, Mar 8, 2018 at 12:01 AM, William Cohenwrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. Then there are vendors who do not always properly implemenent MIDR or IIDRs (people who live in glass houses...). Btw, topic originally discussed here: https://lkml.org/lkml/2017/5/2/113 Thanks, John -Will .
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 15/03/2018 15:53, William Cohen wrote: On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. Then there are vendors who do not always properly implemenent MIDR or IIDRs (people who live in glass houses...). Btw, topic originally discussed here: https://lkml.org/lkml/2017/5/2/113 Thanks, John -Will .
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: > On Thu, Mar 8, 2018 at 12:01 AM, William Cohenwrote: >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >>> Hi Will Cohen, >>> >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >>> wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> to enable JSON events for B0. >> >> Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo >> --- >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> index e61c9ca..93c5d14 100644 >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> @@ -13,4 +13,5 @@ >> # >> #Family-model,Version,Filename,EventType >> 0x420f5160,v1,cavium,core >> +0x430f0af0,v1,cavium,core >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should > be replaced with [[:xdigit:]] to allow for possible future revisions of > chip: >>> >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >>> are ignored/dont-care. >> >> Thanks for pointing that out. See the code masking out those bits in >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the >> equivalent of the MIDR including the revision bits. Thus, the need for >> regular expression matching to avoid having to create a new entry for each >> revision. > > It is same for arm64 too, there is no need to add an entry for every > revision change, need to add when part number changes. > This patch is not intended to add entry for revision change, the fact > of the matter is that, there is complete MIDR change (vulcan to > thunderx2) in B0. > as per current arm64 > implementation(.tools/perf/arch/arm64/util/header.c), it is not > required to have any dontcare marking in mapfile for revision/variant > bits. > > thanks > Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. -Will
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 11:14 PM, Ganapatrao Kulkarni wrote: > On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >>> Hi Will Cohen, >>> >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >>> wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> to enable JSON events for B0. >> >> Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo >> --- >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> index e61c9ca..93c5d14 100644 >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> @@ -13,4 +13,5 @@ >> # >> #Family-model,Version,Filename,EventType >> 0x420f5160,v1,cavium,core >> +0x430f0af0,v1,cavium,core >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should > be replaced with [[:xdigit:]] to allow for possible future revisions of > chip: >>> >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >>> are ignored/dont-care. >> >> Thanks for pointing that out. See the code masking out those bits in >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the >> equivalent of the MIDR including the revision bits. Thus, the need for >> regular expression matching to avoid having to create a new entry for each >> revision. > > It is same for arm64 too, there is no need to add an entry for every > revision change, need to add when part number changes. > This patch is not intended to add entry for revision change, the fact > of the matter is that, there is complete MIDR change (vulcan to > thunderx2) in B0. > as per current arm64 > implementation(.tools/perf/arch/arm64/util/header.c), it is not > required to have any dontcare marking in mapfile for revision/variant > bits. > > thanks > Ganapat Hi Ganapat, Would it make more sense to pass the MIDR value unmodified and then use regular expressions in mapfile.csv to match the values? If an event on a particular processor revision is broken or unusable it can be excluded from the list of events with a corrected list of events. There certainly have been errata listing events that do not work on specific revisions of armv8 processor implementations. -Will
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Fri, Mar 9, 2018 at 11:32 PM, Arnaldo Carvalho de Melowrote: > Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: >> > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo >> > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > > @@ -13,5 +13,5 @@ >> > > # >> > > #Family-model,Version,Filename,EventType >> > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core >> > > -0x420f5160,v1,cavium/thunderx2,core >> > > +0x430f0af0,v1,cavium/thunderx2,core >> > > 0x480fd010,v1,hisilicon/hip08,core > >> > please do not delete existing entry, add additional entry. >> > > +0x430f0af0,v1,cavium/thunderx2,core > >> Ok, my bad, I think my eyes are failing me, I swear I saw them in the >> original patch, which is not the case... > >> Ok, will add, together with Will's Acked-by > > So this is how it ended up: > > > commit 9245299469de2e02d9c3cb167c0e52f75f1cc180 > Author: Ganapatrao Kulkarni > Date: Wed Mar 7 16:38:03 2018 +0530 > > perf vendor events arm64: Enable JSON events for ThunderX2 B0 > > There is MIDR change on ThunderX2 B0, adding an entry to mapfile to > enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni > Acked-by: Will Deacon > Cc: Alexander Shishkin > Cc: Ganapatrao Kulkarni > Cc: Jayachandran C > Cc: Jiri Olsa > Cc: John Garry > Cc: Mark Rutland > Cc: Peter Zijlstra > Cc: Robert Richter > Cc: William Cohen > Cc: linux-arm-ker...@lists.infradead.org > Link: > http://lkml.kernel.org/r/20180307110803.32418-1-ganapatrao.kulka...@cavium.com > [ Fixup wrt recent patchset by John Garry ] > Signed-off-by: Arnaldo Carvalho de Melo > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index 8f11aeb003a9..f03e26ecb658 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -14,4 +14,5 @@ > #Family-model,Version,Filename,EventType > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > 0x420f5160,v1,cavium/thunderx2,core > +0x430f0af0,v1,cavium/thunderx2,core > 0x480fd010,v1,hisilicon/hip08,core thanks for help Arnaldo! thanks ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Fri, Mar 9, 2018 at 11:32 PM, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: >> > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo >> > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > > @@ -13,5 +13,5 @@ >> > > # >> > > #Family-model,Version,Filename,EventType >> > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core >> > > -0x420f5160,v1,cavium/thunderx2,core >> > > +0x430f0af0,v1,cavium/thunderx2,core >> > > 0x480fd010,v1,hisilicon/hip08,core > >> > please do not delete existing entry, add additional entry. >> > > +0x430f0af0,v1,cavium/thunderx2,core > >> Ok, my bad, I think my eyes are failing me, I swear I saw them in the >> original patch, which is not the case... > >> Ok, will add, together with Will's Acked-by > > So this is how it ended up: > > > commit 9245299469de2e02d9c3cb167c0e52f75f1cc180 > Author: Ganapatrao Kulkarni > Date: Wed Mar 7 16:38:03 2018 +0530 > > perf vendor events arm64: Enable JSON events for ThunderX2 B0 > > There is MIDR change on ThunderX2 B0, adding an entry to mapfile to > enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni > Acked-by: Will Deacon > Cc: Alexander Shishkin > Cc: Ganapatrao Kulkarni > Cc: Jayachandran C > Cc: Jiri Olsa > Cc: John Garry > Cc: Mark Rutland > Cc: Peter Zijlstra > Cc: Robert Richter > Cc: William Cohen > Cc: linux-arm-ker...@lists.infradead.org > Link: > http://lkml.kernel.org/r/20180307110803.32418-1-ganapatrao.kulka...@cavium.com > [ Fixup wrt recent patchset by John Garry ] > Signed-off-by: Arnaldo Carvalho de Melo > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index 8f11aeb003a9..f03e26ecb658 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -14,4 +14,5 @@ > #Family-model,Version,Filename,EventType > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > 0x420f5160,v1,cavium/thunderx2,core > +0x430f0af0,v1,cavium/thunderx2,core > 0x480fd010,v1,hisilicon/hip08,core thanks for help Arnaldo! thanks ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: > > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo > > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > > @@ -13,5 +13,5 @@ > > > # > > > #Family-model,Version,Filename,EventType > > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > > > -0x420f5160,v1,cavium/thunderx2,core > > > +0x430f0af0,v1,cavium/thunderx2,core > > > 0x480fd010,v1,hisilicon/hip08,core > > please do not delete existing entry, add additional entry. > > > +0x430f0af0,v1,cavium/thunderx2,core > Ok, my bad, I think my eyes are failing me, I swear I saw them in the > original patch, which is not the case... > Ok, will add, together with Will's Acked-by So this is how it ended up: commit 9245299469de2e02d9c3cb167c0e52f75f1cc180 Author: Ganapatrao KulkarniDate: Wed Mar 7 16:38:03 2018 +0530 perf vendor events arm64: Enable JSON events for ThunderX2 B0 There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Acked-by: Will Deacon Cc: Alexander Shishkin Cc: Ganapatrao Kulkarni Cc: Jayachandran C Cc: Jiri Olsa Cc: John Garry Cc: Mark Rutland Cc: Peter Zijlstra Cc: Robert Richter Cc: William Cohen Cc: linux-arm-ker...@lists.infradead.org Link: http://lkml.kernel.org/r/20180307110803.32418-1-ganapatrao.kulka...@cavium.com [ Fixup wrt recent patchset by John Garry ] Signed-off-by: Arnaldo Carvalho de Melo diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index 8f11aeb003a9..f03e26ecb658 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -14,4 +14,5 @@ #Family-model,Version,Filename,EventType 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core 0x420f5160,v1,cavium/thunderx2,core +0x430f0af0,v1,cavium/thunderx2,core 0x480fd010,v1,hisilicon/hip08,core
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:00:40PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: > > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo > > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > > @@ -13,5 +13,5 @@ > > > # > > > #Family-model,Version,Filename,EventType > > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > > > -0x420f5160,v1,cavium/thunderx2,core > > > +0x430f0af0,v1,cavium/thunderx2,core > > > 0x480fd010,v1,hisilicon/hip08,core > > please do not delete existing entry, add additional entry. > > > +0x430f0af0,v1,cavium/thunderx2,core > Ok, my bad, I think my eyes are failing me, I swear I saw them in the > original patch, which is not the case... > Ok, will add, together with Will's Acked-by So this is how it ended up: commit 9245299469de2e02d9c3cb167c0e52f75f1cc180 Author: Ganapatrao Kulkarni Date: Wed Mar 7 16:38:03 2018 +0530 perf vendor events arm64: Enable JSON events for ThunderX2 B0 There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Acked-by: Will Deacon Cc: Alexander Shishkin Cc: Ganapatrao Kulkarni Cc: Jayachandran C Cc: Jiri Olsa Cc: John Garry Cc: Mark Rutland Cc: Peter Zijlstra Cc: Robert Richter Cc: William Cohen Cc: linux-arm-ker...@lists.infradead.org Link: http://lkml.kernel.org/r/20180307110803.32418-1-ganapatrao.kulka...@cavium.com [ Fixup wrt recent patchset by John Garry ] Signed-off-by: Arnaldo Carvalho de Melo diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index 8f11aeb003a9..f03e26ecb658 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -14,4 +14,5 @@ #Family-model,Version,Filename,EventType 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core 0x420f5160,v1,cavium/thunderx2,core +0x430f0af0,v1,cavium/thunderx2,core 0x480fd010,v1,hisilicon/hip08,core
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: > Hi Arnaldo, > > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo >wrote: > > Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > >> On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > >> > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > >> > > Hi Arnaldo, > >> > > > >> > > can you please pull-in this patch? > >> > > >> > So everybody is Ok with this? Can I have some Acked-by: from subject > >> > matter experts? > >> > >> The original patch looks fine to me: > >> > >> Acked-by: Will Deacon > > > > Ok, so, as John mentioned in another message in his thread, this > > conflicts with a series he sent and that Ganapatrao acked and I already > > applied, I looked at it and think this patch should turn into the patch > > at the end of this message, which I'm applying with the commit log > > message in the original patch in this thread, Ack? > > > > > - Arnaldo > > > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > index 8f11aeb003a9..624e8cae6e86 100644 > > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > @@ -13,5 +13,5 @@ > > # > > #Family-model,Version,Filename,EventType > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > > -0x420f5160,v1,cavium/thunderx2,core > > +0x430f0af0,v1,cavium/thunderx2,core > > 0x480fd010,v1,hisilicon/hip08,core > > please do not delete existing entry, add additional entry. > > +0x430f0af0,v1,cavium/thunderx2,core Ok, my bad, I think my eyes are failing me, I swear I saw them in the original patch, which is not the case... Ok, will add, together with Will's Acked-by Thanks, - Arnaldo
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu: > Hi Arnaldo, > > On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo > wrote: > > Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > >> On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > >> > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > >> > > Hi Arnaldo, > >> > > > >> > > can you please pull-in this patch? > >> > > >> > So everybody is Ok with this? Can I have some Acked-by: from subject > >> > matter experts? > >> > >> The original patch looks fine to me: > >> > >> Acked-by: Will Deacon > > > > Ok, so, as John mentioned in another message in his thread, this > > conflicts with a series he sent and that Ganapatrao acked and I already > > applied, I looked at it and think this patch should turn into the patch > > at the end of this message, which I'm applying with the commit log > > message in the original patch in this thread, Ack? > > > > > - Arnaldo > > > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > index 8f11aeb003a9..624e8cae6e86 100644 > > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > @@ -13,5 +13,5 @@ > > # > > #Family-model,Version,Filename,EventType > > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > > -0x420f5160,v1,cavium/thunderx2,core > > +0x430f0af0,v1,cavium/thunderx2,core > > 0x480fd010,v1,hisilicon/hip08,core > > please do not delete existing entry, add additional entry. > > +0x430f0af0,v1,cavium/thunderx2,core Ok, my bad, I think my eyes are failing me, I swear I saw them in the original patch, which is not the case... Ok, will add, together with Will's Acked-by Thanks, - Arnaldo
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Arnaldo, On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melowrote: > Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: >> On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: >> > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: >> > > Hi Arnaldo, >> > > >> > > can you please pull-in this patch? >> > >> > So everybody is Ok with this? Can I have some Acked-by: from subject >> > matter experts? >> >> The original patch looks fine to me: >> >> Acked-by: Will Deacon > > Ok, so, as John mentioned in another message in his thread, this > conflicts with a series he sent and that Ganapatrao acked and I already > applied, I looked at it and think this patch should turn into the patch > at the end of this message, which I'm applying with the commit log > message in the original patch in this thread, Ack? > > - Arnaldo > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index 8f11aeb003a9..624e8cae6e86 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,5 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > -0x420f5160,v1,cavium/thunderx2,core > +0x430f0af0,v1,cavium/thunderx2,core > 0x480fd010,v1,hisilicon/hip08,core please do not delete existing entry, add additional entry. > +0x430f0af0,v1,cavium/thunderx2,core thanks Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Arnaldo, On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: >> On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: >> > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: >> > > Hi Arnaldo, >> > > >> > > can you please pull-in this patch? >> > >> > So everybody is Ok with this? Can I have some Acked-by: from subject >> > matter experts? >> >> The original patch looks fine to me: >> >> Acked-by: Will Deacon > > Ok, so, as John mentioned in another message in his thread, this > conflicts with a series he sent and that Ganapatrao acked and I already > applied, I looked at it and think this patch should turn into the patch > at the end of this message, which I'm applying with the commit log > message in the original patch in this thread, Ack? > > - Arnaldo > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index 8f11aeb003a9..624e8cae6e86 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,5 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core > -0x420f5160,v1,cavium/thunderx2,core > +0x430f0af0,v1,cavium/thunderx2,core > 0x480fd010,v1,hisilicon/hip08,core please do not delete existing entry, add additional entry. > +0x430f0af0,v1,cavium/thunderx2,core thanks Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > > Hi Arnaldo, > > > > > > can you please pull-in this patch? > > > > So everybody is Ok with this? Can I have some Acked-by: from subject > > matter experts? > > The original patch looks fine to me: > > Acked-by: Will DeaconOk, so, as John mentioned in another message in his thread, this conflicts with a series he sent and that Ganapatrao acked and I already applied, I looked at it and think this patch should turn into the patch at the end of this message, which I'm applying with the commit log message in the original patch in this thread, Ack? - Arnaldo diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index 8f11aeb003a9..624e8cae6e86 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,5 +13,5 @@ # #Family-model,Version,Filename,EventType 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core -0x420f5160,v1,cavium/thunderx2,core +0x430f0af0,v1,cavium/thunderx2,core 0x480fd010,v1,hisilicon/hip08,core
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > > Hi Arnaldo, > > > > > > can you please pull-in this patch? > > > > So everybody is Ok with this? Can I have some Acked-by: from subject > > matter experts? > > The original patch looks fine to me: > > Acked-by: Will Deacon Ok, so, as John mentioned in another message in his thread, this conflicts with a series he sent and that Ganapatrao acked and I already applied, I looked at it and think this patch should turn into the patch at the end of this message, which I'm applying with the commit log message in the original patch in this thread, Ack? - Arnaldo diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index 8f11aeb003a9..624e8cae6e86 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,5 +13,5 @@ # #Family-model,Version,Filename,EventType 0x410fd03[[:xdigit:]],v1,arm/cortex-a53,core -0x420f5160,v1,cavium/thunderx2,core +0x430f0af0,v1,cavium/thunderx2,core 0x480fd010,v1,hisilicon/hip08,core
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > > Hi Arnaldo, > > > > > > can you please pull-in this patch? > > > > So everybody is Ok with this? Can I have some Acked-by: from subject > > matter experts? > > The original patch looks fine to me: > > Acked-by: Will DeaconThanks, applying. - Arnaldo
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 03:58:09PM +, Will Deacon escreveu: > On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > > Hi Arnaldo, > > > > > > can you please pull-in this patch? > > > > So everybody is Ok with this? Can I have some Acked-by: from subject > > matter experts? > > The original patch looks fine to me: > > Acked-by: Will Deacon Thanks, applying. - Arnaldo
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > Hi Arnaldo, > > > > can you please pull-in this patch? > > So everybody is Ok with this? Can I have some Acked-by: from subject > matter experts? The original patch looks fine to me: Acked-by: Will DeaconWill
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > > Hi Arnaldo, > > > > can you please pull-in this patch? > > So everybody is Ok with this? Can I have some Acked-by: from subject > matter experts? The original patch looks fine to me: Acked-by: Will Deacon Will
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > Hi Arnaldo, > > can you please pull-in this patch? So everybody is Ok with this? Can I have some Acked-by: from subject matter experts? - Arnaldo > On Thu, Mar 8, 2018 at 9:44 AM, Ganapatrao Kulkarni> wrote: > > On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: > >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > >>> Hi Will Cohen, > >>> > >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo > >>> wrote: > Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile > >> to enable JSON events for B0. > >> > >> Signed-off-by: Ganapatrao Kulkarni > > Ganapatrao, can you please take this in consideration and if agreeing > send a v2 patch? > > With that I can add an Acked-by: wcohen, Right? > > - Arnaldo > >> --- > >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> index e61c9ca..93c5d14 100644 > >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> @@ -13,4 +13,5 @@ > >> # > >> #Family-model,Version,Filename,EventType > >> 0x420f5160,v1,cavium,core > >> +0x430f0af0,v1,cavium,core > >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core > >> > > > > Hi, > > Like the cortex-a53 the last digit '0' of the match for the MIDR should > > be replaced with [[:xdigit:]] to allow for possible future revisions of > > chip: > >>> > >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > >>> are ignored/dont-care. > >> > >> Thanks for pointing that out. See the code masking out those bits in > >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the > >> equivalent of the MIDR including the revision bits. Thus, the need for > >> regular expression matching to avoid having to create a new entry for each > >> revision. > > > > It is same for arm64 too, there is no need to add an entry for every > > revision change, need to add when part number changes. > > This patch is not intended to add entry for revision change, the fact > > of the matter is that, there is complete MIDR change (vulcan to > > thunderx2) in B0. > > as per current arm64 > > implementation(.tools/perf/arch/arm64/util/header.c), it is not > > required to have any dontcare marking in mapfile for revision/variant > > bits. > > > > thanks > > Ganapat > > > >> > >> -Will > >> > >>> > > > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > > > > -Will Cohen > > >>> > >>> thanks > >>> Ganapat > ___ > linux-arm-kernel mailing list > linux-arm-ker...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > >> > > thanks > Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu: > Hi Arnaldo, > > can you please pull-in this patch? So everybody is Ok with this? Can I have some Acked-by: from subject matter experts? - Arnaldo > On Thu, Mar 8, 2018 at 9:44 AM, Ganapatrao Kulkarni > wrote: > > On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: > >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > >>> Hi Will Cohen, > >>> > >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo > >>> wrote: > Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile > >> to enable JSON events for B0. > >> > >> Signed-off-by: Ganapatrao Kulkarni > > Ganapatrao, can you please take this in consideration and if agreeing > send a v2 patch? > > With that I can add an Acked-by: wcohen, Right? > > - Arnaldo > >> --- > >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > >> 1 file changed, 1 insertion(+) > >> > >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> index e61c9ca..93c5d14 100644 > >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > >> @@ -13,4 +13,5 @@ > >> # > >> #Family-model,Version,Filename,EventType > >> 0x420f5160,v1,cavium,core > >> +0x430f0af0,v1,cavium,core > >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core > >> > > > > Hi, > > Like the cortex-a53 the last digit '0' of the match for the MIDR should > > be replaced with [[:xdigit:]] to allow for possible future revisions of > > chip: > >>> > >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > >>> are ignored/dont-care. > >> > >> Thanks for pointing that out. See the code masking out those bits in > >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the > >> equivalent of the MIDR including the revision bits. Thus, the need for > >> regular expression matching to avoid having to create a new entry for each > >> revision. > > > > It is same for arm64 too, there is no need to add an entry for every > > revision change, need to add when part number changes. > > This patch is not intended to add entry for revision change, the fact > > of the matter is that, there is complete MIDR change (vulcan to > > thunderx2) in B0. > > as per current arm64 > > implementation(.tools/perf/arch/arm64/util/header.c), it is not > > required to have any dontcare marking in mapfile for revision/variant > > bits. > > > > thanks > > Ganapat > > > >> > >> -Will > >> > >>> > > > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > > > > -Will Cohen > > >>> > >>> thanks > >>> Ganapat > ___ > linux-arm-kernel mailing list > linux-arm-ker...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > >> > > thanks > Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Arnaldo, can you please pull-in this patch? On Thu, Mar 8, 2018 at 9:44 AM, Ganapatrao Kulkarniwrote: > On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >>> Hi Will Cohen, >>> >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >>> wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> to enable JSON events for B0. >> >> Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo >> --- >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> index e61c9ca..93c5d14 100644 >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> @@ -13,4 +13,5 @@ >> # >> #Family-model,Version,Filename,EventType >> 0x420f5160,v1,cavium,core >> +0x430f0af0,v1,cavium,core >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should > be replaced with [[:xdigit:]] to allow for possible future revisions of > chip: >>> >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >>> are ignored/dont-care. >> >> Thanks for pointing that out. See the code masking out those bits in >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the >> equivalent of the MIDR including the revision bits. Thus, the need for >> regular expression matching to avoid having to create a new entry for each >> revision. > > It is same for arm64 too, there is no need to add an entry for every > revision change, need to add when part number changes. > This patch is not intended to add entry for revision change, the fact > of the matter is that, there is complete MIDR change (vulcan to > thunderx2) in B0. > as per current arm64 > implementation(.tools/perf/arch/arm64/util/header.c), it is not > required to have any dontcare marking in mapfile for revision/variant > bits. > > thanks > Ganapat > >> >> -Will >> >>> > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > -Will Cohen >>> >>> thanks >>> Ganapat ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> thanks Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Arnaldo, can you please pull-in this patch? On Thu, Mar 8, 2018 at 9:44 AM, Ganapatrao Kulkarni wrote: > On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: >> On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >>> Hi Will Cohen, >>> >>> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >>> wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> to enable JSON events for B0. >> >> Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo >> --- >> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> index e61c9ca..93c5d14 100644 >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> @@ -13,4 +13,5 @@ >> # >> #Family-model,Version,Filename,EventType >> 0x420f5160,v1,cavium,core >> +0x430f0af0,v1,cavium,core >> 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should > be replaced with [[:xdigit:]] to allow for possible future revisions of > chip: >>> >>> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >>> are ignored/dont-care. >> >> Thanks for pointing that out. See the code masking out those bits in >> linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the >> equivalent of the MIDR including the revision bits. Thus, the need for >> regular expression matching to avoid having to create a new entry for each >> revision. > > It is same for arm64 too, there is no need to add an entry for every > revision change, need to add when part number changes. > This patch is not intended to add entry for revision change, the fact > of the matter is that, there is complete MIDR change (vulcan to > thunderx2) in B0. > as per current arm64 > implementation(.tools/perf/arch/arm64/util/header.c), it is not > required to have any dontcare marking in mapfile for revision/variant > bits. > > thanks > Ganapat > >> >> -Will >> >>> > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > -Will Cohen >>> >>> thanks >>> Ganapat ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> thanks Ganapat
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Thu, Mar 8, 2018 at 12:01 AM, William Cohenwrote: > On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >> Hi Will Cohen, >> >> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >> wrote: >>> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > to enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni >>> >>> Ganapatrao, can you please take this in consideration and if agreeing >>> send a v2 patch? >>> >>> With that I can add an Acked-by: wcohen, Right? >>> >>> - Arnaldo > --- > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index e61c9ca..93c5d14 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,4 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x420f5160,v1,cavium,core > +0x430f0af0,v1,cavium,core > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: >> >> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >> are ignored/dont-care. > > Thanks for pointing that out. See the code masking out those bits in > linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the > equivalent of the MIDR including the revision bits. Thus, the need for > regular expression matching to avoid having to create a new entry for each > revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat > > -Will > >> 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen >>> >> >> thanks >> Ganapat >>> ___ >>> linux-arm-kernel mailing list >>> linux-arm-ker...@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On Thu, Mar 8, 2018 at 12:01 AM, William Cohen wrote: > On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: >> Hi Will Cohen, >> >> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >> wrote: >>> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > to enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni >>> >>> Ganapatrao, can you please take this in consideration and if agreeing >>> send a v2 patch? >>> >>> With that I can add an Acked-by: wcohen, Right? >>> >>> - Arnaldo > --- > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index e61c9ca..93c5d14 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,4 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x420f5160,v1,cavium,core > +0x430f0af0,v1,cavium,core > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: >> >> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) >> are ignored/dont-care. > > Thanks for pointing that out. See the code masking out those bits in > linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the > equivalent of the MIDR including the revision bits. Thus, the need for > regular expression matching to avoid having to create a new entry for each > revision. It is same for arm64 too, there is no need to add an entry for every revision change, need to add when part number changes. This patch is not intended to add entry for revision change, the fact of the matter is that, there is complete MIDR change (vulcan to thunderx2) in B0. as per current arm64 implementation(.tools/perf/arch/arm64/util/header.c), it is not required to have any dontcare marking in mapfile for revision/variant bits. thanks Ganapat > > -Will > >> 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen >>> >> >> thanks >> Ganapat >>> ___ >>> linux-arm-kernel mailing list >>> linux-arm-ker...@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen, > > On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo >wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni >> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? >> >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >>> replaced with [[:xdigit:]] to allow for possible future revisions of chip: > > for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. -Will > >>> >>> 0x430f0af[[:xdigit:]],v1,cavium,core >>> >>> >>> -Will Cohen >> > > thanks > Ganapat >> ___ >> linux-arm-kernel mailing list >> linux-arm-ker...@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote: > Hi Will Cohen, > > On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo > wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni >> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? >> >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >>> replaced with [[:xdigit:]] to allow for possible future revisions of chip: > > for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) > are ignored/dont-care. Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision. -Will > >>> >>> 0x430f0af[[:xdigit:]],v1,cavium,core >>> >>> >>> -Will Cohen >> > > thanks > Ganapat >> ___ >> linux-arm-kernel mailing list >> linux-arm-ker...@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melowrote: > Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> > There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> > to enable JSON events for B0. >> > >> > Signed-off-by: Ganapatrao Kulkarni > > Ganapatrao, can you please take this in consideration and if agreeing > send a v2 patch? > > With that I can add an Acked-by: wcohen, Right? > > - Arnaldo >> > --- >> > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> > 1 file changed, 1 insertion(+) >> > >> > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > index e61c9ca..93c5d14 100644 >> > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > @@ -13,4 +13,5 @@ >> > # >> > #Family-model,Version,Filename,EventType >> > 0x420f5160,v1,cavium,core >> > +0x430f0af0,v1,cavium,core >> > 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > >> >> Hi, >> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >> replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. >> >> 0x430f0af[[:xdigit:]],v1,cavium,core >> >> >> -Will Cohen > thanks Ganapat > ___ > linux-arm-kernel mailing list > linux-arm-ker...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Hi Will Cohen, On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo wrote: > Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: >> > There is MIDR change on ThunderX2 B0, adding an entry to mapfile >> > to enable JSON events for B0. >> > >> > Signed-off-by: Ganapatrao Kulkarni > > Ganapatrao, can you please take this in consideration and if agreeing > send a v2 patch? > > With that I can add an Acked-by: wcohen, Right? > > - Arnaldo >> > --- >> > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + >> > 1 file changed, 1 insertion(+) >> > >> > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > index e61c9ca..93c5d14 100644 >> > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv >> > @@ -13,4 +13,5 @@ >> > # >> > #Family-model,Version,Filename,EventType >> > 0x420f5160,v1,cavium,core >> > +0x430f0af0,v1,cavium,core >> > 0x410fd03[[:xdigit:]],v1,cortex-a53,core >> > >> >> Hi, >> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >> replaced with [[:xdigit:]] to allow for possible future revisions of chip: for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant) are ignored/dont-care. >> >> 0x430f0af[[:xdigit:]],v1,cavium,core >> >> >> -Will Cohen > thanks Ganapat > ___ > linux-arm-kernel mailing list > linux-arm-ker...@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 10:25 AM, John Garry wrote: > On 07/03/2018 14:38, Arnaldo Carvalho de Melo wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni>> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? With that change I would ack it. -Will >> > > JFYI, This patch conflicts with "[PATCH v2 00/11] perf events patches for > improved ARM64 support". I was planning on sending a v3 quite soon. > >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >>> replaced with [[:xdigit:]] to allow for possible future revisions of chip: >>> >>> 0x430f0af[[:xdigit:]],v1,cavium,core >>> >>> >>> -Will Cohen >> >> . > > Thanks, > John > >> > >
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 10:25 AM, John Garry wrote: > On 07/03/2018 14:38, Arnaldo Carvalho de Melo wrote: >> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: >>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni >> >> Ganapatrao, can you please take this in consideration and if agreeing >> send a v2 patch? >> >> With that I can add an Acked-by: wcohen, Right? With that change I would ack it. -Will >> > > JFYI, This patch conflicts with "[PATCH v2 00/11] perf events patches for > improved ARM64 support". I was planning on sending a v3 quite soon. > >> - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core >>> >>> Hi, >>> Like the cortex-a53 the last digit '0' of the match for the MIDR should be >>> replaced with [[:xdigit:]] to allow for possible future revisions of chip: >>> >>> 0x430f0af[[:xdigit:]],v1,cavium,core >>> >>> >>> -Will Cohen >> >> . > > Thanks, > John > >> > >
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 07/03/2018 14:38, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao KulkarniGanapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? JFYI, This patch conflicts with "[PATCH v2 00/11] perf events patches for improved ARM64 support". I was planning on sending a v3 quite soon. - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen . Thanks, John
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 07/03/2018 14:38, Arnaldo Carvalho de Melo wrote: Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: There is MIDR change on ThunderX2 B0, adding an entry to mapfile to enable JSON events for B0. Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? JFYI, This patch conflicts with "[PATCH v2 00/11] perf events patches for improved ARM64 support". I was planning on sending a v3 quite soon. - Arnaldo --- tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv index e61c9ca..93c5d14 100644 --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv @@ -13,4 +13,5 @@ # #Family-model,Version,Filename,EventType 0x420f5160,v1,cavium,core +0x430f0af0,v1,cavium,core 0x410fd03[[:xdigit:]],v1,cortex-a53,core Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen . Thanks, John
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > > to enable JSON events for B0. > > > > Signed-off-by: Ganapatrao KulkarniGanapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo > > --- > > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > index e61c9ca..93c5d14 100644 > > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > @@ -13,4 +13,5 @@ > > # > > #Family-model,Version,Filename,EventType > > 0x420f5160,v1,cavium,core > > +0x430f0af0,v1,cavium,core > > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > > > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should be > replaced with [[:xdigit:]] to allow for possible future revisions of chip: > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > -Will Cohen
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu: > On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > > to enable JSON events for B0. > > > > Signed-off-by: Ganapatrao Kulkarni Ganapatrao, can you please take this in consideration and if agreeing send a v2 patch? With that I can add an Acked-by: wcohen, Right? - Arnaldo > > --- > > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > index e61c9ca..93c5d14 100644 > > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > > @@ -13,4 +13,5 @@ > > # > > #Family-model,Version,Filename,EventType > > 0x420f5160,v1,cavium,core > > +0x430f0af0,v1,cavium,core > > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > > > > Hi, > Like the cortex-a53 the last digit '0' of the match for the MIDR should be > replaced with [[:xdigit:]] to allow for possible future revisions of chip: > > 0x430f0af[[:xdigit:]],v1,cavium,core > > > -Will Cohen
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > to enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni> --- > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index e61c9ca..93c5d14 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,4 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x420f5160,v1,cavium,core > +0x430f0af0,v1,cavium,core > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen
Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote: > There is MIDR change on ThunderX2 B0, adding an entry to mapfile > to enable JSON events for B0. > > Signed-off-by: Ganapatrao Kulkarni > --- > tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv > b/tools/perf/pmu-events/arch/arm64/mapfile.csv > index e61c9ca..93c5d14 100644 > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv > @@ -13,4 +13,5 @@ > # > #Family-model,Version,Filename,EventType > 0x420f5160,v1,cavium,core > +0x430f0af0,v1,cavium,core > 0x410fd03[[:xdigit:]],v1,cortex-a53,core > Hi, Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip: 0x430f0af[[:xdigit:]],v1,cavium,core -Will Cohen