Android Frameworks源码分析之Binder(六)---Service Manager(2)

最新推荐文章于 2024-09-14 19:06:02 发布

woaininizhidao

最新推荐文章于 2024-09-14 19:06:02 发布

阅读量64

点赞数

分类专栏： Android 文章标签： android 源码 Binder frameworks

本文链接：https://blog.csdn.net/woaininizhidao/article/details/38876461

版权

Android 专栏收录该内容

14 篇文章 0 订阅

订阅专栏

在这篇文章中，我们看一看Service Manager的代理对象的获得。

这部分涉及到的文件主要有以下几个：

IServiceManager.h frameworks/native/include/binder/IServiceManager.h

IServiceManager.cpp frameworks/native/libs/binder/IServiceManager.cpp

在IServiceManager.h文件中，定义了Service Manager的接口IServiceManage

class IServiceManager : public IInterface
{
public:
    DECLARE_META_INTERFACE(ServiceManager);

    /**
     * Retrieve an existing service, blocking for a few seconds
     * if it doesn't yet exist.
     */
    virtual sp<IBinder>         getService( const String16& name) const = 0;

    /**
     * Retrieve an existing service, non-blocking.
     */
    virtual sp<IBinder>         checkService( const String16& name) const = 0;

    /**
     * Register a service.
     */
    virtual status_t            addService( const String16& name,
                                            const sp<IBinder>& service,
                                            bool allowIsolated = false) = 0;

    /**
     * Return list of all existing services.
     */
    virtual Vector<String16>    listServices() = 0;

    enum {
        GET_SERVICE_TRANSACTION = IBinder::FIRST_CALL_TRANSACTION,
        CHECK_SERVICE_TRANSACTION,
        ADD_SERVICE_TRANSACTION,
        LIST_SERVICES_TRANSACTION,
    };
};

其中，addService和getService用于将Binder本地对象加入到Service Manager中和从Service Manager中获取Binder代理对象。

在IServiceManager.cpp文件中，定义了defaultServiceManager函数，用来获得Service Manager的Binder代理对象。

sp<IServiceManager> defaultServiceManager()
{
    if (gDefaultServiceManager != NULL) return gDefaultServiceManager;
    
    {
        AutoMutex _l(gDefaultServiceManagerLock);
        if (gDefaultServiceManager == NULL) {
            gDefaultServiceManager = interface_cast<IServiceManager>(
                ProcessState::self()->getContextObject(NULL));
        }
    }
    
    return gDefaultServiceManager;
}

gDefaultServiceManager是一个全局变量，保存进程获得的唯一的一个Service Manager的Binder代理对象。

如果是第一次调用gDefaultServiceManager函数，会调用ProcessState的getContextObject函数来获得Binder代理对象，而因为Binder本地对象的虚拟地址为0，因此在这里传进去的参数为null。ProcessState的getContextObject函数定义如下：

sp<IBinder> ProcessState::getContextObject(const sp<IBinder>& caller)
{
    return getStrongProxyForHandle(0);
}

sp<IBinder> ProcessState::getStrongProxyForHandle(int32_t handle)
{
    sp<IBinder> result;

    AutoMutex _l(mLock);

    handle_entry* e = lookupHandleLocked(handle);

    if (e != NULL) {
        // We need to create a new BpBinder if there isn't currently one, OR we
        // are unable to acquire a weak reference on this current one.  See comment
        // in getWeakProxyForHandle() for more info about this.
        IBinder* b = e->binder;
        if (b == NULL || !e->refs->attemptIncWeak(this)) {
			//构造一个代理对象
            b = new BpBinder(handle); 
            e->binder = b;
            if (b) e->refs = b->getWeakRefs();
            result = b;
        } else {
            // This little bit of nastyness is to allow us to add a primary
            // reference to the remote proxy when this team doesn't have one
            // but another team is sending the handle to us.
            result.force_set(b);
            e->refs->decWeak(this);
        }
    }

    return result;
}

在getStrongProxyForHandle函数中会调用lookupHandleLocked来查找与参数handle对应的handle_entry结构。在进程中会使用一个列表保存进程的所有的Binder代理对象

ProcessState::handle_entry* ProcessState::lookupHandleLocked(int32_t handle)
{
    const size_t N=mHandleToObject.size();
    if (N <= (size_t)handle) {
        handle_entry e;
        e.binder = NULL;
        e.refs = NULL;
        status_t err = mHandleToObject.insertAt(e, N, handle+1-N);
        if (err < NO_ERROR) return NULL;
    }
    return &mHandleToObject.editItemAt(handle);
}