From: Mark Rutland <mark.rutland@arm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
catalin.marinas@arm.com, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, keescook@chromium.org,
luto@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390
Date: Fri, 11 Nov 2016 16:23:43 +0000 [thread overview]
Message-ID: <20161111162343.GK11945@leverpostej> (raw)
In-Reply-To: <20161111164237.1f381e57@mschwide>
On Fri, Nov 11, 2016 at 04:42:37PM +0100, Martin Schwidefsky wrote:
> On Fri, 11 Nov 2016 10:16:22 +0100
> Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> > > On Wed, Nov 02, 2016 at 03:56:26PM +0000, Mark Rutland wrote:
> > > > On Wed, Oct 26, 2016 at 06:43:05PM +0100, Mark Rutland wrote:
> > > > [1] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git core-ti-stack-split
> > >
> > > I believe that Catalin's hoping to take my arm64 patches for v4.10,
> > > using the above tag as a base.
> > >
> > > What's the plan for s390? Are you happy to do the same?
> >
> > We intend to merge the s390 variant also for v4.10. Our approach has
> > changed however: we came to the conclusion that having a per-cpu preempt
> > count will generate better code on s390; so Martin implemented that.
> >
> > And while being at it he also moved the rest of the s390 specific stuff out
> > of our struct thread_info. The corresponding patches will be pushed to
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features
> Just pushed our collected works to the features branch, in case you are
> interested.
Thanks for the heads-up!
It doesn't look like we can do similar for arm64 (we don't have anything
akin to the lowcore stuff), but it certainly seems nicer for s390.
Thanks,
Mark.
next prev parent reply other threads:[~2016-11-11 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:43 [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390 Mark Rutland
2016-10-26 17:43 ` [PATCHv2 1/2] thread_info: factor out restart_block Mark Rutland
2016-10-26 17:43 ` [PATCHv2 2/2] thread_info: include <current.h> for THREAD_INFO_IN_TASK Mark Rutland
2016-11-02 15:56 ` [PATCHv2 0/2] THREAD_INFO_IN_TASK prep work for arm64+s390 Mark Rutland
2016-11-10 18:13 ` Mark Rutland
2016-11-11 9:16 ` Heiko Carstens
2016-11-11 15:42 ` Martin Schwidefsky
2016-11-11 16:23 ` Mark Rutland [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-26 17:42 Mark Rutland
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=20161111162343.GK11945@leverpostej \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=schwidefsky@de.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