Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 4 Dec 2019 12:55:59 +0800
From:   Wang YanQing <udknight@gmail.com>
To:     afaerber@suse.de
Cc:     linux-kernel@vger.kernel.org, linux-soc@vger.kernel.org,
        linux-realtek-soc@lists.infradead.org
Subject: perf record doesn't work on rtd129x SoC
Message-ID: <20191204045559.GA10458@udknight>
Mail-Followup-To: Wang YanQing <udknight@gmail.com>, afaerber@suse.de,
        linux-kernel@vger.kernel.org, linux-soc@vger.kernel.org,
        linux-realtek-soc@lists.infradead.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Andreas F?rber!

I use "perf record" to debug performance issue on RTD1296 SOC, it does't work, but
the "perf stat" is ok!

After some dig in the kernel, I find the reason is no pmu overflow interrupt, I think
below pmu configuration isn't right for RTD1296:
"
        arm_pmu: arm-pmu {
                compatible = "arm,cortex-a53-pmu";
                interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>;
        };
"

We need 4 PMU SPI for RTD1296 (4 cores), and I guess the 48 isn't right too.

Any suggestion is welcome.

Thanks!