From: Will Deacon <will.deacon@arm.com>
To: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
peterz@infradead.org, arnd@arndb.de, Waiman.Long@hpe.com,
mingo@redhat.com, boqun.feng@gmail.com
Subject: Re: [PATCH v4] locking/qrwlock: Fix write unlock issue in big endian
Date: Thu, 21 Jul 2016 17:17:31 +0100 [thread overview]
Message-ID: <20160721161731.GI21616@arm.com> (raw)
In-Reply-To: <1468835259-4486-1-git-send-email-xinhui.pan@linux.vnet.ibm.com>
On Mon, Jul 18, 2016 at 05:47:39PM +0800, Pan Xinhui wrote:
> From: pan xinhui <xinhui.pan@linux.vnet.ibm.com>
>
> This patch aims to get rid of endianness in queued_write_unlock(). We
> want to set __qrwlock->wmode to NULL, however the address is not
> &lock->cnts in big endian machine. That causes queued_write_unlock()
> write NULL to the wrong field of __qrwlock.
>
> So implement __qrwlock_write_byte() which returns the correct
> __qrwlock->wmode address.
>
> Suggested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Signed-off-by: Pan Xinhui <xinhui.pan@linux.vnet.ibm.com>
> ---
> change from v3:
> rewrite totally. :)
> change from v2:
> change macro's name, add comments.
> change from v1:
> A typo fix which is really bad...
> thanks Will for the carefull review.
> ---
> include/asm-generic/qrwlock.h | 27 +++++++++++++++++++++++++--
> 1 file changed, 25 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-generic/qrwlock.h b/include/asm-generic/qrwlock.h
> index 54a8e65..7d026bf 100644
> --- a/include/asm-generic/qrwlock.h
> +++ b/include/asm-generic/qrwlock.h
> @@ -25,7 +25,20 @@
> #include <asm-generic/qrwlock_types.h>
>
> /*
> - * Writer states & reader shift and bias
> + * Writer states & reader shift and bias.
> + *
> + * | +0 | +1 | +2 | +3 |
> + * ----+----+----+----+----+
> + * LE | 78 | 56 | 34 | 12 | 0x12345678
> + * ----+----+----+----+----+
> + * | wr | rd |
> + * +----+----+----+----+
> + *
> + * ----+----+----+----+----+
> + * BE | 12 | 34 | 56 | 78 | 0x12345678
> + * ----+----+----+----+----+
> + * | rd | wr |
> + * +----+----+----+----+
> */
> #define _QW_WAITING 1 /* A writer is waiting */
> #define _QW_LOCKED 0xff /* A writer holds the lock */
> @@ -134,12 +147,22 @@ static inline void queued_read_unlock(struct qrwlock *lock)
> }
>
> /**
> + * __qrwlock_write_byte - retrieve the write byte address of a queue rwlock
> + * @lock : Pointer to queue rwlock structure
> + * Return: the write byte address of a queue rwlock
> + */
> +static inline u8 *__qrwlock_write_byte(struct qrwlock *lock)
> +{
> + return (u8 *)lock + 3 * IS_BUILTIN(CONFIG_CPU_BIG_ENDIAN);
> +}
Might be worth a comment here, saying that IS_BUILTIN expands to 1 or 0.
Either way, the patch looks correct to me:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
prev parent reply other threads:[~2016-07-21 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 9:47 [PATCH v4] locking/qrwlock: Fix write unlock issue in big endian Pan Xinhui
2016-07-21 16:17 ` Will Deacon [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=20160721161731.GI21616@arm.com \
--to=will.deacon@arm.com \
--cc=Waiman.Long@hpe.com \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xinhui.pan@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).