From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: AArch64 arch_spin_unlock not signaling global event?
Date: Wed, 31 Jul 2013 17:25:17 -0400 [thread overview]
Message-ID: <51F980BD.2050904@codeaurora.org> (raw)
In-Reply-To: <CANz0V+6-yk9jWZ1y9zidKFJAhDof9qQR1uAHzsvhwswApMbxUA@mail.gmail.com>
Hi Andrei,
On 07/31/2013 04:19 PM, Andrei E. Warkentin wrote:
> Hiya,
>
> I've noticed the AArch64 arch_spin_unlock is implemented with the
> 'stlr' instruction.
>
> Shouldn't that be followed by a 'sev'?
Check the git log and go through silver to make sure you're looking at the
latest documentation. I believe the link from infocenter is stale.
Regards,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2013-07-31 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 20:19 AArch64 arch_spin_unlock not signaling global event? Andrei E. Warkentin
2013-07-31 21:25 ` Christopher Covington [this message]
2013-08-01 8:48 ` Will Deacon
2013-08-01 10:23 ` Andrei E. Warkentin
2013-08-02 10:11 ` Will Deacon
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=51F980BD.2050904@codeaurora.org \
--to=cov@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).