From: Peter Zijlstra <peterz@infradead.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCHv2 0/3] improve wait logic of stop_machine
Date: Thu, 13 Jun 2019 15:48:58 +0200 [thread overview]
Message-ID: <20190613134858.GL3436@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190613103510.60529-1-heiko.carstens@de.ibm.com>
On Thu, Jun 13, 2019 at 12:35:07PM +0200, Heiko Carstens wrote:
> Heiko Carstens (2):
> processor: remove spin_cpu_yield
> processor: get rid of cpu_relax_yield
>
> Martin Schwidefsky (1):
> s390: improve wait logic of stop_machine
>
> arch/powerpc/include/asm/processor.h | 2 --
> arch/s390/include/asm/processor.h | 7 +------
> arch/s390/kernel/processor.c | 19 +++++++++++++------
> arch/s390/kernel/smp.c | 2 +-
> include/linux/processor.h | 9 ---------
> include/linux/sched.h | 4 ----
> include/linux/stop_machine.h | 1 +
> kernel/stop_machine.c | 19 ++++++++++++++-----
> 8 files changed, 30 insertions(+), 33 deletions(-)
Seems sensible to me.
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
next prev parent reply other threads:[~2019-06-13 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 10:35 [PATCHv2 0/3] improve wait logic of stop_machine Heiko Carstens
2019-06-13 10:35 ` Heiko Carstens
2019-06-13 10:35 ` [PATCHv2 1/3] processor: remove spin_cpu_yield Heiko Carstens
2019-06-13 10:35 ` Heiko Carstens
2019-06-13 10:35 ` [PATCHv2 2/3] s390: improve wait logic of stop_machine Heiko Carstens
2019-06-13 10:35 ` Heiko Carstens
2019-06-13 10:35 ` [PATCHv2 3/3] processor: get rid of cpu_relax_yield Heiko Carstens
2019-06-13 10:35 ` Heiko Carstens
2019-06-13 13:48 ` Peter Zijlstra [this message]
2019-06-13 13:48 ` [PATCHv2 0/3] improve wait logic of stop_machine Peter Zijlstra
2019-06-13 19:57 ` Thomas Gleixner
2019-06-13 19:57 ` Thomas Gleixner
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=20190613134858.GL3436@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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