From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752507AbdBCHP7 (ORCPT ); Fri, 3 Feb 2017 02:15:59 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:33704 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751585AbdBCHP6 (ORCPT ); Fri, 3 Feb 2017 02:15:58 -0500 Date: Fri, 3 Feb 2017 08:16:01 +0100 From: Greg Kroah-Hartman To: John Stultz Cc: Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Linux Kernel Mailing List , Martijn Coenen Subject: Re: [PATCH 00/10] android: binder: support for domains and scatter-gather. Message-ID: <20170203071601.GA25580@kroah.com> References: <1477315238-104062-1-git-send-email-maco@android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 02, 2017 at 08:56:04PM -0800, John Stultz wrote: > On Mon, Oct 24, 2016 at 6:20 AM, Martijn Coenen wrote: > > Android userspace will start using binder IPC for communication with HAL > > modules. To clearly separate this IPC domain from the existing framework > > IPC domain, this patch series adds support for multiple "binder domains". > > This is implemented by each domain having its own binder context manager, > > and then having a separate device node per domain. > > > > The other change introduced by this series is scatter-gather; currently > > all objects passed through binder IPC must be serialized in userspace, with > > with the exception of binder objects and file descriptors. By adding scatter- > > gather support for memory buffers, we can avoid the serialization copy, > > thereby increasing performance for larger transaction sizes. > > > > The two patches from Arve are security patches that we've already applied > > in android-common. I included them in front of the series because my changes > > touch quite some of that code. > > Hey Greg, > Curious what the status of these patches are? Did you have any > outstanding objection, or were you just waiting for them to be resent? > > AOSP is now making use of this feature, so mainline kernels have > trouble booting w/o it, so it would be good to get merged. :) The patches that ended up in AOSP are a bit different from this series from what I remember, which is why I didn't end up applying this series at the time (it needed more work.) If you could dig up the latest versions, I'll be glad to review/merge them as well. There's also the 'hwbinder' work that should be in AOSP also, that should get merged too. thanks, greg k-h