From: Peter Zijlstra <peterz@infradead.org>
To: bdegraaf@codeaurora.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Timur Tabi <timur@codeaurora.org>,
Nathan Lynch <nathan_lynch@mentor.com>,
linux-kernel@vger.kernel.org,
Christopher Covington <cov@codeaurora.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] arm64: Enforce observed order for spinlock and data
Date: Tue, 4 Oct 2016 08:50:15 +0200 [thread overview]
Message-ID: <20161004065015.GK3318@worktop.controleur.wifipass.org> (raw)
In-Reply-To: <b86926dc0203384522e0e6ce18bbb132@codeaurora.org>
On Mon, Oct 03, 2016 at 03:20:57PM -0400, bdegraaf@codeaurora.org wrote:
> Thinking about this, as the reader/writer code has no known "abuse"
> case, I'll remove it from the patchset, then provide a v2 patchset
> with a detailed explanation for the lockref problem using the commits
> you provided as an example, as well as performance consideration.
Please, fix lockref in those patches. Touching the spinlock because
lockref does something dubious really is the wrong thing.
next prev parent reply other threads:[~2016-10-04 6:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 17:40 Brent DeGraaf
2016-09-30 18:43 ` Robin Murphy
2016-10-01 15:45 ` bdegraaf
2016-09-30 18:52 ` Peter Zijlstra
2016-09-30 19:05 ` Peter Zijlstra
2016-10-01 15:59 ` bdegraaf
2016-09-30 19:32 ` Mark Rutland
2016-10-01 16:11 ` bdegraaf
2016-10-01 18:11 ` Mark Rutland
2016-10-03 19:20 ` bdegraaf
2016-10-04 6:50 ` Peter Zijlstra [this message]
2016-10-04 10:12 ` Mark Rutland
2016-10-04 17:53 ` bdegraaf
2016-10-04 18:28 ` bdegraaf
2016-10-04 19:12 ` Mark Rutland
2016-10-05 14:55 ` bdegraaf
2016-10-05 15:10 ` Peter Zijlstra
2016-10-05 15:30 ` bdegraaf
2016-10-12 20:01 ` bdegraaf
2016-10-13 11:02 ` Will Deacon
2016-10-13 20:00 ` bdegraaf
2016-10-14 0:24 ` Mark Rutland
2016-10-05 15:11 ` bdegraaf
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=20161004065015.GK3318@worktop.controleur.wifipass.org \
--to=peterz@infradead.org \
--cc=bdegraaf@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=nathan_lynch@mentor.com \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®