1. 所在位置
  2. 首页
  3. 经验笔记
  4. 正文

Android系统进程间通信（IPC）机制Binder中的Server启动过程源代码分析

        在前面一篇文章Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路中，介绍了在Android系统中Binder进程间通信机制中的Server角色是如何获得Service Manager远程接口的，即defaultServiceManager函数的实现。Server获得了Service Manager远程接口之后，就要把自己的Service添加到Service Manager中去，然后把自己启动起来，等待Client的请求。本文将通过分析源代码了解Server的启动过程是怎么样的。

        本文通过一个具体的例子来说明Binder机制中Server的启动过程。我们知道，在Android系统中，提供了多媒体播放的功能，这个功能是以服务的形式来提供的。这里，我们就通过分析MediaPlayerService的实现来了解Media Server的启动过程。

        首先，看一下MediaPlayerService的类图，以便我们理解下面要描述的内容。

        我们将要介绍的主角MediaPlayerService继承于BnMediaPlayerService类，熟悉Binder机制的同学应该知道BnMediaPlayerService是一个Binder Native类，用来处理Client请求的。BnMediaPlayerService继承于BnInterface<IMediaPlayerService>类，BnInterface是一个模板类，它定义在frameworks/base/include/binder/IInterface.h文件中：

template<typename INTERFACE> 
class BnInterface : public INTERFACE, public BBinder 
{ 
public: 
 virtual sp<IInterface>  queryLocalInterface(const String16& _descriptor); 
 virtual const String16&  getInterfaceDescriptor() const; 
 
protected: 
 virtual IBinder*   onAsBinder(); 
};

       这里可以看出，BnMediaPlayerService实际是继承了IMediaPlayerService和BBinder类。IMediaPlayerService和BBinder类又分别继承了IInterface和IBinder类，IInterface和IBinder类又同时继承了RefBase类。

       实际上，BnMediaPlayerService并不是直接接收到Client处发送过来的请求，而是使用了IPCThreadState接收Client处发送过来的请求，而IPCThreadState又借助了ProcessState类来与Binder驱动程序交互。有关IPCThreadState和ProcessState的关系，可以参考上一篇文章Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路，接下来也会有相应的描述。IPCThreadState接收到了Client处的请求后，就会调用BBinder类的transact函数，并传入相关参数，BBinder类的transact函数最终调用BnMediaPlayerService类的onTransact函数，于是，就开始真正地处理Client的请求了。

      了解了MediaPlayerService类结构之后，就要开始进入到本文的主题了。

      首先，看看MediaPlayerService是如何启动的。启动MediaPlayerService的代码位于frameworks/base/media/mediaserver/main_mediaserver.cpp文件中：

int main(int argc, char** argv) 
{ 
 sp<ProcessState> proc(ProcessState::self()); 
 sp<IServiceManager> sm = defaultServiceManager(); 
 LOGI("ServiceManager: %p", sm.get()); 
 AudioFlinger::instantiate(); 
 MediaPlayerService::instantiate(); 
 CameraService::instantiate(); 
 AudioPolicyService::instantiate(); 
 ProcessState::self()->startThreadPool(); 
 IPCThreadState::self()->joinThreadPool(); 
}

       这里我们不关注AudioFlinger和CameraService相关的代码。
       先看下面这句代码：

                       sp<ProcessState> proc(ProcessState::self());  

       这句代码的作用是通过ProcessState::self()调用创建一个ProcessState实例。ProcessState::self()是ProcessState类的一个静态成员变量，定义在frameworks/base/libs/binder/ProcessState.cpp文件中：

sp<ProcessState> ProcessState::self() 
{ 
 if (gProcess != NULL) return gProcess; 
  
 AutoMutex _l(gProcessMutex); 
 if (gProcess == NULL) gProcess = new ProcessState; 
 return gProcess; 
}

       这里可以看出，这个函数作用是返回一个全局唯一的ProcessState实例gProcess。全局唯一实例变量gProcess定义在frameworks/base/libs/binder/Static.cpp文件中：

                        Mutex gProcessMutex; 
                        sp<ProcessState> gProcess;  

       再来看ProcessState的构造函数：

ProcessState::ProcessState() 
 : mDriverFD(open_driver()) 
 , mVMStart(MAP_FAILED) 
 , mManagesContexts(false) 
 , mBinderContextCheckFunc(NULL) 
 , mBinderContextUserData(NULL) 
 , mThreadPoolStarted(false) 
 , mThreadPoolSeq(1) 
{ 
 if (mDriverFD >= 0) { 
  // XXX Ideally, there should be a specific define for whether we 
  // have mmap (or whether we could possibly have the kernel module 
  // availabla). 
#if !defined(HAVE_WIN32_IPC) 
  // mmap the binder, providing a chunk of virtual address space to receive transactions. 
  mVMStart = mmap(0, BINDER_VM_SIZE, PROT_READ, MAP_PRIVATE | MAP_NORESERVE, mDriverFD, 0); 
  if (mVMStart == MAP_FAILED) { 
   // *sigh* 
   LOGE("Using /dev/binder failed: unable to mmap transaction memory.\n"); 
   close(mDriverFD); 
   mDriverFD = -1; 
  } 
#else 
  mDriverFD = -1; 
#endif 
 } 
 if (mDriverFD < 0) { 
  // Need to run without the driver, starting our own thread pool. 
 } 
}

        这个函数有两个关键地方，一是通过open_driver函数打开Binder设备文件/dev/binder，并将打开设备文件描述符保存在成员变量mDriverFD中；二是通过mmap来把设备文件/dev/binder映射到内存中。

        先看open_driver函数的实现，这个函数同样位于frameworks/base/libs/binder/ProcessState.cpp文件中：

static int open_driver() 
{ 
 if (gSingleProcess) { 
  return -1; 
 } 
 
 int fd = open("/dev/binder", O_RDWR); 
 if (fd >= 0) { 
  fcntl(fd, F_SETFD, FD_CLOEXEC); 
  int vers; 
#if defined(HAVE_ANDROID_OS) 
  status_t result = ioctl(fd, BINDER_VERSION, &vers); 
#else 
  status_t result = -1; 
  errno = EPERM; 
#endif 
  if (result == -1) { 
   LOGE("Binder ioctl to obtain version failed: %s", strerror(errno)); 
   close(fd); 
   fd = -1; 
  } 
  if (result != 0 || vers != BINDER_CURRENT_PROTOCOL_VERSION) { 
   LOGE("Binder driver protocol does not match user space protocol!"); 
   close(fd); 
   fd = -1; 
  } 
#if defined(HAVE_ANDROID_OS) 
  size_t maxThreads = 15; 
  result = ioctl(fd, BINDER_SET_MAX_THREADS, &maxThreads); 
  if (result == -1) { 
   LOGE("Binder ioctl to set max threads failed: %s", strerror(errno)); 
  } 
#endif 
   
 } else { 
  LOGW("Opening '/dev/binder' failed: %s\n", strerror(errno)); 
 } 
 return fd; 
}

        这个函数的作用主要是通过open文件操作函数来打开/dev/binder设备文件，然后再调用ioctl文件控制函数来分别执行BINDER_VERSION和BINDER_SET_MAX_THREADS两个命令来和Binder驱动程序进行交互，前者用于获得当前Binder驱动程序的版本号，后者用于通知Binder驱动程序，MediaPlayerService最多可同时启动15个线程来处理Client端的请求。

        open在Binder驱动程序中的具体实现，请参考前面一篇文章浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路，这里不再重复描述。打开/dev/binder设备文件后，Binder驱动程序就为MediaPlayerService进程创建了一个struct binder_proc结构体实例来维护MediaPlayerService进程上下文相关信息。

        我们来看一下ioctl文件操作函数执行BINDER_VERSION命令的过程：

                        status_t result = ioctl(fd, BINDER_VERSION, &vers);  

        这个函数调用最终进入到Binder驱动程序的binder_ioctl函数中，我们只关注BINDER_VERSION相关的部分逻辑：

