From: John Stultz <john.stultz@linaro.org>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Colin Cross <ccross@android.com>,
Serban Constantinescu <serban.constantinescu@arm.com>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH 2/3] staging: binder: Support concurrent 32 bit and 64 bit processes.
Date: Fri, 21 Feb 2014 13:29:55 -0800 [thread overview]
Message-ID: <5307C553.9040504@linaro.org> (raw)
In-Reply-To: <CAMP5Xgf1cMUEk5Z3KQvnUNTzvo12URYX_w4m+SyH8WEF=1kKhg@mail.gmail.com>
On 02/21/2014 12:59 PM, Arve Hjønnevåg wrote:
> On Fri, Feb 21, 2014 at 12:43 PM, John Stultz <john.stultz@linaro.org> wrote:
>> From: Arve Hjønnevåg <arve@android.com>
>>
>> For 64bit systems we want to use the same binder interface for 32bit and
>> 64bit processes. Thus the size and the layout of the structures passed
>> between the kernel and the userspace has to be the same for both 32 and
>> 64bit processes.
>>
>> This change replaces all the uses of void* and size_t with
>> binder_uintptr_t and binder_size_t. These are then typedefed to specific
>> sizes depending on the use of the interface, as follows:
>> * __u32 - on legacy 32bit only userspace
>> * __u64 - on mixed 32/64bit userspace where all processes use the same
>> interface.
>>
>> This change also increments the BINDER_CURRENT_PROTOCOL_VERSION to 8 and
>> hooks the compat_ioctl entry for the mixed 32/64bit Android userspace.
>>
> It only increments the version to 8 if the old 32 bit interface is not selected.
>
>> This patch also provides a CONFIG_ANDROID_BINDER_IPC_32BIT option for
>> compatability, which if set which enables the old protocol on 32 bit
>> systems.
Ok. I thought that point was covered by the detail on
CONFIG_ANDROID_BINDER_IPC_32BIT, but maybe its not explicit enough.
Would you be ok with:
This change also increments the BINDER_CURRENT_PROTOCOL_VERSION to 8 and
hooks the compat_ioctl entry for the mixed 32/64bit Android userspace.
This patch also provides a CONFIG_ANDROID_BINDER_IPC_32BIT option for
compatability, which if set which enables the old protocol, setting
BINDER_CURRENT_PROTOCOL_VERSION to 7, on 32 bit systems.
?
thanks
-john
next prev parent reply other threads:[~2014-02-21 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 20:43 [PATCH 0/3] Binder ABI updates for 64bit systems for staging-next John Stultz
2014-02-21 20:43 ` [PATCH 1/3] staging: binder: Fix ABI for 64bit Android John Stultz
2014-02-21 20:43 ` [PATCH 2/3] staging: binder: Support concurrent 32 bit and 64 bit processes John Stultz
2014-02-21 20:59 ` Arve Hjønnevåg
2014-02-21 21:29 ` John Stultz [this message]
2014-02-21 21:56 ` Arve Hjønnevåg
2014-02-21 22:04 ` John Stultz
2014-02-21 22:10 ` Arve Hjønnevåg
2014-02-21 22:35 ` John Stultz
2014-02-21 20:43 ` [PATCH 3/3] staging: binder: Improve Kconfig entry for ANDROID_BINDER_IPC_32BIT John Stultz
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=5307C553.9040504@linaro.org \
--to=john.stultz@linaro.org \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serban.constantinescu@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.