From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, efault@gmx.de,
tglx@linutronix.de, mingo@kernel.org,
alexander.levin@verizon.com
Subject: Re: Runqueue spinlock recursion on arm64 v4.15
Date: Fri, 2 Feb 2018 20:55:06 +0100 [thread overview]
Message-ID: <20180202195506.GP2269@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180202192704.nqwjsthl3agszhzt@lakrids.cambridge.arm.com>
On Fri, Feb 02, 2018 at 07:27:04PM +0000, Mark Rutland wrote:
> ... in some cases, owner_cpu is -1, so I guess we're racing with an
> unlock. I only ever see this on the runqueue locks in wake up functions.
So runqueue locks are special in that the owner changes over a contex
switch, maybe something goes funny there?
next prev parent reply other threads:[~2018-02-02 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 19:27 Runqueue spinlock recursion on arm64 v4.15 Mark Rutland
2018-02-02 19:55 ` Peter Zijlstra [this message]
2018-02-02 22:07 ` Mark Rutland
2018-02-05 13:36 ` Mark Rutland
2018-02-05 14:02 ` Peter Zijlstra
2018-02-05 14:15 ` Mark Rutland
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=20180202195506.GP2269@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexander.levin@verizon.com \
--cc=efault@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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