static long binder_ioctl(struct file *filp, unsigned int cmd, unsigned long arg) 
{ 
 int ret; 
 struct binder_proc *proc = filp->private_data; 
 struct binder_thread *thread; 
 unsigned int size = _IOC_SIZE(cmd); 
 void __user *ubuf = (void __user *)arg; 
 
 /*printk(KERN_INFO "binder_ioctl: %d:%d %x %lx\n", proc->pid, current->pid, cmd, arg);*/ 
 
 ret = wait_event_interruptible(binder_user_error_wait, binder_stop_on_user_error < 2); 
 if (ret) 
  return ret; 
 
 mutex_lock(&binder_lock); 
 thread = binder_get_thread(proc); 
 if (thread == NULL) { 
  ret = -ENOMEM; 
  goto err; 
 } 
 
 switch (cmd) { 
 ...... 
 case BINDER_VERSION: 
  if (size != sizeof(struct binder_version)) { 
   ret = -EINVAL; 
   goto err; 
  } 
  if (put_user(BINDER_CURRENT_PROTOCOL_VERSION, &((struct binder_version *)ubuf)->protocol_version)) { 
   ret = -EINVAL; 
   goto err; 
  } 
  break; 
 ...... 
 } 
 ret = 0; 
err: 
  ...... 
 return ret; 
}

        很简单，只是将BINDER_CURRENT_PROTOCOL_VERSION写入到传入的参数arg指向的用户缓冲区中去就返回了。BINDER_CURRENT_PROTOCOL_VERSION是一个宏，定义在kernel/common/drivers/staging/android/binder.h文件中：

                     /* This is the current protocol version. */ 
             #define BINDER_CURRENT_PROTOCOL_VERSION 7  

       这里为什么要把ubuf转换成struct binder_version之后，再通过其protocol_version成员变量再来写入呢，转了一圈，最终内容还是写入到ubuf中。我们看一下struct binder_version的定义就会明白，同样是在kernel/common/drivers/staging/android/binder.h文件中：

/* Use with BINDER_VERSION, driver fills in fields. */ 
struct binder_version { 
 /* driver protocol version -- increment with incompatible change */ 
 signed long protocol_version; 
};

         从注释中可以看出来，这里是考虑到兼容性，因为以后很有可能不是用signed long来表示版本号。

        这里有一个重要的地方要注意的是，由于这里是打开设备文件/dev/binder之后，第一次进入到binder_ioctl函数，因此，这里调用binder_get_thread的时候，就会为当前线程创建一个struct binder_thread结构体变量来维护线程上下文信息，具体可以参考浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路一文。

        接着我们再来看一下ioctl文件操作函数执行BINDER_SET_MAX_THREADS命令的过程：

                   result = ioctl(fd, BINDER_SET_MAX_THREADS, &maxThreads);  

        这个函数调用最终进入到Binder驱动程序的binder_ioctl函数中，我们只关注BINDER_SET_MAX_THREADS相关的部分逻辑：

static long binder_ioctl(struct file *filp, unsigned int cmd, unsigned long arg) 
{ 
 int ret; 
 struct binder_proc *proc = filp->private_data; 
 struct binder_thread *thread; 
 unsigned int size = _IOC_SIZE(cmd); 
 void __user *ubuf = (void __user *)arg; 
 
 /*printk(KERN_INFO "binder_ioctl: %d:%d %x %lx\n", proc->pid, current->pid, cmd, arg);*/ 
 
 ret = wait_event_interruptible(binder_user_error_wait, binder_stop_on_user_error < 2); 
 if (ret) 
  return ret; 
 
 mutex_lock(&binder_lock); 
 thread = binder_get_thread(proc); 
 if (thread == NULL) { 
  ret = -ENOMEM; 
  goto err; 
 } 
 
 switch (cmd) { 
 ...... 
 case BINDER_SET_MAX_THREADS: 
  if (copy_from_user(&proc->max_threads, ubuf, sizeof(proc->max_threads))) { 
   ret = -EINVAL; 
   goto err; 
  } 
  break; 
 ...... 
 } 
 ret = 0; 
err: 
 ...... 
 return ret; 
}

        这里实现也是非常简单，只是简单地把用户传进来的参数保存在proc->max_threads中就完毕了。注意，这里再调用binder_get_thread函数的时候，就可以在proc->threads中找到当前线程对应的struct binder_thread结构了，因为前面已经创建好并保存在proc->threads红黑树中。

        回到ProcessState的构造函数中，这里还通过mmap函数来把设备文件/dev/binder映射到内存中，这个函数在浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路一文也已经有详细介绍，这里不再重复描述。宏BINDER_VM_SIZE就定义在ProcessState.cpp文件中：

             #define BINDER_VM_SIZE ((1*1024*1024) - (4096 *2))  

        mmap函数调用完成之后，Binder驱动程序就为当前进程预留了BINDER_VM_SIZE大小的内存空间了。

        这样，ProcessState全局唯一变量gProcess就创建完毕了，回到frameworks/base/media/mediaserver/main_mediaserver.cpp文件中的main函数，下一步是调用defaultServiceManager函数来获得Service Manager的远程接口，这个已经在上一篇文章浅谈Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路有详细描述，读者可以回过头去参考一下。

        再接下来，就进入到MediaPlayerService::instantiate函数把MediaPlayerService添加到Service Manger中去了。这个函数定义在frameworks/base/media/libmediaplayerservice/MediaPlayerService.cpp文件中：

void MediaPlayerService::instantiate() { 
 defaultServiceManager()->addService( 
   String16("media.player"), new MediaPlayerService()); 
}

        我们重点看一下IServiceManger::addService的过程，这有助于我们加深对Binder机制的理解。

        在上一篇文章浅谈Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路中说到，defaultServiceManager返回的实际是一个BpServiceManger类实例，因此，我们看一下BpServiceManger::addService的实现，这个函数实现在frameworks/base/libs/binder/IServiceManager.cpp文件中：

class BpServiceManager : public BpInterface<IServiceManager> 
{ 
public: 
 BpServiceManager(const sp<IBinder>& impl) 
  : BpInterface<IServiceManager>(impl) 
 { 
 } 
 
 ...... 
 
 virtual status_t addService(const String16& name, const sp<IBinder>& service) 
 { 
  Parcel data, reply; 
  data.writeInterfaceToken(IServiceManager::getInterfaceDescriptor()); 
  data.writeString16(name); 
  data.writeStrongBinder(service); 
  status_t err = remote()->transact(ADD_SERVICE_TRANSACTION, data, &reply); 
  return err == NO_ERROR ? reply.readExceptionCode() 
 } 
 
 ...... 
 
};

         这里的Parcel类是用来于序列化进程间通信数据用的。
         先来看这一句的调用：

           data.writeInterfaceToken(IServiceManager::getInterfaceDescriptor());  

         IServiceManager::getInterfaceDescriptor()返回来的是一个字符串，即"android.os.IServiceManager"，具体可以参考IServiceManger的实现。我们看一下Parcel::writeInterfaceToken的实现，位于frameworks/base/libs/binder/Parcel.cpp文件中：

// Write RPC headers. (previously just the interface token) 
status_t Parcel::writeInterfaceToken(const String16& interface) 
{ 
 writeInt32(IPCThreadState::self()->getStrictModePolicy() | 
    STRICT_MODE_PENALTY_GATHER); 
 // currently the interface identification token is just its name as a string 
 return writeString16(interface); 
}

         它的作用是写入一个整数和一个字符串到Parcel中去。

         再来看下面的调用：

                    data.writeString16(name);  

        这里又是写入一个字符串到Parcel中去，这里的name即是上面传进来的“media.player”字符串。
        往下看：

               data.writeStrongBinder(service);  

        这里定入一个Binder对象到Parcel去。我们重点看一下这个函数的实现，因为它涉及到进程间传输Binder实体的问题，比较复杂，需要重点关注，同时，也是理解Binder机制的一个重点所在。注意，这里的service参数是一个MediaPlayerService对象。

