From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: Add PMU node for APM X-Gene Storm SOC
Date: Mon, 23 Jun 2014 23:42:00 -0400 [thread overview]
Message-ID: <53A8F388.80101@redhat.com> (raw)
In-Reply-To: <CACVXFVMiOvV=CytiaLFgEdt3_f7frJ6afjz39iLhafOhvJ0m7g@mail.gmail.com>
On 06/23/2014 10:47 PM, Ming Lei wrote:
> On Thu, Mar 20, 2014 at 5:47 PM, Vinayak Kale <vkale@apm.com> wrote:
>> This patch adds the PMU device tree node for APM X-Gene Storm SOC.
>>
>> Please note that this patch has dependancy on a GIC driver patch [1] which is
>> yet to be approved by maintainers.
>>
>> [1]- https://lkml.org/lkml/2014/2/27/605
>> (irqchip:gic: change access of gicc_ctrl register to read modify write)
> No matter if Feng Kan's gic patch is applied or not, perf(PMU)
> still can't work well with your patch, and the failure[1] will be
> triggered when 'perf top' is started.
>
> The failure happened during the 1st pmu overflow interrupt.
>
> I test several mustang boards, and all has the problem with
> upstream kernel.
Note that the GIC bypass register config is set by the firmware and this
only preserves the original setting, so you could be running an older
firmware (such as U-Boot). On our (UEFI-enabled systems, complete with
correct patch) perf top runs correctly without any such problems.
Jon.
next prev parent reply other threads:[~2014-06-24 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 9:47 [PATCH 0/2] arm64: Add PMU node for APM X-Gene Storm SoC Vinayak Kale
2014-03-20 9:47 ` [PATCH 1/2] dt-bindings: Add Potenza PMU binding Vinayak Kale
2014-03-20 9:47 ` [PATCH 2/2] arm64: dts: Add PMU node for APM X-Gene Storm SOC Vinayak Kale
2014-06-24 2:47 ` Ming Lei
2014-06-24 3:42 ` Jon Masters [this message]
2014-06-24 4:17 ` Ming Lei
2014-06-24 7:00 ` Ming Lei
2014-07-12 16:40 ` Dann Frazier
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=53A8F388.80101@redhat.com \
--to=jcm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox