From: Peter Zijlstra <peterz@infradead.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-arch@vger.kernel.org,
linux-s390 <linux-s390@vger.kernel.org>,
kvm@vger.kernel.org, xen-devel-request@lists.xenproject.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
virtualization@lists.linux-foundation.org,
Noam Camus <noamc@ezchip.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/5] stop_machine: yield CPU during stop machine
Date: Mon, 24 Oct 2016 10:47:47 +0200 [thread overview]
Message-ID: <20161024084747.GE3102@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <251574ff-13ba-c0df-76c3-cb7df30894cb@de.ibm.com>
On Mon, Oct 24, 2016 at 09:52:31AM +0200, Christian Borntraeger wrote:
> Peter, I will fixup the patch set (I forgot to remove the lowlatency
> in 2 places) and push it on my tree for linux-next. Lets see what happens.
> Would the tip tree be the right place if things work out ok?
I think so, you're touching a fair bit of kernel/locking/ and there's
bound to be some conflicts with work there. So carrying it in the
locking tree might be best.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
linux-kernel@vger.kernel.org,
linux-s390 <linux-s390@vger.kernel.org>,
linux-arch@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Noam Camus <noamc@ezchip.com>,
virtualization@lists.linux-foundation.org,
xen-devel-request@lists.xenproject.org, kvm@vger.kernel.org
Subject: Re: [PATCH 2/5] stop_machine: yield CPU during stop machine
Date: Mon, 24 Oct 2016 10:47:47 +0200 [thread overview]
Message-ID: <20161024084747.GE3102@twins.programming.kicks-ass.net> (raw)
Message-ID: <20161024084747.o0kPOJqHALY3BW77LAggUXbrtJKxJoOqFYmnbgORtcY@z> (raw)
In-Reply-To: <251574ff-13ba-c0df-76c3-cb7df30894cb@de.ibm.com>
On Mon, Oct 24, 2016 at 09:52:31AM +0200, Christian Borntraeger wrote:
> Peter, I will fixup the patch set (I forgot to remove the lowlatency
> in 2 places) and push it on my tree for linux-next. Lets see what happens.
> Would the tip tree be the right place if things work out ok?
I think so, you're touching a fair bit of kernel/locking/ and there's
bound to be some conflicts with work there. So carrying it in the
locking tree might be best.
next prev parent reply other threads:[~2016-10-24 8:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:58 [PATCH/RFC 0/5] cpu_relax: introduce yield, remove lowlatency Christian Borntraeger
2016-10-21 11:58 ` [PATCH 1/5] processor.h: introduce cpu_relax_yield Christian Borntraeger
2016-10-21 11:58 ` [PATCH 2/5] stop_machine: yield CPU during stop machine Christian Borntraeger
2016-10-21 12:05 ` Peter Zijlstra
2016-10-21 12:05 ` Peter Zijlstra
2016-10-21 12:41 ` Juergen Gross
2016-10-21 12:41 ` Juergen Gross
2016-10-21 12:41 ` Juergen Gross
2016-10-22 0:06 ` Nicholas Piggin
2016-10-22 0:06 ` Nicholas Piggin
2016-10-24 7:52 ` Christian Borntraeger
2016-10-24 7:52 ` Christian Borntraeger
2016-10-24 8:47 ` Peter Zijlstra [this message]
2016-10-24 8:47 ` Peter Zijlstra
2016-10-21 11:58 ` [PATCH 3/5] s390: make cpu_relax a barrier again Christian Borntraeger
2016-10-21 11:58 ` [PATCH 4/5] Remove cpu_relax_lowlatency users Christian Borntraeger
2016-10-21 11:58 ` [PATCH 5/5] remove cpu_relax_lowlatency Christian Borntraeger
2016-10-21 12:06 ` [PATCH/RFC 0/5] cpu_relax: introduce yield, remove lowlatency Peter Zijlstra
2016-10-21 14:57 ` David Miller
2016-10-21 15:08 ` Christian Borntraeger
2016-10-21 15:08 ` Christian Borntraeger
2016-10-21 15:08 ` Christian Borntraeger
2016-10-21 15:12 ` David Miller
2016-10-21 15:12 ` David Miller
2016-10-21 15:12 ` David Miller
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=20161024084747.GE3102@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=borntraeger@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=noamc@ezchip.com \
--cc=npiggin@gmail.com \
--cc=schwidefsky@de.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel-request@lists.xenproject.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 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.