涉及源碼（Android 4.4.2）：
frameworks/base/cmds/app_process/app_main.cpp
/frameworks/base/core/jni/AndroidRuntime.cpp
/libnativehelper/JniInvocation.cpp
/dalvik/vm/Jni.cpp
/dalvik/vm/JniInternal.h
/libnativehelper/include/nativehelper/jni.h

首先來看看app_main.cpp的main方法内狸，它是啟動虛擬機的入口方法。

frameworks/base/cmds/app_process/app_main.cpp

int main(int argc, char* const argv[])
{
   // zygote進程是由init進程通過fork而來
    AppRuntime runtime;
  
    if (zygote) {
        runtime.start("com.android.internal.os.ZygoteInit",
                startSystemServer ? "start-system-server" : "");
    }
}

/frameworks/base/core/jni/AndroidRuntime.cpp

void AndroidRuntime::start(const char* className, const char* options)
{

    /* start the virtual machine */
    JniInvocation jni_invocation;
    // 1骑晶、初始化JNI相關(guān)的函數(shù)
    jni_invocation.Init(NULL);
    JNIEnv* env;
    // 2拟赊、啟動虛擬機
    if (startVm(&mJavaVM, &env) != 0) {
        return;
    }
    onVmCreated(env);

    // 3刺桃、注冊JNI函數(shù)
    if (startReg(env) < 0) {
        ALOGE("Unable to register all android natives\n");
        return;
    }
}

一、初始化JNI相關(guān)的函數(shù)

/libnativehelper/JniInvocation.cpp

bool JniInvocation::Init(const char* library) {
#ifdef HAVE_ANDROID_OS
  char default_library[PROPERTY_VALUE_MAX];
  property_get(kLibrarySystemProperty, default_library, kLibraryFallback);
#else
  const char* default_library = kLibraryFallback;
#endif
  if (library == NULL) {
    library = default_library;
  }
  // 通過dlopen加載libdvm.so吸祟，libdvm.so是dalvik vm的核心庫
  handle_ = dlopen(library, RTLD_NOW);
  //從libdvm.so中找到JNI_GetDefaultJavaVMInitArgs瑟慈、NI_CreateJavaVM和JNI_GetCreateJavaVMs這三個函數(shù)指針。
  if (!FindSymbol(reinterpret_cast<void**>(&JNI_GetDefaultJavaVMInitArgs_),
                  "JNI_GetDefaultJavaVMInitArgs")) {
    return false;
  }
  if (!FindSymbol(reinterpret_cast<void**>(&JNI_CreateJavaVM_),
                  "JNI_CreateJavaVM")) {
    return false;
  }
  if (!FindSymbol(reinterpret_cast<void**>(&JNI_GetCreatedJavaVMs_),
                  "JNI_GetCreatedJavaVMs")) {
    return false;
  }
  return true;
}

二屋匕、啟動虛擬機

int AndroidRuntime::startVm(JavaVM** pJavaVM, JNIEnv** pEnv)
{
 // 前面是初始化操作葛碧，重點是整個方法
 if (JNI_CreateJavaVM(pJavaVM, pEnv, &initArgs) < 0) {
        ALOGE("JNI_CreateJavaVM failed\n");
        goto bail;
    }
}

JNI_CreateJavaVM方法就是前面libdvm.so中的方法，它就是創(chuàng)建虛擬機的方法过吻。

下面來看看這個JNI_CreateJavaVM方法

/dalvik/vm/Jni.cpp

jint JNI_CreateJavaVM(JavaVM** p_vm, JNIEnv** p_env, void* vm_args) {
    const JavaVMInitArgs* args = (JavaVMInitArgs*) vm_args;
    
    //1进泼、gDvm是一個靜態(tài)的數(shù)據(jù)結(jié)構(gòu)，數(shù)據(jù)類型為結(jié)構(gòu)體DvmGlobals
    // 虛擬機的大部分數(shù)據(jù)都是有它來存放
    memset(&gDvm, 0, sizeof(gDvm));

    //2纤虽、創(chuàng)建JavaVMExt對象乳绕，其實也是JavaVM對象
    JavaVMExt* pVM = (JavaVMExt*) calloc(1, sizeof(JavaVMExt));
    pVM->funcTable = &gInvokeInterface;
    pVM->envList = NULL;
    dvmInitMutex(&pVM->envListLock);

   
    gDvmJni.jniVm = (JavaVM*) pVM;

   // 3、創(chuàng)建JNIEnvExt對象逼纸，其實對應的也是JNIEnv對象
    JNIEnvExt* pEnv = (JNIEnvExt*) dvmCreateJNIEnv(NULL);

    //4洋措、啟動虛擬機
    gDvm.initializing = true;
    std::string status =
            dvmStartup(argc, argv.get(), args->ignoreUnrecognized, (JNIEnv*)pEnv);
    gDvm.initializing = false;
    
    *p_env = (JNIEnv*) pEnv;
    *p_vm = (JavaVM*) pVM;
   
}

