linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] Switch arm64 over to qrwlock
Date: Tue, 24 Oct 2017 15:48:10 +0100	[thread overview]
Message-ID: <20171024144810.GD14568@arm.com> (raw)
In-Reply-To: <20171019165332.GD30652@arm.com>

Ingo, Peter,

Would you be willing to merge this via -tip, please? I'm happy to
rebase/repost as required, but the code is in good shape now.

Will

On Thu, Oct 19, 2017 at 05:53:32PM +0100, Will Deacon wrote:
> On Thu, Oct 12, 2017 at 01:20:46PM +0100, Will Deacon wrote:
> > This is version three of the patches previously posted here:
> > 
> > v1: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/534666.html
> > v2: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/534981.html
> > 
> > Changes since v2 include:
> > 
> >   * Drop unused cnt argument
> >   * Fix typo in UNLOCK Kconfig inlining options
> >   * Added Tested-by tags
> > 
> > Thanks to all of those who provided review and testing feedback!
> 
> I've not had any more feedback on this and the testing results are very
> encouraging so I'd like to merge it for 4.15. However, it might make more
> sense for the whole thing to go via -tip instead.
> 
> Ingo, Peter: what do you prefer?
> 
> Will
> 
> > Will Deacon (5):
> >   kernel/locking: Use struct qrwlock instead of struct __qrwlock
> >   locking/atomic: Add atomic_cond_read_acquire
> >   kernel/locking: Use atomic_cond_read_acquire when spinning in qrwlock
> >   arm64: locking: Move rwlock implementation over to qrwlocks
> >   kernel/locking: Prevent slowpath writers getting held up by fastpath
> > 
> >  arch/arm64/Kconfig                      |  17 ++++
> >  arch/arm64/include/asm/Kbuild           |   1 +
> >  arch/arm64/include/asm/spinlock.h       | 164 +-------------------------------
> >  arch/arm64/include/asm/spinlock_types.h |   6 +-
> >  include/asm-generic/atomic-long.h       |   3 +
> >  include/asm-generic/qrwlock.h           |  37 ++-----
> >  include/asm-generic/qrwlock_types.h     |  15 ++-
> >  include/linux/atomic.h                  |   4 +
> >  kernel/locking/qrwlock.c                |  86 +++--------------
> >  9 files changed, 61 insertions(+), 272 deletions(-)
> > 
> > -- 
> > 2.1.4
> > 

  reply	other threads:[~2017-10-24 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 12:20 [PATCH v3 0/5] Switch arm64 over to qrwlock Will Deacon
2017-10-12 12:20 ` [PATCH v3 1/5] kernel/locking: Use struct qrwlock instead of struct __qrwlock Will Deacon
2017-10-12 12:20 ` [PATCH v3 2/5] locking/atomic: Add atomic_cond_read_acquire Will Deacon
2017-10-12 12:20 ` [PATCH v3 3/5] kernel/locking: Use atomic_cond_read_acquire when spinning in qrwlock Will Deacon
2017-10-12 12:20 ` [PATCH v3 4/5] arm64: locking: Move rwlock implementation over to qrwlocks Will Deacon
2017-10-12 12:20 ` [PATCH v3 5/5] kernel/locking: Prevent slowpath writers getting held up by fastpath Will Deacon
2017-10-12 13:16 ` [PATCH v3 0/5] Switch arm64 over to qrwlock Adam Wallis
2017-10-19 16:53 ` Will Deacon
2017-10-24 14:48   ` Will Deacon [this message]
2017-10-24 15:40     ` Ingo Molnar
2017-10-25  8:36       ` Peter Zijlstra
2017-10-28  6:10   ` chengjian (D)

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=20171024144810.GD14568@arm.com \
    --to=will.deacon@arm.com \
    --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).