From: Daniel Thompson <daniel.thompson@linaro.org>
To: Mark Rutland <mark.rutland@arm.com>,
Mario Smarduch <m.smarduch@samsung.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
wim@iguana.be, Christoffer Dall <christoffer.dall@linaro.org>,
linux-watchdog@vger.kernel.org
Subject: Re: arm/arm64 HARDLOCKUP Detector and PERF NMI support
Date: Mon, 11 Jan 2016 11:25:49 +0000 [thread overview]
Message-ID: <5693913D.5060308@linaro.org> (raw)
In-Reply-To: <20160111102658.GB6499@leverpostej>
On 11/01/16 10:26, Mark Rutland wrote:
> Hi,
>
> On Sat, Jan 09, 2016 at 04:13:48PM -0800, Mario Smarduch wrote:
>> I'm trying to get HARDLOCKUP detector to work on arm (on foundation
>> model and Juno, but armv7 should have the same issue). Turns out there is no
>> PERF NMI support (HAVE_PERF_EVENTS_NMI), which I guess would be PMU NMI - I
>> tested overflow on cycle counter and PMU interrupts can be masked. HARDLOCKUP
>> assumes perf interrupts are non-maskable and uses the PMU to program an NMI to
>> detect hard lockup and that in turn drives softlockup detection.
>>
>> Is there something, someplace in ARM manuals that addresses this, searched the
>> manuals but couldn't find anything?
>>
>> Or other approaches that I'm not aware off or have floated on the mailing list.
>
> Russell and Daniel did some work [1,2] to use FIQs as NMIs on arm, for
> backtracing and PMU overflow.
>
> For arm64 the kernel always runs on the non-secure side, so we don't
> expect to have access to FIQ. It's possible to implement NMIs using
> priorities (which it looks like Daniel was looking into [3]).
Thanks Mark.
The blog post is still pretty much describes my ambitions and the
benefits these features can bring. It also has a link to a fairly
elderly kernel that contains all the features fully integrated.
There are more patchsets for both ARM (if/f FIQ is available) and ARM64
(if/f device has GICv3). However these only provide NMI backtrace.
arm: http://thread.gmane.org/gmane.linux.kernel/2112583
arm64: http://thread.gmane.org/gmane.linux.kernel/2037735 (Mark's
link to my git repo is more up to date than this patchset)
To get the hard lockup and profiling support upstream then my old code
to integrate NMIs into the irq subsystem (which was just a cut down
clone of the existing irq infrastructure) needs to be redesigned.
However I decided to put the rewrite on ice until I get the foundational
patches right.
Daniel.
WARNING: multiple messages have this Message-ID (diff)
From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: arm/arm64 HARDLOCKUP Detector and PERF NMI support
Date: Mon, 11 Jan 2016 11:25:49 +0000 [thread overview]
Message-ID: <5693913D.5060308@linaro.org> (raw)
In-Reply-To: <20160111102658.GB6499@leverpostej>
On 11/01/16 10:26, Mark Rutland wrote:
> Hi,
>
> On Sat, Jan 09, 2016 at 04:13:48PM -0800, Mario Smarduch wrote:
>> I'm trying to get HARDLOCKUP detector to work on arm (on foundation
>> model and Juno, but armv7 should have the same issue). Turns out there is no
>> PERF NMI support (HAVE_PERF_EVENTS_NMI), which I guess would be PMU NMI - I
>> tested overflow on cycle counter and PMU interrupts can be masked. HARDLOCKUP
>> assumes perf interrupts are non-maskable and uses the PMU to program an NMI to
>> detect hard lockup and that in turn drives softlockup detection.
>>
>> Is there something, someplace in ARM manuals that addresses this, searched the
>> manuals but couldn't find anything?
>>
>> Or other approaches that I'm not aware off or have floated on the mailing list.
>
> Russell and Daniel did some work [1,2] to use FIQs as NMIs on arm, for
> backtracing and PMU overflow.
>
> For arm64 the kernel always runs on the non-secure side, so we don't
> expect to have access to FIQ. It's possible to implement NMIs using
> priorities (which it looks like Daniel was looking into [3]).
Thanks Mark.
The blog post is still pretty much describes my ambitions and the
benefits these features can bring. It also has a link to a fairly
elderly kernel that contains all the features fully integrated.
There are more patchsets for both ARM (if/f FIQ is available) and ARM64
(if/f device has GICv3). However these only provide NMI backtrace.
arm: http://thread.gmane.org/gmane.linux.kernel/2112583
arm64: http://thread.gmane.org/gmane.linux.kernel/2037735 (Mark's
link to my git repo is more up to date than this patchset)
To get the hard lockup and profiling support upstream then my old code
to integrate NMIs into the irq subsystem (which was just a cut down
clone of the existing irq infrastructure) needs to be redesigned.
However I decided to put the rewrite on ice until I get the foundational
patches right.
Daniel.
next prev parent reply other threads:[~2016-01-11 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569199C0.9030500@samsung.com>
2016-01-10 0:13 ` arm/arm64 HARDLOCKUP Detector and PERF NMI support Mario Smarduch
2016-01-11 10:26 ` Mark Rutland
2016-01-11 10:26 ` Mark Rutland
2016-01-11 11:25 ` Daniel Thompson [this message]
2016-01-11 11:25 ` Daniel Thompson
2016-01-11 20:06 ` Mario Smarduch
2016-01-11 20:06 ` Mario Smarduch
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=5693913D.5060308@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=Marc.Zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.smarduch@samsung.com \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.com \
--cc=wim@iguana.be \
/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.