All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jinpu Wang <jinpuwang@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "v3.14+, only the raid10 part" <stable@vger.kernel.org>
Subject: Re: [RFC stable-4.14 00/11] PSI feature for 4.14
Date: Fri, 15 Mar 2019 11:48:49 +0100	[thread overview]
Message-ID: <CAD9gYJJ=eD+zNHZA2nyhQ63Pse-LFdZaWaCs-MXQd-TS9DhSCA@mail.gmail.com> (raw)
In-Reply-To: <20190314172905.GC28850@kroah.com>

Greg KH <gregkh@linuxfoundation.org> 于2019年3月14日周四 下午6:29写道：
>
> On Wed, Mar 13, 2019 at 11:15:43AM +0100, Jinpu Wang wrote:
> > snip
> > > This is nice, but why?  We can't take new features into the stable
> > > kernel trees.  For Android devices (which do want PSI), all of the
> > > patches are already backported into the android-common 4.14 branch,
> > > right?  Or does this differ from that backport somehow?
> > >
> > > thanks,
> > >
> > > greg k-h
> > (Resend to reply to all, sorry)
> >
> > Thanks Greg,
> >
> > We want the feature for our product. Yeah, I know we have
> > stable-rules, didn't expect
> > the patches to be included, just in case other guys also need PSI.
> >
> > I'm not aware of android-common did the backport already, could you
> > point me the link?
> >
> > I checked in
> > https://android.googlesource.com/kernel/common/+/refs/heads/android-4.14*
> >
> > I didn't find the psi support.
>
> Ah, I was wrong, sorry, it has been submitted to AOSP, but not merged
> yet.  Here's the 4.14 patches queued up and ready to go:
>         https://android-review.googlesource.com/q/topic:%22psi+4.14+backport%22+(status:open%20OR%20status:merged)
>
> The 4.9 and 4.19 branches also have them queued up:
>         https://android-review.googlesource.com/q/topic:%22psi+4.9+backport%22+(status:open%20OR%20status:merged)
>         https://android-review.googlesource.com/q/topic:%22psi+4.19+backport%22+(status:open%20OR%20status:merged)
>
> I talked to the developer this week and he said he was waiting for a few
> of the remaining patches to be merged upstream first before merging to
> AOSP to ensure that nothing diverged.  Hopefully that should happen in a
> few weeks or so, after the merge window is open and maintainers reopen
> their development branches.
>
> thanks,
>
> greg k-h

Thanks Greg,

It's very helpful, I indeed missed some patches.
I will check their backport.

Regards,

Jack

      reply	other threads:[~2019-03-15 10:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 10:19 [RFC stable-4.14 00/11] PSI feature for 4.14 Jack Wang
2019-03-12 10:19 ` [stable-4.14 01/11] mm: workingset: don't drop refault information prematurely Jack Wang
2019-03-12 16:37   ` Linus Torvalds
2019-03-13 10:05     ` Jinpu Wang
2019-03-12 10:19 ` [stable-4.14 02/11] mm: workingset: tell cache transitions from workingset thrashing Jack Wang
2019-03-12 10:19 ` [stable-4.14 03/11] delayacct: track delays from thrashing cache pages Jack Wang
2019-03-12 10:19 ` [stable-4.14 04/11] sched: loadavg: consolidate LOAD_INT, LOAD_FRAC, CALC_LOAD Jack Wang
2019-03-12 10:19 ` [stable-4.14 05/11] sched: loadavg: make calc_load_n() public Jack Wang
2019-03-12 10:19 ` [stable-4.14 06/11] sched: sched.h: make rq locking and clock functions available in stats.h Jack Wang
2019-03-12 10:19 ` [stable-4.14 07/11] sched: introduce this_rq_lock_irq() Jack Wang
2019-03-12 10:19 ` [stable-4.14 08/11] psi: pressure stall information for CPU, memory, and IO Jack Wang
2019-03-12 10:20 ` [stable-4.14 09/11] psi: cgroup support Jack Wang
2019-03-12 10:20 ` [stable-4.14 10/11] kernel/sched/psi.c: simplify cgroup_move_task() Jack Wang
2019-03-12 10:20 ` [stable-4.14 11/11] psi: make disabling/enabling easier for vendor kernels Jack Wang
2019-03-12 11:43 ` [RFC stable-4.14 00/11] PSI feature for 4.14 Greg KH
2019-03-13 10:15   ` Jinpu Wang
2019-03-14 17:29     ` Greg KH
2019-03-15 10:48       ` Jinpu Wang [this message]

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='CAD9gYJJ=eD+zNHZA2nyhQ63Pse-LFdZaWaCs-MXQd-TS9DhSCA@mail.gmail.com' \
    --to=jinpuwang@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.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.