status_t Parcel::writeStrongBinder(const sp<IBinder>& val) 
{ 
 return flatten_binder(ProcessState::self(), val, this); 
}

        看到flatten_binder函数，是不是似曾相识的感觉？我们在前面一篇文章浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路中，曾经提到在Binder驱动程序中，使用struct flat_binder_object来表示传输中的一个binder对象，它的定义如下所示：

/* 
 * This is the flattened representation of a Binder object for transfer 
 * between processes. The 'offsets' supplied as part of a binder transaction 
 * contains offsets into the data where these structures occur. The Binder 
 * driver takes care of re-writing the structure type and data as it moves 
 * between processes. 
 */ 
struct flat_binder_object { 
 /* 8 bytes for large_flat_header. */ 
 unsigned long  type; 
 unsigned long  flags; 
 
 /* 8 bytes of data. */ 
 union { 
  void  *binder; /* local object */ 
  signed long handle;  /* remote object */ 
 }; 
 
 /* extra data associated with local object */ 
 void   *cookie; 
};

        各个成员变量的含义请参考资料Android Binder设计与实现。
        我们进入到flatten_binder函数看看：

status_t flatten_binder(const sp<ProcessState>& proc, 
 const sp<IBinder>& binder, Parcel* out) 
{ 
 flat_binder_object obj; 
  
 obj.flags = 0x7f | FLAT_BINDER_FLAG_ACCEPTS_FDS; 
 if (binder != NULL) { 
  IBinder *local = binder->localBinder(); 
  if (!local) { 
   BpBinder *proxy = binder->remoteBinder(); 
   if (proxy == NULL) { 
    LOGE("null proxy"); 
   } 
   const int32_t handle = proxy ? proxy->handle() : 0; 
   obj.type = BINDER_TYPE_HANDLE; 
   obj.handle = handle; 
   obj.cookie = NULL; 
  } else { 
   obj.type = BINDER_TYPE_BINDER; 
   obj.binder = local->getWeakRefs(); 
   obj.cookie = local; 
  } 
 } else { 
  obj.type = BINDER_TYPE_BINDER; 
  obj.binder = NULL; 
  obj.cookie = NULL; 
 } 
  
 return finish_flatten_binder(binder, obj, out); 
}

        首先是初始化flat_binder_object的flags域： 

               obj.flags = 0x7f | FLAT_BINDER_FLAG_ACCEPTS_FDS;  

        0x7f表示处理本Binder实体请求数据包的线程的最低优先级，FLAT_BINDER_FLAG_ACCEPTS_FDS表示这个Binder实体可以接受文件描述符，Binder实体在收到文件描述符时，就会在本进程中打开这个文件。

       传进来的binder即为MediaPlayerService::instantiate函数中new出来的MediaPlayerService实例，因此，不为空。又由于MediaPlayerService继承自BBinder类，它是一个本地Binder实体，因此binder->localBinder返回一个BBinder指针，而且肯定不为空，于是执行下面语句：

obj.type = BINDER_TYPE_BINDER; 
obj.binder = local->getWeakRefs(); 
obj.cookie = local;

        设置了flat_binder_obj的其他成员变量，注意，指向这个Binder实体地址的指针local保存在flat_binder_obj的成员变量cookie中。

        函数调用finish_flatten_binder来将这个flat_binder_obj写入到Parcel中去：

inline static status_t finish_flatten_binder( 
 const sp<IBinder>& binder, const flat_binder_object& flat, Parcel* out) 
{ 
 return out->writeObject(flat, false); 
}

       Parcel::writeObject的实现如下：

status_t Parcel::writeObject(const flat_binder_object& val, bool nullMetaData) 
{ 
 const bool enoughData = (mDataPos+sizeof(val)) <= mDataCapacity; 
 const bool enoughObjects = mObjectsSize < mObjectsCapacity; 
 if (enoughData && enoughObjects) { 
restart_write: 
  *reinterpret_cast<flat_binder_object*>(mData+mDataPos) = val; 
   
  // Need to write meta-data? 
  if (nullMetaData || val.binder != NULL) { 
   mObjects[mObjectsSize] = mDataPos; 
   acquire_object(ProcessState::self(), val, this); 
   mObjectsSize++; 
  } 
   
  // remember if it's a file descriptor 
  if (val.type == BINDER_TYPE_FD) { 
   mHasFds = mFdsKnown = true; 
  } 
 
  return finishWrite(sizeof(flat_binder_object)); 
 } 
 
 if (!enoughData) { 
  const status_t err = growData(sizeof(val)); 
  if (err != NO_ERROR) return err; 
 } 
 if (!enoughObjects) { 
  size_t newSize = ((mObjectsSize+2)*3)/2; 
  size_t* objects = (size_t*)realloc(mObjects, newSize*sizeof(size_t)); 
  if (objects == NULL) return NO_MEMORY; 
  mObjects = objects; 
  mObjectsCapacity = newSize; 
 } 
  
 goto restart_write; 
}

        这里除了把flat_binder_obj写到Parcel里面之内，还要记录这个flat_binder_obj在Parcel里面的偏移位置：

                    mObjects[mObjectsSize] = mDataPos;  

       这里因为，如果进程间传输的数据间带有Binder对象的时候，Binder驱动程序需要作进一步的处理，以维护各个Binder实体的一致性，下面我们将会看到Binder驱动程序是怎么处理这些Binder对象的。

       再回到BpServiceManager::addService函数中，调用下面语句：

      status_t err = remote()->transact(ADD_SERVICE_TRANSACTION, data, &reply);  

       回到浅谈Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路一文中的类图中去看一下，这里的remote成员函数来自于BpRefBase类，它返回一个BpBinder指针。因此，我们继续进入到BpBinder::transact函数中去看看：

status_t BpBinder::transact( 
 uint32_t code, const Parcel& data, Parcel* reply, uint32_t flags) 
{ 
 // Once a binder has died, it will never come back to life. 
 if (mAlive) { 
  status_t status = IPCThreadState::self()->transact( 
   mHandle, code, data, reply, flags); 
  if (status == DEAD_OBJECT) mAlive = 0; 
  return status; 
 } 
 
 return DEAD_OBJECT; 
}

       这里又调用了IPCThreadState::transact进执行实际的操作。注意，这里的mHandle为0，code为ADD_SERVICE_TRANSACTION。ADD_SERVICE_TRANSACTION是上面以参数形式传进来的，那mHandle为什么是0呢？因为这里表示的是Service Manager远程接口，它的句柄值一定是0，具体请参考浅谈Android系统进程间通信（IPC）机制Binder中的Server和Client获得Service Manager接口之路一文。

       再进入到IPCThreadState::transact函数，看看做了些什么事情：