1、重置gDvm結(jié)構(gòu)

DvmGlobals樊展，該結(jié)構(gòu)體是Dalvik的核心數(shù)據(jù)結(jié)構(gòu)呻纹，幾乎所有的重要成員等都通過gDvm來管理。

2专缠、創(chuàng)建JavaVMExt對象

JavaVMExt對象的funcTable成員用來保存Dalvik虛擬機實例函數(shù)表，從代碼可以看到淑仆，這個函數(shù)表為gInvokeInterface涝婉，gInvokeInterface是一個類型為JNIInvokeInterface的結(jié)構(gòu)體。

/dalvik/vm/jni.cpp

static const struct JNIInvokeInterface gInvokeInterface = {  
    NULL,  
    NULL,  
    NULL,  

    DestroyJavaVM,  
    AttachCurrentThread,  
    DetachCurrentThread,  

    GetEnv,  

    AttachCurrentThreadAsDaemon,  
};  

3蔗怠、創(chuàng)建JNIEnvExt對象

下面來看看dvmCreateJNIEnv函數(shù)

JNIEnv* dvmCreateJNIEnv(Thread* self) {
    JavaVMExt* vm = (JavaVMExt*) gDvmJni.jniVm;
    
    // 1墩弯、創(chuàng)建JNIEnvExt對象
    // Dalvik虛擬機里JNI的所有函數(shù)都封裝在gNativeInterface中
    JNIEnvExt* newEnv = (JNIEnvExt*) calloc(1, sizeof(JNIEnvExt));
    newEnv->funcTable = &gNativeInterface;
    if (self != NULL) {
        dvmSetJniEnvThreadId((JNIEnv*) newEnv, self);
        assert(newEnv->envThreadId != 0);
    } else {
        newEnv->envThreadId = 0x77777775;
        newEnv->self = (Thread*) 0x77777779;
    }
    if (gDvmJni.useCheckJni) {
        dvmUseCheckedJniEnv(newEnv);
    }

    ScopedPthreadMutexLock lock(&vm->envListLock);

    // 2、將JNIEnvExt插入到JavaVMExt對象的成員變量envList列表的頭部
    newEnv->next = vm->envList;
    assert(newEnv->prev == NULL);
    if (vm->envList == NULL) {
        // rare, but possible
        vm->envList = newEnv;
    } else {
        vm->envList->prev = newEnv;
    }
    vm->envList = newEnv;
    
    return (JNIEnv*) newEnv;
}

（1）結(jié)構(gòu)體JNINativeInterface用來描述一個本地接口表寞射。當我們需要在C/C++代碼在中調(diào)用Java函數(shù)渔工，就要用到這個本地接口表

static const struct JNINativeInterface gNativeInterface = {  
    ......  
      
    FindClass,  
  
    ......  
  
    GetMethodID,  
      
    ......  
  
    CallObjectMethod,  
      
    ......  
  
    GetFieldID,  
  
    ......  
      
    SetIntField,  
      
    ......  
  
    RegisterNatives,  
    UnregisterNatives,  
  
    ......  
  
    GetJavaVM,  
  
    ......  
};

（2）每一個Dalvik虛擬機實例還有一個JNI環(huán)境列表,這個列表保存JavaVMExt對象的成員變量envList中。JavaVMExt的JNI環(huán)境列表就是JNIEnvExt列表桥温。每一個Attach到Dalvik虛擬機中去的線程都有一個對應的JNIEnvExt引矩，用來描述它的JNI環(huán)境。

他們之間的關(guān)系圖如下圖所示：

/dalvik/vm/JniInternal.h
/libnativehelper/include/nativehelper/jni.h

vmstart.png

4、初始化并啟動虛擬機

dalvik/vm/init.cpp

