From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Mark Rutland <mark.rutland@arm.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:42:37 +0100 [thread overview]
Message-ID: <20161111164237.1f381e57@mschwide> (raw)
In-Reply-To: <20161111091622.GA4019@osiris>
On Fri, 11 Nov 2016 10:16:22 +0100
Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> Hi Mark,
>
> > 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:
> > > > Heiko and I have been working on THREAD_INFO_IN_TASK for s390 and arm64
> > > > respectively, and we're both targetting v4.10.
> > > >
> > > > These are the common core changes which we both require. I've put together a
> > > > branch [1,2] based on v4.9-rc2. I intend to tag this at some point next week so
> > > > that Heiko and I have a stable base.
> > >
> > > As a heads-up, I've collated the tags I've received in the last few days, along
> > > with the comment Andy requested in the v1 thread, and tagged this as
> > > core-ti-stack-split [1].
> > >
> > > Thanks,
> > > Mark.
> > >
> > > [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
>
> branch soon.
>
> In result we will have a struct thread_info that only contains the flags
> field like x86 does.
> So we don't depend an any other patches anymore...
Just pushed our collected works to the features branch, in case you are
interested.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2016-11-11 15:42 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 [this message]
2016-11-11 16:23 ` Mark Rutland
-- 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=20161111164237.1f381e57@mschwide \
--to=schwidefsky@de.ibm.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=mark.rutland@arm.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.