status_t IPCThreadState::transact(int32_t handle, 
         uint32_t code, const Parcel& data, 
         Parcel* reply, uint32_t flags) 
{ 
 status_t err = data.errorCheck(); 
 
 flags |= TF_ACCEPT_FDS; 
 
 IF_LOG_TRANSACTIONS() { 
  TextOutput::Bundle _b(alog); 
  alog << "BC_TRANSACTION thr " << (void*)pthread_self() << " / hand " 
   << handle << " / code " << TypeCode(code) << ": " 
   << indent << data << dedent << endl; 
 } 
  
 if (err == NO_ERROR) { 
  LOG_ONEWAY(">>>> SEND from pid %d uid %d %s", getpid(), getuid(), 
   (flags & TF_ONE_WAY) == 0 ? "READ REPLY" : "ONE WAY"); 
  err = writeTransactionData(BC_TRANSACTION, flags, handle, code, data, NULL); 
 } 
  
 if (err != NO_ERROR) { 
  if (reply) reply->setError(err); 
  return (mLastError = err); 
 } 
  
 if ((flags & TF_ONE_WAY) == 0) { 
  #if 0 
  if (code == 4) { // relayout 
   LOGI(">>>>>> CALLING transaction 4"); 
  } else { 
   LOGI(">>>>>> CALLING transaction %d", code); 
  } 
  #endif 
  if (reply) { 
   err = waitForResponse(reply); 
  } else { 
   Parcel fakeReply; 
   err = waitForResponse(&fakeReply); 
  } 
  #if 0 
  if (code == 4) { // relayout 
   LOGI("<<<<<< RETURNING transaction 4"); 
  } else { 
   LOGI("<<<<<< RETURNING transaction %d", code); 
  } 
  #endif 
   
  IF_LOG_TRANSACTIONS() { 
   TextOutput::Bundle _b(alog); 
   alog << "BR_REPLY thr " << (void*)pthread_self() << " / hand " 
    << handle << ": "; 
   if (reply) alog << indent << *reply << dedent << endl; 
   else alog << "(none requested)" << endl; 
  } 
 } else { 
  err = waitForResponse(NULL, NULL); 
 } 
  
 return err; 
}

        IPCThreadState::transact函数的参数flags是一个默认值为0的参数，上面没有传相应的实参进来，因此，这里就为0。

        函数首先调用writeTransactionData函数准备好一个struct binder_transaction_data结构体变量，这个是等一下要传输给Binder驱动程序的。struct binder_transaction_data的定义我们在浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路一文中有详细描述，读者不妨回过去读一下。这里为了方便描述，将struct binder_transaction_data的定义再次列出来：

struct binder_transaction_data { 
 /* The first two are only used for bcTRANSACTION and brTRANSACTION, 
  * identifying the target and contents of the transaction. 
  */ 
 union { 
  size_t handle; /* target descriptor of command transaction */ 
  void *ptr; /* target descriptor of return transaction */ 
 } target; 
 void  *cookie; /* target object cookie */ 
 unsigned int code;  /* transaction command */ 
 
 /* General information about the transaction. */ 
 unsigned int flags; 
 pid_t  sender_pid; 
 uid_t  sender_euid; 
 size_t  data_size; /* number of bytes of data */ 
 size_t  offsets_size; /* number of bytes of offsets */ 
 
 /* If this transaction is inline, the data immediately 
  * follows here; otherwise, it ends with a pointer to 
  * the data buffer. 
  */ 
 union { 
  struct { 
   /* transaction data */ 
   const void *buffer; 
   /* offsets from buffer to flat_binder_object structs */ 
   const void *offsets; 
  } ptr; 
  uint8_t buf[8]; 
 } data; 
};

         writeTransactionData函数的实现如下：

status_t IPCThreadState::writeTransactionData(int32_t cmd, uint32_t binderFlags, 
 int32_t handle, uint32_t code, const Parcel& data, status_t* statusBuffer) 
{ 
 binder_transaction_data tr; 
 
 tr.target.handle = handle; 
 tr.code = code; 
 tr.flags = binderFlags; 
  
 const status_t err = data.errorCheck(); 
 if (err == NO_ERROR) { 
  tr.data_size = data.ipcDataSize(); 
  tr.data.ptr.buffer = data.ipcData(); 
  tr.offsets_size = data.ipcObjectsCount()*sizeof(size_t); 
  tr.data.ptr.offsets = data.ipcObjects(); 
 } else if (statusBuffer) { 
  tr.flags |= TF_STATUS_CODE; 
  *statusBuffer = err; 
  tr.data_size = sizeof(status_t); 
  tr.data.ptr.buffer = statusBuffer; 
  tr.offsets_size = 0; 
  tr.data.ptr.offsets = NULL; 
 } else { 
  return (mLastError = err); 
 } 
  
 mOut.writeInt32(cmd); 
 mOut.write(&tr, sizeof(tr)); 
  
 return NO_ERROR; 
}

  注意，这里的cmd为BC_TRANSACTION。 这个函数很简单，在这个场景下，就是执行下面语句来初始化本地变量tr：

tr.data_size = data.ipcDataSize(); 
tr.data.ptr.buffer = data.ipcData(); 
tr.offsets_size = data.ipcObjectsCount()*sizeof(size_t); 
tr.data.ptr.offsets = data.ipcObjects();

       回忆一下上面的内容，写入到tr.data.ptr.buffer的内容相当于下面的内容：

writeInt32(IPCThreadState::self()->getStrictModePolicy() | 
    STRICT_MODE_PENALTY_GATHER); 
writeString16("android.os.IServiceManager"); 
writeString16("media.player"); 
writeStrongBinder(new MediaPlayerService());

      其中包含了一个Binder实体MediaPlayerService，因此需要设置tr.offsets_size就为1，tr.data.ptr.offsets就指向了这个MediaPlayerService的地址在tr.data.ptr.buffer中的偏移量。最后，将tr的内容保存在IPCThreadState的成员变量mOut中。

       回到IPCThreadState::transact函数中，接下去看，(flags & TF_ONE_WAY) == 0为true，并且reply不为空，所以最终进入到waitForResponse(reply)这条路径来。我们看一下waitForResponse函数的实现：

status_t IPCThreadState::waitForResponse(Parcel *reply, status_t *acquireResult) 
{ 
 int32_t cmd; 
 int32_t err; 
 
 while (1) { 
  if ((err=talkWithDriver()) < NO_ERROR) break; 
  err = mIn.errorCheck(); 
  if (err < NO_ERROR) break; 
  if (mIn.dataAvail() == 0) continue; 
   
  cmd = mIn.readInt32(); 
   
  IF_LOG_COMMANDS() { 
   alog << "Processing waitForResponse Command: " 
    << getReturnString(cmd) << endl; 
  } 
 
  switch (cmd) { 
  case BR_TRANSACTION_COMPLETE: 
   if (!reply && !acquireResult) goto finish; 
   break; 
   
  case BR_DEAD_REPLY: 
   err = DEAD_OBJECT; 
   goto finish; 
 
  case BR_FAILED_REPLY: 
   err = FAILED_TRANSACTION; 
   goto finish; 
   
  case BR_ACQUIRE_RESULT: 
   { 
    LOG_ASSERT(acquireResult != NULL, "Unexpected brACQUIRE_RESULT"); 
    const int32_t result = mIn.readInt32(); 
    if (!acquireResult) continue; 
    *acquireResult = result ? NO_ERROR : INVALID_OPERATION; 
   } 
   goto finish; 
   
  case BR_REPLY: 
   { 
    binder_transaction_data tr; 
    err = mIn.read(&tr, sizeof(tr)); 
    LOG_ASSERT(err == NO_ERROR, "Not enough command data for brREPLY"); 
    if (err != NO_ERROR) goto finish; 
 
    if (reply) { 
     if ((tr.flags & TF_STATUS_CODE) == 0) { 
      reply->ipcSetDataReference( 
       reinterpret_cast<const uint8_t*>(tr.data.ptr.buffer), 
       tr.data_size, 
       reinterpret_cast<const size_t*>(tr.data.ptr.offsets), 
       tr.offsets_size/sizeof(size_t), 
       freeBuffer, this); 
     } else { 
      err = *static_cast<const status_t*>(tr.data.ptr.buffer); 
      freeBuffer(NULL, 
       reinterpret_cast<const uint8_t*>(tr.data.ptr.buffer), 
       tr.data_size, 
       reinterpret_cast<const size_t*>(tr.data.ptr.offsets), 
       tr.offsets_size/sizeof(size_t), this); 
     } 
    } else { 
     freeBuffer(NULL, 
      reinterpret_cast<const uint8_t*>(tr.data.ptr.buffer), 
      tr.data_size, 
      reinterpret_cast<const size_t*>(tr.data.ptr.offsets), 
      tr.offsets_size/sizeof(size_t), this); 
     continue; 
    } 
   } 
   goto finish; 
 
  default: 
   err = executeCommand(cmd); 
   if (err != NO_ERROR) goto finish; 
   break; 
  } 
 } 
 
finish: 
 if (err != NO_ERROR) { 
  if (acquireResult) *acquireResult = err; 
  if (reply) reply->setError(err); 
  mLastError = err; 
 } 
  
 return err; 
}

        这个函数虽然很长，但是主要调用了talkWithDriver函数来与Binder驱动程序进行交互：