std::string dvmStartup(int argc, const char* const argv[],
        bool ignoreUnrecognized, JNIEnv* pEnv)
{
     /*
     * Initialize components.
     */
    dvmQuasiAtomicsStartup();
    if (!dvmAllocTrackerStartup()) {
        return "dvmAllocTrackerStartup failed";
    }
    if (!dvmGcStartup()) {
        return "dvmGcStartup failed";
    }
    if (!dvmThreadStartup()) {
        return "dvmThreadStartup failed";
    }
    if (!dvmInlineNativeStartup()) {
        return "dvmInlineNativeStartup";
    }
    if (!dvmRegisterMapStartup()) {
        return "dvmRegisterMapStartup failed";
    }
    if (!dvmInstanceofStartup()) {
        return "dvmInstanceofStartup failed";
    }
    if (!dvmClassStartup()) {
        return "dvmClassStartup failed";
    }

    if (!dvmFindRequiredClassesAndMembers()) {
        return "dvmFindRequiredClassesAndMembers failed";
    }

    if (!dvmStringInternStartup()) {
        return "dvmStringInternStartup failed";
    }
    if (!dvmNativeStartup()) {
        return "dvmNativeStartup failed";
    }
    if (!dvmInternalNativeStartup()) {
        return "dvmInternalNativeStartup failed";
    }
    if (!dvmJniStartup()) {
        return "dvmJniStartup failed";
    }
    if (!dvmProfilingStartup()) {
        return "dvmProfilingStartup failed";
    }

    if (!dvmCreateInlineSubsTable()) {
        return "dvmCreateInlineSubsTable failed";
    }

    if (!dvmValidateBoxClasses()) {
        return "dvmValidateBoxClasses failed";
    }

    if (!dvmPrepMainForJni(pEnv)) {
        return "dvmPrepMainForJni failed";
    }

    if (!dvmInitClass(gDvm.classJavaLangClass)) {
        return "couldn't initialized java.lang.Class";
    }

    if (!registerSystemNatives(pEnv)) {
        return "couldn't register system natives";
    }

    if (!dvmCreateStockExceptions()) {
        return "dvmCreateStockExceptions failed";
    }

    if (!dvmPrepMainThread()) {
        return "dvmPrepMainThread failed";
    }

    if (dvmReferenceTableEntries(&dvmThreadSelf()->internalLocalRefTable) != 0)
    {
        ALOGW("Warning: tracked references remain post-initialization");
        dvmDumpReferenceTable(&dvmThreadSelf()->internalLocalRefTable, "MAIN");
    }

    if (!dvmDebuggerStartup()) {
        return "dvmDebuggerStartup failed";
    }

    if (!dvmGcStartupClasses()) {
        return "dvmGcStartupClasses failed";
    }

    /*
     * Init for either zygote mode or non-zygote mode.  The key difference
     * is that we don't start any additional threads in Zygote mode.
     */
    if (gDvm.zygote) {
        if (!initZygote()) {
            return "initZygote failed";
        }
    } else {
        if (!dvmInitAfterZygote()) {
            return "dvmInitAfterZygote failed";
        }
    }

}

主要用來初始化Dalvik虛擬機

三旺韭、注冊JNI函數(shù)

/frameworks/base/core/jni/AndroidRuntime.cpp

/*static*/ int AndroidRuntime::startReg(JNIEnv* env)
{
    // 注冊JNI函數(shù)氛谜，gRegJNI是一個全局數(shù)組
    if (register_jni_procs(gRegJNI, NELEM(gRegJNI), env) < 0) {
        env->PopLocalFrame(NULL);
        return -1;
    }
    env->PopLocalFrame(NULL);

    return 0;
}

static const RegJNIRec gRegJNI[] = {
    REG_JNI(register_android_debug_JNITest),
    REG_JNI(register_com_android_internal_os_RuntimeInit),
    REG_JNI(register_android_os_SystemClock),
    REG_JNI(register_android_util_EventLog),
    REG_JNI(register_android_util_Log),
    REG_JNI(register_android_util_FloatMath),
    REG_JNI(register_android_text_format_Time),
    REG_JNI(register_android_content_AssetManager),
    REG_JNI(register_android_content_StringBlock),
    REG_JNI(register_android_content_XmlBlock),
    REG_JNI(register_android_emoji_EmojiFactory),
    REG_JNI(register_android_text_AndroidCharacter),
    REG_JNI(register_android_text_AndroidBidi),
    REG_JNI(register_android_view_InputDevice),
    REG_JNI(register_android_view_KeyCharacterMap),
    REG_JNI(register_android_os_Process),
    REG_JNI(register_android_os_SystemProperties),
    REG_JNI(register_android_os_Binder),
    // ...還是很多
    }

參考文章：
http://www.infoq.com/cn/articles/android-in-depth-dalvik
http://blog.csdn.net/luoshengyang/article/details/8885792