Messages in this thread | | | Subject | Re: [RFC PATCH v2 09/13] perf vendor events: Add JSON metrics for imx8mm DDR Perf | From | John Garry <> | Date | Mon, 20 Apr 2020 15:20:29 +0100 |
| |
On 20/04/2020 12:25, Joakim Zhang wrote: >>> imx8_ddr.write_cycles: 13153 1000495125 1000495125 >>> # time counts unit events >>> 1.000476625 13153 imx8_ddr.write_cycles >> # 205.5 MB imx8mm_ddr_write.all >>> imx8_ddr.write_cycles: 3582 1000681375 1000681375 >>> 2.001167750 3582 imx8_ddr.write_cycles >> # 56.0 MB imx8mm_ddr_write.all >>> >>> 8QM: >>> root@imx8qmmek:~# ./perf stat -v -a -I 1000 -M imx8qm_ddr_read.all >> Note: for this example, I don't know why you didn't use imx8mm_ddr_write.all, >> as for your 8MM test, so we can compare the same. > Yes, I use the imx8mm_ddr_write.all, I just re-name the metric, change nothing else.
Well it's hard to even keep up - let alone help - when you're debugging QM support, which is not supported in this series (only MM is), and I don't know exactly what is in this JSON who have created (for QM).
For a start, the MM json will use "i.mx8mm" compat, which I figure should not work for QM. Please explain this.
Thanks, John
> >>> Using CPUID 0x00000000410fd030 >>> metric expr imx8_ddr.read_cycles * 4 * 4 for i
| |