status_t IPCThreadState::talkWithDriver(bool doReceive) 
{ 
 LOG_ASSERT(mProcess->mDriverFD >= 0, "Binder driver is not opened"); 
  
 binder_write_read bwr; 
  
 // Is the read buffer empty? 
 const bool needRead = mIn.dataPosition() >= mIn.dataSize(); 
  
 // We don't want to write anything if we are still reading 
 // from data left in the input buffer and the caller 
 // has requested to read the next data. 
 const size_t outAvail = (!doReceive || needRead) ? mOut.dataSize() : 0; 
  
 bwr.write_size = outAvail; 
 bwr.write_buffer = (long unsigned int)mOut.data(); 
 
 // This is what we'll read. 
 if (doReceive && needRead) { 
  bwr.read_size = mIn.dataCapacity(); 
  bwr.read_buffer = (long unsigned int)mIn.data(); 
 } else { 
  bwr.read_size = 0; 
 } 
  
 IF_LOG_COMMANDS() { 
  TextOutput::Bundle _b(alog); 
  if (outAvail != 0) { 
   alog << "Sending commands to driver: " << indent; 
   const void* cmds = (const void*)bwr.write_buffer; 
   const void* end = ((const uint8_t*)cmds)+bwr.write_size; 
   alog << HexDump(cmds, bwr.write_size) << endl; 
   while (cmds < end) cmds = printCommand(alog, cmds); 
   alog << dedent; 
  } 
  alog << "Size of receive buffer: " << bwr.read_size 
   << ", needRead: " << needRead << ", doReceive: " << doReceive << endl; 
 } 
  
 // Return immediately if there is nothing to do. 
 if ((bwr.write_size == 0) && (bwr.read_size == 0)) return NO_ERROR; 
  
 bwr.write_consumed = 0; 
 bwr.read_consumed = 0; 
 status_t err; 
 do { 
  IF_LOG_COMMANDS() { 
   alog << "About to read/write, write size = " << mOut.dataSize() << endl; 
  } 
#if defined(HAVE_ANDROID_OS) 
  if (ioctl(mProcess->mDriverFD, BINDER_WRITE_READ, &bwr) >= 0) 
   err = NO_ERROR; 
  else 
   err = -errno; 
#else 
  err = INVALID_OPERATION; 
#endif 
  IF_LOG_COMMANDS() { 
   alog << "Finished read/write, write size = " << mOut.dataSize() << endl; 
  } 
 } while (err == -EINTR); 
  
 IF_LOG_COMMANDS() { 
  alog << "Our err: " << (void*)err << ", write consumed: " 
   << bwr.write_consumed << " (of " << mOut.dataSize() 
   << "), read consumed: " << bwr.read_consumed << endl; 
 } 
 
 if (err >= NO_ERROR) { 
  if (bwr.write_consumed > 0) { 
   if (bwr.write_consumed < (ssize_t)mOut.dataSize()) 
    mOut.remove(0, bwr.write_consumed); 
   else 
    mOut.setDataSize(0); 
  } 
  if (bwr.read_consumed > 0) { 
   mIn.setDataSize(bwr.read_consumed); 
   mIn.setDataPosition(0); 
  } 
  IF_LOG_COMMANDS() { 
   TextOutput::Bundle _b(alog); 
   alog << "Remaining data size: " << mOut.dataSize() << endl; 
   alog << "Received commands from driver: " << indent; 
   const void* cmds = mIn.data(); 
   const void* end = mIn.data() + mIn.dataSize(); 
   alog << HexDump(cmds, mIn.dataSize()) << endl; 
   while (cmds < end) cmds = printReturnCommand(alog, cmds); 
   alog << dedent; 
  } 
  return NO_ERROR; 
 } 
  
 return err; 
}

        这里doReceive和needRead均为1，有兴趣的读者可以自已分析一下。因此，这里告诉Binder驱动程序，先执行write操作，再执行read操作，下面我们将会看到。

        最后，通过ioctl(mProcess->mDriverFD, BINDER_WRITE_READ, &bwr)进行到Binder驱动程序的binder_ioctl函数，我们只关注cmd为BINDER_WRITE_READ的逻辑：

static long binder_ioctl(struct file *filp, unsigned int cmd, unsigned long arg) 
{ 
 int ret; 
 struct binder_proc *proc = filp->private_data; 
 struct binder_thread *thread; 
 unsigned int size = _IOC_SIZE(cmd); 
 void __user *ubuf = (void __user *)arg; 
 
 /*printk(KERN_INFO "binder_ioctl: %d:%d %x %lx\n", proc->pid, current->pid, cmd, arg);*/ 
 
 ret = wait_event_interruptible(binder_user_error_wait, binder_stop_on_user_error < 2); 
 if (ret) 
  return ret; 
 
 mutex_lock(&binder_lock); 
 thread = binder_get_thread(proc); 
 if (thread == NULL) { 
  ret = -ENOMEM; 
  goto err; 
 } 
 
 switch (cmd) { 
 case BINDER_WRITE_READ: { 
  struct binder_write_read bwr; 
  if (size != sizeof(struct binder_write_read)) { 
   ret = -EINVAL; 
   goto err; 
  } 
  if (copy_from_user(&bwr, ubuf, sizeof(bwr))) { 
   ret = -EFAULT; 
   goto err; 
  } 
  if (binder_debug_mask & BINDER_DEBUG_READ_WRITE) 
   printk(KERN_INFO "binder: %d:%d write %ld at %08lx, read %ld at %08lx\n", 
   proc->pid, thread->pid, bwr.write_size, bwr.write_buffer, bwr.read_size, bwr.read_buffer); 
  if (bwr.write_size > 0) { 
   ret = binder_thread_write(proc, thread, (void __user *)bwr.write_buffer, bwr.write_size, &bwr.write_consumed); 
   if (ret < 0) { 
    bwr.read_consumed = 0; 
    if (copy_to_user(ubuf, &bwr, sizeof(bwr))) 
     ret = -EFAULT; 
    goto err; 
   } 
  } 
  if (bwr.read_size > 0) { 
   ret = binder_thread_read(proc, thread, (void __user *)bwr.read_buffer, bwr.read_size, &bwr.read_consumed, filp->f_flags & O_NONBLOCK); 
   if (!list_empty(&proc->todo)) 
    wake_up_interruptible(&proc->wait); 
   if (ret < 0) { 
    if (copy_to_user(ubuf, &bwr, sizeof(bwr))) 
     ret = -EFAULT; 
    goto err; 
   } 
  } 
  if (binder_debug_mask & BINDER_DEBUG_READ_WRITE) 
   printk(KERN_INFO "binder: %d:%d wrote %ld of %ld, read return %ld of %ld\n", 
   proc->pid, thread->pid, bwr.write_consumed, bwr.write_size, bwr.read_consumed, bwr.read_size); 
  if (copy_to_user(ubuf, &bwr, sizeof(bwr))) { 
   ret = -EFAULT; 
   goto err; 
  } 
  break; 
 } 
 ...... 
 } 
 ret = 0; 
err: 
 ...... 
 return ret; 
}

         函数首先是将用户传进来的参数拷贝到本地变量struct binder_write_read bwr中去。这里bwr.write_size > 0为true，因此，进入到binder_thread_write函数中，我们只关注BC_TRANSACTION部分的逻辑：

