From: Peter Zijlstra <peterz@infradead.org>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH 0/2] A couple of qspinlock fixes
Date: Tue, 13 Feb 2018 14:45:33 +0100 [thread overview]
Message-ID: <20180213134533.GK25201@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1518528177-19169-1-git-send-email-will.deacon@arm.com>
On Tue, Feb 13, 2018 at 01:22:55PM +0000, Will Deacon wrote:
> Hi all,
>
> Here are a couple of fixes for qspinlock issues I've found by code
> inspection whilst investigating the possibility of enabling this for
> arm64. The first patch fixes a problem with unusual hardware re-ordering
> whilst the second fixes a problem with unusual compiler re-ordering.
Thanks Will!
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
prev parent reply other threads:[~2018-02-13 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 13:22 Will Deacon
2018-02-13 13:22 ` [PATCH 1/2] locking/qspinlock: Ensure node is initialised before updating prev->next Will Deacon
2018-02-13 15:27 ` [tip:locking/urgent] " tip-bot for Will Deacon
2018-02-13 13:22 ` [PATCH 2/2] locking/qspinlock: Ensure node->count is updated before initialising node Will Deacon
2018-02-13 15:27 ` [tip:locking/urgent] " tip-bot for Will Deacon
2018-02-13 13:45 ` Peter Zijlstra [this message]
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=20180213134533.GK25201@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
Powered by JetHome