public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu-Ting Tseng <yutingtseng@google.com>
To: cmllamas@google.com, tkjos@google.com, gregkh@linuxfoundation.org
Cc: arve@android.com, maco@android.com, joel@joelfernandes.org,
	 brauner@kernel.org, surenb@google.com, aliceryhl@google.com,
	 kernel-team@android.com, linux-kernel@vger.kernel.org,
	 Yu-Ting Tseng <yutingtseng@google.com>
Subject: [PATCH v9 0/2] binder: frozen notification
Date: Tue,  9 Jul 2024 00:00:45 -0700	[thread overview]
Message-ID: <20240709070047.4055369-2-yutingtseng@google.com> (raw)

This patchset adds a binder feature that allows userspace to subscribe
to frozen state changes. See patch 1/2 for more details on why this is
needed. Patch 1/2 contains the core implementation. Patch 2/2 contains
a binderfs change so userspace can query whether this feature is
supported.


Yu-Ting Tseng (2):
  binder: frozen notification
  binder: frozen notification binder_features flag

 drivers/android/binder.c                      | 284 +++++++++++++++++-
 drivers/android/binder_internal.h             |  21 +-
 drivers/android/binderfs.c                    |   8 +
 include/uapi/linux/android/binder.h           |  36 +++
 .../filesystems/binderfs/binderfs_test.c      |   1 +
 5 files changed, 346 insertions(+), 4 deletions(-)


base-commit: 14d7c92f8df9c0964ae6f8b813c1b3ac38120825
-- 
2.45.2.803.g4e1b14247a-goog


             reply	other threads:[~2024-07-09  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  7:00 Yu-Ting Tseng [this message]
2024-07-09  7:00 ` [PATCH v9 1/2] binder: frozen notification Yu-Ting Tseng
2024-07-16 14:11   ` Carlos Llamas
2024-07-09  7:00 ` [PATCH v9 2/2] binder: frozen notification binder_features flag Yu-Ting Tseng

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=20240709070047.4055369-2-yutingtseng@google.com \
    --to=yutingtseng@google.com \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.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