From: Christian Brauner <christian.brauner@ubuntu.com>
To: Li Li <dualli@chromium.org>
Cc: dualli@google.com, tkjos@google.com, gregkh@linuxfoundation.org,
christian@brauner.io, arve@android.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
maco@google.com, hridya@google.com, surenb@google.com,
joel@joelfernandes.org, kernel-team@android.com,
jannh@google.com
Subject: Re: [PATCH v3 0/3] Binder: Enable App Freezing Capability
Date: Wed, 17 Mar 2021 19:00:48 +0100 [thread overview]
Message-ID: <20210317180048.inzdursqmnvxkgwp@wittgenstein> (raw)
In-Reply-To: <20210316011630.1121213-1-dualli@chromium.org>
On Mon, Mar 15, 2021 at 06:16:27PM -0700, Li Li wrote:
> From: Li Li <dualli@google.com>
>
> To improve the user experience when switching between recently used
> applications, the background applications which are not currently needed
> are cached in the memory. Normally, a well designed application will not
> consume valuable CPU resources in the background. However, it's possible
> some applications are not able or willing to behave as expected, wasting
> energy even after being cached.
>
> It is a good idea to freeze those applications when they're only being
> kept alive for the sake of faster startup and energy saving. These kernel
> patches will provide the necessary infrastructure for user space framework
> to freeze and thaw a cached process, check the current freezing status and
> correctly deal with outstanding binder transactions to frozen processes.
>
> Changes in v2: avoid panic by using pr_warn for unexpected cases.
> Changes in v3: improved errcode logic in binder_proc_transaction().
>
> Marco Ballesio (3):
> binder: BINDER_FREEZE ioctl
> binder: use EINTR for interrupted wait for work
> binder: BINDER_GET_FROZEN_INFO ioctl
>
> drivers/android/binder.c | 198 ++++++++++++++++++++++++++--
> drivers/android/binder_internal.h | 18 +++
> include/uapi/linux/android/binder.h | 20 +++
> 3 files changed, 224 insertions(+), 12 deletions(-)
[+Cc Jann]
Christian
next prev parent reply other threads:[~2021-03-17 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 1:16 Li Li
2021-03-16 1:16 ` [PATCH v3 1/3] binder: BINDER_FREEZE ioctl Li Li
2021-03-16 15:28 ` Todd Kjos
2021-03-17 18:15 ` Christian Brauner
2021-03-16 1:16 ` [PATCH v3 2/3] binder: use EINTR for interrupted wait for work Li Li
2021-03-16 1:16 ` [PATCH v3 3/3] binder: BINDER_GET_FROZEN_INFO ioctl Li Li
2021-03-17 18:00 ` Christian Brauner [this message]
2021-03-17 20:17 ` [PATCH v3 0/3] Binder: Enable App Freezing Capability Jann Horn
2021-03-18 16:20 ` Todd Kjos
2021-03-18 17:10 ` Li Li
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=20210317180048.inzdursqmnvxkgwp@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=dualli@chromium.org \
--cc=dualli@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hridya@google.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@google.com \
--cc=surenb@google.com \
--cc=tkjos@google.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
all inboxes | Powered by JetHome®