binder_thread_write(struct binder_proc *proc, struct binder_thread *thread, 
     void __user *buffer, int size, signed long *consumed) 
{ 
 uint32_t cmd; 
 void __user *ptr = buffer + *consumed; 
 void __user *end = buffer + size; 
 
 while (ptr < end && thread->return_error == BR_OK) { 
  if (get_user(cmd, (uint32_t __user *)ptr)) 
   return -EFAULT; 
  ptr += sizeof(uint32_t); 
  if (_IOC_NR(cmd) < ARRAY_SIZE(binder_stats.bc)) { 
   binder_stats.bc[_IOC_NR(cmd)]++; 
   proc->stats.bc[_IOC_NR(cmd)]++; 
   thread->stats.bc[_IOC_NR(cmd)]++; 
  } 
  switch (cmd) { 
   ..... 
  case BC_TRANSACTION: 
  case BC_REPLY: { 
   struct binder_transaction_data tr; 
 
   if (copy_from_user(&tr, ptr, sizeof(tr))) 
    return -EFAULT; 
   ptr += sizeof(tr); 
   binder_transaction(proc, thread, &tr, cmd == BC_REPLY); 
   break; 
  } 
  ...... 
  } 
  *consumed = ptr - buffer; 
 } 
 return 0; 
}

         首先将用户传进来的transact参数拷贝在本地变量struct binder_transaction_data tr中去，接着调用binder_transaction函数进一步处理，这里我们忽略掉无关代码：

static void 
binder_transaction(struct binder_proc *proc, struct binder_thread *thread, 
struct binder_transaction_data *tr, int reply) 
{ 
 struct binder_transaction *t; 
 struct binder_work *tcomplete; 
 size_t *offp, *off_end; 
 struct binder_proc *target_proc; 
 struct binder_thread *target_thread = NULL; 
 struct binder_node *target_node = NULL; 
 struct list_head *target_list; 
 wait_queue_head_t *target_wait; 
 struct binder_transaction *in_reply_to = NULL; 
 struct binder_transaction_log_entry *e; 
 uint32_t return_error; 
 
  ...... 
 
 if (reply) { 
   ...... 
 } else { 
  if (tr->target.handle) { 
   ...... 
  } else { 
   target_node = binder_context_mgr_node; 
   if (target_node == NULL) { 
    return_error = BR_DEAD_REPLY; 
    goto err_no_context_mgr_node; 
   } 
  } 
  ...... 
  target_proc = target_node->proc; 
  if (target_proc == NULL) { 
   return_error = BR_DEAD_REPLY; 
   goto err_dead_binder; 
  } 
  ...... 
 } 
 if (target_thread) { 
  ...... 
 } else { 
  target_list = &target_proc->todo; 
  target_wait = &target_proc->wait; 
 } 
  
 ...... 
 
 /* TODO: reuse incoming transaction for reply */ 
 t = kzalloc(sizeof(*t), GFP_KERNEL); 
 if (t == NULL) { 
  return_error = BR_FAILED_REPLY; 
  goto err_alloc_t_failed; 
 } 
 ...... 
 
 tcomplete = kzalloc(sizeof(*tcomplete), GFP_KERNEL); 
 if (tcomplete == NULL) { 
  return_error = BR_FAILED_REPLY; 
  goto err_alloc_tcomplete_failed; 
 } 
  
 ...... 
 
 if (!reply && !(tr->flags & TF_ONE_WAY)) 
  t->from = thread; 
 else 
  t->from = NULL; 
 t->sender_euid = proc->tsk->cred->euid; 
 t->to_proc = target_proc; 
 t->to_thread = target_thread; 
 t->code = tr->code; 
 t->flags = tr->flags; 
 t->priority = task_nice(current); 
 t->buffer = binder_alloc_buf(target_proc, tr->data_size, 
  tr->offsets_size, !reply && (t->flags & TF_ONE_WAY)); 
 if (t->buffer == NULL) { 
  return_error = BR_FAILED_REPLY; 
  goto err_binder_alloc_buf_failed; 
 } 
 t->buffer->allow_user_free = 0; 
 t->buffer->debug_id = t->debug_id; 
 t->buffer->transaction = t; 
 t->buffer->target_node = target_node; 
 if (target_node) 
  binder_inc_node(target_node, 1, 0, NULL); 
 
 offp = (size_t *)(t->buffer->data + ALIGN(tr->data_size, sizeof(void *))); 
 
 if (copy_from_user(t->buffer->data, tr->data.ptr.buffer, tr->data_size)) { 
  ...... 
  return_error = BR_FAILED_REPLY; 
  goto err_copy_data_failed; 
 } 
 if (copy_from_user(offp, tr->data.ptr.offsets, tr->offsets_size)) { 
  ...... 
  return_error = BR_FAILED_REPLY; 
  goto err_copy_data_failed; 
 } 
 ...... 
 
 off_end = (void *)offp + tr->offsets_size; 
 for (; offp < off_end; offp++) { 
  struct flat_binder_object *fp; 
  ...... 
  fp = (struct flat_binder_object *)(t->buffer->data + *offp); 
  switch (fp->type) { 
  case BINDER_TYPE_BINDER: 
  case BINDER_TYPE_WEAK_BINDER: { 
   struct binder_ref *ref; 
   struct binder_node *node = binder_get_node(proc, fp->binder); 
   if (node == NULL) { 
    node = binder_new_node(proc, fp->binder, fp->cookie); 
    if (node == NULL) { 
     return_error = BR_FAILED_REPLY; 
     goto err_binder_new_node_failed; 
    } 
    node->min_priority = fp->flags & FLAT_BINDER_FLAG_PRIORITY_MASK; 
    node->accept_fds = !!(fp->flags & FLAT_BINDER_FLAG_ACCEPTS_FDS); 
   } 
   if (fp->cookie != node->cookie) { 
    ...... 
    goto err_binder_get_ref_for_node_failed; 
   } 
   ref = binder_get_ref_for_node(target_proc, node); 
   if (ref == NULL) { 
    return_error = BR_FAILED_REPLY; 
    goto err_binder_get_ref_for_node_failed; 
   } 
   if (fp->type == BINDER_TYPE_BINDER) 
    fp->type = BINDER_TYPE_HANDLE; 
   else 
    fp->type = BINDER_TYPE_WEAK_HANDLE; 
   fp->handle = ref->desc; 
   binder_inc_ref(ref, fp->type == BINDER_TYPE_HANDLE, &thread->todo); 
   ...... 
        
  } break; 
  ...... 
  } 
 } 
 
 if (reply) { 
  ...... 
 } else if (!(t->flags & TF_ONE_WAY)) { 
  BUG_ON(t->buffer->async_transaction != 0); 
  t->need_reply = 1; 
  t->from_parent = thread->transaction_stack; 
  thread->transaction_stack = t; 
 } else { 
  ...... 
 } 
 t->work.type = BINDER_WORK_TRANSACTION; 
 list_add_tail(&t->work.entry, target_list); 
 tcomplete->type = BINDER_WORK_TRANSACTION_COMPLETE; 
 list_add_tail(&tcomplete->entry, &thread->todo); 
 if (target_wait) 
  wake_up_interruptible(target_wait); 
 return; 
 ...... 
}

       注意，这里传进来的参数reply为0，tr->target.handle也为0。因此，target_proc、target_thread、target_node、target_list和target_wait的值分别为：

target_node = binder_context_mgr_node; 
target_proc = target_node->proc; 
target_list = &target_proc->todo; 
target_wait = &target_proc->wait;

       接着，分配了一个待处理事务t和一个待完成工作项tcomplete，并执行初始化工作：

/* TODO: reuse incoming transaction for reply */ 
t = kzalloc(sizeof(*t), GFP_KERNEL); 
if (t == NULL) { 
 return_error = BR_FAILED_REPLY; 
 goto err_alloc_t_failed; 
} 
...... 
 
tcomplete = kzalloc(sizeof(*tcomplete), GFP_KERNEL); 
if (tcomplete == NULL) { 
 return_error = BR_FAILED_REPLY; 
 goto err_alloc_tcomplete_failed; 
} 
 
...... 
 
if (!reply && !(tr->flags & TF_ONE_WAY)) 
 t->from = thread; 
else 
 t->from = NULL; 
