From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
x86@kernel.org, Zhenzhong Duan <zhenzhong.duan@oracle.com>,
James Morse <james.morse@arm.com>,
SRINIVAS <srinivas.eeda@oracle.com>
Subject: Re: [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels
Date: Wed, 30 Jan 2019 15:07:07 +0100 [thread overview]
Message-ID: <20190130140707.GC2296@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1548798828-16156-1-git-send-email-longman@redhat.com>
> Waiman Long (4):
> locking/qspinlock: Handle > 4 slowpath nesting levels
> locking/qspinlock_stat: Track the no MCS node available case
I've taken these two,
> locking/qspinlock_stat: Introduce a generic lockevent counting APIs
> locking/lock_events: Make lock_events available for all archs & other
> locks
while no real objection to these; I feel we should wait until there are
in fact more users of this.
next prev parent reply other threads:[~2019-01-30 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:53 [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels Waiman Long
2019-01-29 21:53 ` [PATCH v3 1/4] locking/qspinlock: Handle > 4 slowpath " Waiman Long
2019-02-04 8:58 ` [tip:locking/core] " tip-bot for Waiman Long
2019-01-29 21:53 ` [PATCH v3 2/4] locking/qspinlock_stat: Track the no MCS node available case Waiman Long
2019-02-04 8:58 ` [tip:locking/core] " tip-bot for Waiman Long
2019-01-29 21:53 ` [PATCH v3 3/4] locking/qspinlock_stat: Introduce a generic lockevent counting APIs Waiman Long
2019-01-29 21:53 ` [PATCH v3 4/4] locking/lock_events: Make lock_events available for all archs & other locks Waiman Long
2019-01-30 14:07 ` Peter Zijlstra [this message]
2019-01-30 16:25 ` [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels Waiman Long
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=20190130140707.GC2296@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=srinivas.eeda@oracle.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=zhenzhong.duan@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.