t->sender_euid = proc->tsk->cred->euid; 
t->to_proc = target_proc; 
t->to_thread = target_thread; 
t->code = tr->code; 
t->flags = tr->flags; 
t->priority = task_nice(current); 
t->buffer = binder_alloc_buf(target_proc, tr->data_size, 
 tr->offsets_size, !reply && (t->flags & TF_ONE_WAY)); 
if (t->buffer == NULL) { 
 return_error = BR_FAILED_REPLY; 
 goto err_binder_alloc_buf_failed; 
} 
t->buffer->allow_user_free = 0; 
t->buffer->debug_id = t->debug_id; 
t->buffer->transaction = t; 
t->buffer->target_node = target_node; 
if (target_node) 
 binder_inc_node(target_node, 1, 0, NULL); 
 
offp = (size_t *)(t->buffer->data + ALIGN(tr->data_size, sizeof(void *))); 
 
if (copy_from_user(t->buffer->data, tr->data.ptr.buffer, tr->data_size)) { 
 ...... 
 return_error = BR_FAILED_REPLY; 
 goto err_copy_data_failed; 
} 
if (copy_from_user(offp, tr->data.ptr.offsets, tr->offsets_size)) { 
 ...... 
 return_error = BR_FAILED_REPLY; 
 goto err_copy_data_failed; 
}

         注意，这里的事务t是要交给target_proc处理的，在这个场景之下，就是Service Manager了。因此，下面的语句：

t->buffer = binder_alloc_buf(target_proc, tr->data_size, 
  tr->offsets_size, !reply && (t->flags & TF_ONE_WAY));

         就是在Service Manager的进程空间中分配一块内存来保存用户传进入的参数了：

if (copy_from_user(t->buffer->data, tr->data.ptr.buffer, tr->data_size)) { 
 ...... 
 return_error = BR_FAILED_REPLY; 
 goto err_copy_data_failed; 
} 
if (copy_from_user(offp, tr->data.ptr.offsets, tr->offsets_size)) { 
 ...... 
 return_error = BR_FAILED_REPLY; 
 goto err_copy_data_failed; 
}

         由于现在target_node要被使用了，增加它的引用计数：

if (target_node) 
  binder_inc_node(target_node, 1, 0, NULL);

        接下去的for循环，就是用来处理传输数据中的Binder对象了。在我们的场景中，有一个类型为BINDER_TYPE_BINDER的Binder实体MediaPlayerService：

 switch (fp->type) { 
 case BINDER_TYPE_BINDER: 
 case BINDER_TYPE_WEAK_BINDER: { 
struct binder_ref *ref; 
struct binder_node *node = binder_get_node(proc, fp->binder); 
if (node == NULL) { 
 node = binder_new_node(proc, fp->binder, fp->cookie); 
 if (node == NULL) { 
  return_error = BR_FAILED_REPLY; 
  goto err_binder_new_node_failed; 
 } 
 node->min_priority = fp->flags & FLAT_BINDER_FLAG_PRIORITY_MASK; 
 node->accept_fds = !!(fp->flags & FLAT_BINDER_FLAG_ACCEPTS_FDS); 
} 
if (fp->cookie != node->cookie) { 
 ...... 
 goto err_binder_get_ref_for_node_failed; 
} 
ref = binder_get_ref_for_node(target_proc, node); 
if (ref == NULL) { 
 return_error = BR_FAILED_REPLY; 
 goto err_binder_get_ref_for_node_failed; 
} 
if (fp->type == BINDER_TYPE_BINDER) 
 fp->type = BINDER_TYPE_HANDLE; 
else 
 fp->type = BINDER_TYPE_WEAK_HANDLE; 
fp->handle = ref->desc; 
binder_inc_ref(ref, fp->type == BINDER_TYPE_HANDLE, &thread->todo); 
...... 
       
} break;

        由于是第一次在Binder驱动程序中传输这个MediaPlayerService，调用binder_get_node函数查询这个Binder实体时，会返回空，于是binder_new_node在proc中新建一个，下次就可以直接使用了。

        现在，由于要把这个Binder实体MediaPlayerService交给target_proc，也就是Service Manager来管理，也就是说Service Manager要引用这个MediaPlayerService了，于是通过binder_get_ref_for_node为MediaPlayerService创建一个引用，并且通过binder_inc_ref来增加这个引用计数，防止这个引用还在使用过程当中就被销毁。注意，到了这里的时候，t->buffer中的flat_binder_obj的type已经改为BINDER_TYPE_HANDLE，handle已经改为ref->desc，跟原来不一样了，因为这个flat_binder_obj是最终是要传给Service Manager的，而Service Manager只能够通过句柄值来引用这个Binder实体。

        最后，把待处理事务加入到target_list列表中去：

                 list_add_tail(&t->work.entry, target_list);  

        并且把待完成工作项加入到本线程的todo等待执行列表中去：

                    list_add_tail(&tcomplete->entry, &thread->todo);  

        现在目标进程有事情可做了，于是唤醒它：

             if (target_wait)  
                          wake_up_interruptible(target_wait);   

       这里就是要唤醒Service Manager进程了。回忆一下前面这篇文章，此时， Service Manager正在binder_t浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路hread_read函数中调用wait_event_interruptible进入休眠状态。

       这里我们先忽略一下Service Manager被唤醒之后的场景，继续MedaPlayerService的启动过程，然后再回来。

       回到binder_ioctl函数，bwr.read_size > 0为true，于是进入binder_thread_read函数：

static int 
binder_thread_read(struct binder_proc *proc, struct binder_thread *thread, 
     void __user *buffer, int size, signed long *consumed, int non_block) 
{ 
 void __user *ptr = buffer + *consumed; 
 void __user *end = buffer + size; 
 
 int ret = 0; 
 int wait_for_proc_work; 
 
 if (*consumed == 0) { 
  if (put_user(BR_NOOP, (uint32_t __user *)ptr)) 
   return -EFAULT; 
  ptr += sizeof(uint32_t); 
 } 
 
retry: 
 wait_for_proc_work = thread->transaction_stack == NULL && list_empty(&thread->todo); 
  
 ....... 
 
 if (wait_for_proc_work) { 
  ....... 
 } else { 
  if (non_block) { 
   if (!binder_has_thread_work(thread)) 
    ret = -EAGAIN; 
  } else 
   ret = wait_event_interruptible(thread->wait, binder_has_thread_work(thread)); 
 } 
  
 ...... 
 
 while (1) { 
  uint32_t cmd; 
  struct binder_transaction_data tr; 
  struct binder_work *w; 
  struct binder_transaction *t = NULL; 
 
  if (!list_empty(&thread->todo)) 
   w = list_first_entry(&thread->todo, struct binder_work, entry); 
  else if (!list_empty(&proc->todo) && wait_for_proc_work) 
   w = list_first_entry(&proc->todo, struct binder_work, entry); 
  else { 
   if (ptr - buffer == 4 && !(thread->looper & BINDER_LOOPER_STATE_NEED_RETURN)) /* no data added */ 
    goto retry; 
   break; 
  } 
 
  if (end - ptr < sizeof(tr) + 4) 
   break; 
 
  switch (w->type) { 
  ...... 
  case BINDER_WORK_TRANSACTION_COMPLETE: { 
   cmd = BR_TRANSACTION_COMPLETE; 
   if (put_user(cmd, (uint32_t __user *)ptr)) 
    return -EFAULT; 
   ptr += sizeof(uint32_t); 
 
   binder_stat_br(proc, thread, cmd); 
   if (binder_debug_mask & BINDER_DEBUG_TRANSACTION_COMPLETE) 
    printk(KERN_INFO "binder: %d:%d BR_TRANSACTION_COMPLETE\n", 
    proc->pid, thread->pid); 
 
   list_del(&w->entry); 
   kfree(w); 
   binder_stats.obj_deleted[BINDER_STAT_TRANSACTION_COMPLETE]++; 
            } break; 
  ...... 
  } 
 
  if (!t) 
   continue; 
 
  ...... 
 } 
 
done: 
 ...... 
 return 0; 
}

        这里，thread->transaction_stack和thread->todo均不为空，于是wait_for_proc_work为false，由于binder_has_thread_work的时候，返回true，这里因为thread->todo不为空，因此，线程虽然调用了wait_event_interruptible，但是不会睡眠，于是继续往下执行。

        由于thread->todo不为空，执行下列语句：

if (!list_empty(&thread->todo)) 
  w = list_first_entry(&thread->todo, struct binder_work, entry);

        w->type为BINDER_WORK_TRANSACTION_COMPLETE，这是在上面的binder_transaction函数设置的，于是执行：

 switch (w->type) { 
 ...... 
 case BINDER_WORK_TRANSACTION_COMPLETE: { 
cmd = BR_TRANSACTION_COMPLETE; 
if (put_user(cmd, (uint32_t __user *)ptr)) 
 return -EFAULT; 
ptr += sizeof(uint32_t); 
 
  ...... 
list_del(&w->entry); 
kfree(w); 
   
} break; 
...... 
 }

        这里就将w从thread->todo删除了。由于这里t为空，重新执行while循环，这时由于已经没有事情可做了，最后就返回到binder_ioctl函数中。注间，这里一共往用户传进来的缓冲区buffer写入了两个整数，分别是BR_NOOP和BR_TRANSACTION_COMPLETE。

        binder_ioctl函数返回到用户空间之前，把数据消耗情况拷贝回用户空间中：

if (copy_to_user(ubuf, &bwr, sizeof(bwr))) { 
 ret = -EFAULT; 
 goto err; 
}

        最后返回到IPCThreadState::talkWithDriver函数中，执行下面语句： 

 if (err >= NO_ERROR) { 
  if (bwr.write_consumed > 0) { 
   if (bwr.write_consumed < (ssize_t)mOut.dataSize()) 
    mOut.remove(0, bwr.write_consumed); 
   else 
    mOut.setDataSize(0); 
  } 
  if (bwr.read_consumed > 0) { 
<pre code_snippet_id="134056" snippet_file_name="blog_20131230_54_6706870" name="code" class="cpp">   mIn.setDataSize(bwr.read_consumed); 
   mIn.setDataPosition(0);</pre>  }  ......  return NO_ERROR; }

        首先是把mOut的数据清空：
                          mOut.setDataSize(0);  

       然后设置已经读取的内容的大小：

                          mIn.setDataSize(bwr.read_consumed);  
                          mIn.setDataPosition(0);  

        然后返回到IPCThreadState::waitForResponse函数中。在IPCThreadState::waitForResponse函数，先是从mIn读出一个整数，这个便是BR_NOOP了，这是一个空操作，什么也不做。然后继续进入IPCThreadState::talkWithDriver函数中。

        这时候，下面语句执行后：

                       const bool needRead = mIn.dataPosition() >= mIn.dataSize();  

        needRead为false，因为在mIn中，尚有一个整数BR_TRANSACTION_COMPLETE未读出。

       这时候，下面语句执行后：

                       const size_t outAvail = (!doReceive || needRead) ? mOut.dataSize() : 0;  

        outAvail等于0。因此，最后bwr.write_size和bwr.read_size均为0，IPCThreadState::talkWithDriver函数什么也不做，直接返回到IPCThreadState::waitForResponse函数中。在IPCThreadState::waitForResponse函数，又继续从mIn读出一个整数，这个便是BR_TRANSACTION_COMPLETE：

switch (cmd) { 
case BR_TRANSACTION_COMPLETE: 
  if (!reply && !acquireResult) goto finish; 
  break; 
...... 
}

        reply不为NULL，因此，IPCThreadState::waitForResponse的循环没有结束，继续执行，又进入到IPCThreadState::talkWithDrive中。

        这次，needRead就为true了，而outAvail仍为0，所以bwr.read_size不为0，bwr.write_size为0。于是通过：

                       ioctl(mProcess->mDriverFD, BINDER_WRITE_READ, &bwr)  

        进入到Binder驱动程序中的binder_ioctl函数中。由于bwr.write_size为0，bwr.read_size不为0，这次直接就进入到binder_thread_read函数中。这时候，thread->transaction_stack不等于0，但是thread->todo为空，于是线程就通过：
[cpp] view plain copy 在CODE上查看代码片派生到我的代码片
wait_event_interruptible(thread->wait, binder_has_thread_work(thread));  

        进入睡眠状态，等待Service Manager来唤醒了。

        现在，我们可以回到Service Manager被唤醒的过程了。我们接着前面浅谈Service Manager成为Android进程间通信（IPC）机制Binder守护进程之路这篇文章的最后，继续描述。此时， Service Manager正在binder_thread_read函数中调用wait_event_interruptible_exclusive进入休眠状态。上面被MediaPlayerService启动后进程唤醒后，继续执行binder_thread_read函数：

static int 
binder_thread_read(struct binder_proc *proc, struct binder_thread *thread, 
     void __user *buffer, int size, signed long *consumed, int non_block) 
{ 
 void __user *ptr = buffer + *consumed; 
 void __user *end = buffer + size; 
 
 int ret = 0; 
 int wait_for_proc_work; 
 
 if (*consumed == 0) { 
  if (put_user(BR_NOOP, (uint32_t __user *)ptr)) 
   return -EFAULT; 
  ptr += sizeof(uint32_t); 
 } 
 
retry: 
 wait_for_proc_work = thread->transaction_stack == NULL && list_empty(&thread->todo); 
 
 ...... 
 
 if (wait_for_proc_work) { 
  ...... 
  if (non_block) { 
   if (!binder_has_proc_work(proc, thread)) 
    ret = -EAGAIN; 
  } else 
   ret = wait_event_interruptible_exclusive(proc->wait, binder_has_proc_work(proc, thread)); 
 } else { 
  ...... 
 } 
  
 ...... 
 
 while (1) { 
  uint32_t cmd; 
  struct binder_transaction_data tr; 
  struct binder_work *w; 
  struct binder_transaction *t = NULL; 
 
  if (!list_empty(&thread->todo)) 
   w = list_first_entry(&thread->todo, struct binder_work, entry); 
  else if (!list_empty(&proc->todo) && wait_for_proc_work) 
   w = list_first_entry(&proc->todo, struct binder_work, entry); 
  else { 
   if (ptr - buffer == 4 && !(thread->looper & BINDER_LOOPER_STATE_NEED_RETURN)) /* no data added */ 
    goto retry; 
   break; 
  } 
 
  if (end - ptr < sizeof(tr) + 4) 
   break; 
 
  switch (w->type) { 
  case BINDER_WORK_TRANSACTION: { 
   t = container_of(w, struct binder_transaction, work); 
          } break; 
  ...... 
  } 
 
  if (!t) 
   continue; 
 
  BUG_ON(t->buffer == NULL); 
  if (t->buffer->target_node) { 
   struct binder_node *target_node = t->buffer->target_node; 
   tr.target.ptr = target_node->ptr; 
   tr.cookie = target_node->cookie; 
   ...... 
   cmd = BR_TRANSACTION; 
  } else { 
   ...... 
  } 
  tr.code = t->code; 
  tr.flags = t->flags; 
  tr.sender_euid = t->sender_euid; 
 
  if (t->from) { 
   struct task_struct *sender = t->from		
声明：本文内容来源于网络，版权归原作者所有，内容由互联网用户自发贡献自行上传，本网站不拥有所有权，未作人工编辑处理，也不承担相关法律责任。如果您发现有涉嫌版权的内容，欢迎发送邮件至：notice#nhooo.com（发邮件时，请将#更换为@）进行举报，并提供相关证据，一经查实，本站将立刻删除涉嫌侵权内容。
基础教程
猜你喜欢

友情链接： json在线解析 通晓查询 糯晒黄历 姓名打分 风车动漫