【framework】Surface创建流程
1 前言
View添加过程 中介绍了从 WindowManagerImpl 的 addView() 方法到 WindowState、SurfaceSession 的创建流程,本文将介绍 Surface 的创建流程。应用进程中,ViewRootImpl 持有 Surface 对象,system_server 进程中,WindowSurfaceController 持有 SurfaceControl 对象,Surface 和 SurfaceControl 都持有 native 层的同一个 Surface 对象的地址(SurfaceFlinger 进程)。
Surface 在应用进程和 system_server 进程中都有创建,因此,本文主要介绍 system_server 进程中 SurfaceControl 的创建流程和应用进程中 Surface 的创建流程。
为区分不同进程,将应用进程、system_server 进程分别标识为浅蓝色、深蓝色。
2 源码分析
2.1 ViewRootImpl 到 Session
如图,浅蓝色的类是应用进程中执行的,深蓝色的类是在 system_server 进程中执行的,黄色的类是指 AIDL 文件生成的接口(用于跨进程)。

(1)ViewRootImpl
/frameworks/base/core/java/android/view/ViewRootImpl.java
public final Surface mSurface = new Surface();
private final SurfaceControl mSurfaceControl = new SurfaceControl();
public ViewRootImpl(Context context, Display display) {
mContext = context;
//IWindowSession 类型,单例对象,getWindowSession() 方法调用 WMS 的 openSession() 方法,new 一个 Session 对象(IWindowSession.Stub 的实现类)
mWindowSession = WindowManagerGlobal.getWindowSession();
mDisplay = display;
...
mWindow = new W(this); //IWindow.Stub 的实现类
...
mAttachInfo = new View.AttachInfo(mWindowSession, mWindow, display, this, mHandler, this, context); //View.AttachInfo 类型
...
mChoreographer = Choreographer.getInstance();
mDisplayManager = (DisplayManager)context.getSystemService(Context.DISPLAY_SERVICE);
...
}
说明:Session 是 IWindowSession.Stub 的实现类,属于 WMS 端的类,WindowManagerGlobal.getWindowSession() 方法最终会调用 WMS 的 openSession() 方法,创建一个 Session 对象,每个应用进程,最多对应一个 Session 对象;W 类是 ViewRootImpl 的内部类,也是 IWindow.Stub 的实现类,每个 根 View 都与一个 W 一一对应,即 mWindow.asBinder() 可以作为 根 View (或窗口)的身份标识。
(2)setView
/frameworks/base/core/java/android/view/ViewRootImpl.java
public void setView(View view, WindowManager.LayoutParams attrs, View panelParentView) {
synchronized (this) {
if (mView == null) {
mView = view;
...
mWindowAttributes.copyFrom(attrs);
...
mAttachInfo.mRootView = view;
...
if (panelParentView != null) {
mAttachInfo.mPanelParentWindowToken = panelParentView.getApplicationWindowToken();
}
...
//请求显示 View
requestLayout();
...
try {
...
//添加 View
res = mWindowSession.addToDisplay(mWindow, mSeq, mWindowAttributes, getHostVisibility(),
mDisplay.getDisplayId(), mTmpFrame, mAttachInfo.mContentInsets, mAttachInfo.mStableInsets,
mAttachInfo.mOutsets, mAttachInfo.mDisplayCutout, mInputChannel, mTempInsets);
setFrame(mTmpFrame);
}
...
}
}
}
mWindowSession.addToDisplay() 的执行流程在 View添加过程 中已做介绍,接下来跟踪 requestLayout() 的执行流程。
(3)requestLayout
/frameworks/base/core/java/android/view/ViewRootImpl.java
public void requestLayout() {
if (!mHandlingLayoutInLayoutRequest) {
...
scheduleTraversals();
}
}
(4)scheduleTraversals
/frameworks/base/core/java/android/view/ViewRootImpl.java
void scheduleTraversals() {
if (!mTraversalScheduled) {
...
mChoreographer.postCallback(Choreographer.CALLBACK_TRAVERSAL, mTraversalRunnable, null);
...
}
}
final class TraversalRunnable implements Runnable {
public void run() {
doTraversal();
}
}
final TraversalRunnable mTraversalRunnable = new TraversalRunnable();
Choreographer 通过消息处理,最终调用 mTraversalRunnable 的 run() 方法,其中又会调用 doTraversal() 方法。
(5)doTraversal
/frameworks/base/core/java/android/view/ViewRootImpl.java
void doTraversal() {
if (mTraversalScheduled) {
...
performTraversals();
...
}
}
(6)performTraversals
/frameworks/base/core/java/android/view/ViewRootImpl.java
private void performTraversals() {
...
if (mFirst || windowShouldResize || insetsChanged || viewVisibilityChanged || params != null || mForceNextWindowRelayout) {
...
try {
...
//mWindowSession.relayout()
relayoutResult = relayoutWindow(params, viewVisibility, insetsPending);
...
}
...
}
...
if (didLayout) {
//view.requestLayout()
performLayout(lp, mWidth, mHeight);
...
}
...
if (!cancelDraw) {
...
//开始绘制:draw(fullRedrawNeeded)
performDraw();
}
...
}
(7)relayoutWindow
/frameworks/base/core/java/android/view/ViewRootImpl.java
private int relayoutWindow(WindowManager.LayoutParams params, int viewVisibility, boolean insetsPending) throws RemoteException {
...
int relayoutResult = mWindowSession.relayout(mWindow, mSeq, params, (int) (mView.getMeasuredWidth() * appScale + 0.5f),
(int) (mView.getMeasuredHeight() * appScale + 0.5f), viewVisibility, insetsPending ? WindowManagerGlobal.RELAYOUT_INSETS_PENDING : 0,
frameNumber, mTmpFrame, mPendingOverscanInsets, mPendingContentInsets, mPendingVisibleInsets, mPendingStableInsets,
mPendingOutsets, mPendingBackDropFrame, mPendingDisplayCutout, mPendingMergedConfiguration, mSurfaceControl, mTempInsets);
if (mSurfaceControl.isValid()) {
//复制 Surface:mNativeObject = nativeGetFromSurfaceControl(mNativeObject, other.mNativeObject)
mSurface.copyFrom(mSurfaceControl);
}
...
}
说明: mSurfaceControl 对象传递给 mWindowSession.relayout() 方法,最终在 WindowSurfaceController 的 getSurfaceControl() 方法中完成初始化。初始化后的 SurfaceControl 持有 native 层的 Surface 对象地址。mSurface.copyFrom() 方法从 SurfaceControl 中复制 native 层的 Surface 对象地址。
2.2 Session 到 WindowSurfaceController

(1)relayout
/frameworks/base/services/core/java/com/android/server/wm/Session.java
public int relayout(IWindow window, int seq, WindowManager.LayoutParams attrs, int requestedWidth, int requestedHeight,
int viewFlags, int flags, long frameNumber, Rect outFrame, Rect outOverscanInsets, Rect outContentInsets,
Rect outVisibleInsets, Rect outStableInsets, Rect outsets, Rect outBackdropFrame, DisplayCutout.ParcelableWrapper cutout,
MergedConfiguration mergedConfiguration, SurfaceControl outSurfaceControl, InsetsState outInsetsState) {
...
int res = mService.relayoutWindow(this, window, seq, attrs, requestedWidth, requestedHeight, viewFlags,
flags, frameNumber, outFrame, outOverscanInsets, outContentInsets, outVisibleInsets, outStableInsets,
outsets, outBackdropFrame, cutout, mergedConfiguration, outSurfaceControl, outInsetsState);
...
}
(2)relayoutWindow
/frameworks/base/services/core/java/com/android/server/wm/WindowManagerService.java
public int relayoutWindow(Session session, IWindow client, int seq, LayoutParams attrs,
int requestedWidth, int requestedHeight, int viewVisibility, int flags,
long frameNumber, Rect outFrame, Rect outOverscanInsets, Rect outContentInsets,
Rect outVisibleInsets, Rect outStableInsets, Rect outOutsets, Rect outBackdropFrame,
DisplayCutout.ParcelableWrapper outCutout, MergedConfiguration mergedConfiguration,
SurfaceControl outSurfaceControl, InsetsState outInsetsState) {
...
synchronized (mGlobalLock) {
//mWindowMap.get(client.asBinder())
final WindowState win = windowForClientLocked(session, client, false);
...
//mWinAnimator 在 WindowState 的构造方法中创建
WindowStateAnimator winAnimator = win.mWinAnimator;
if (viewVisibility != View.GONE) {
win.setRequestedSize(requestedWidth, requestedHeight);
}
win.setFrameNumber(frameNumber);
...
if (shouldRelayout) {
...
try {
//创建 SurfaceControl 对象,并拷贝给 outSurfaceControl
result = createSurfaceControl(outSurfaceControl, result, win, winAnimator);
}
...
}
...
}
...
}
说明:WindowStateAnimator 在 WindowState 的构造方法中创建,并将自身注入,即 WindowState 对象与 WindowStateAnimator 对象一一对应。
(3)createSurfaceControl
/frameworks/base/services/core/java/com/android/server/wm/WindowManagerService.java
private int createSurfaceControl(SurfaceControl outSurfaceControl, int result, WindowState win, WindowStateAnimator winAnimator) {
...
WindowSurfaceController surfaceController;
try {
...
//创建 WindowSurfaceController
surfaceController = winAnimator.createSurfaceLocked(win.mAttrs.type, win.mOwnerUid);
}
...
if (surfaceController != null) {
//获取 SurfaceController:outSurfaceControl.copyFrom(mSurfaceControl)
surfaceController.getSurfaceControl(outSurfaceControl);
...
}
...
}
(4)createSurfaceLocked
/frameworks/base/services/core/java/com/android/server/wm/WindowStateAnimator.java
WindowSurfaceController createSurfaceLocked(int windowType, int ownerUid) {
final WindowState w = mWin;
if (mSurfaceController != null) {
return mSurfaceController;
}
...
calculateSurfaceBounds(w, attrs, mTmpSize);
...
try {
...
mSurfaceController = new WindowSurfaceController(mSession.mSurfaceSession, attrs.getTitle().toString(),
width, height, format, flags, this, windowType, ownerUid);
...
}
...
return mSurfaceController;
}
说明:WindowSurfaceController 在 WindowStateAnimator 中单例存在,在创建 WindowSurfaceController 时,又将 WindowStateAnimator 注入,由此说明 WindowSurfaceController 和 WindowStateAnimator 一一对应,进一步说明 WindowState 与 WindowSurfaceController 、WindowStateAnimator 一一对应。
(5)WindowSurfaceController
/frameworks/base/services/core/java/com/android/server/wm/WindowSurfaceController.java
public WindowSurfaceController(SurfaceSession s, String name, int w, int h, int format,
int flags, WindowStateAnimator animator, int windowType, int ownerUid) {
mAnimator = animator;
mSurfaceW = w;
mSurfaceH = h;
title = name;
mService = animator.mService;
final WindowState win = animator.mWin;
mWindowType = windowType;
mWindowSession = win.mSession;
...
final SurfaceControl.Builder b = win.makeSurface().setParent(win.getSurfaceControl()).setName(name)
.setBufferSize(w, h).setFormat(format).setFlags(flags).setMetadata(METADATA_OWNER_UID, ownerUid);
//创建 SurfaceControl:new SurfaceControl()
mSurfaceControl = b.build();
}
说明: win.makeSurface() 调用的是 WindowState 的父类 WindowContainer 中的方法。
(6)getSurfaceControl
/frameworks/base/services/core/java/com/android/server/wm/WindowSurfaceController.java
void getSurfaceControl(SurfaceControl outSurfaceControl) {
outSurfaceControl.copyFrom(mSurfaceControl);
}
2.3 WindowContainer 到 SurfaceControl

(1)makeSurface
/frameworks/base/services/core/java/com/android/server/wm/WindowContainer.java
SurfaceControl.Builder makeSurface() {
final WindowContainer p = getParent();
return p.makeChildSurface(this);
}
说明:WindowSurfaceController 调用了 win.makeSurface(),而 WindowState 继承了 WindowContainer。
(2)makeChildSurface
/frameworks/base/services/core/java/com/android/server/wm/WindowContainer.java
//child 为 WindowState 对象
SurfaceControl.Builder makeChildSurface(WindowContainer child) {
final WindowContainer p = getParent();
return p.makeChildSurface(child).setParent(mSurfaceControl);
}
说明:这里顺着容器层次结构由下往上依次调用,直到某个容器重写了 makeChildSurface() 方法,先后经历的容器有 WindowState、WindowToken、Task、TaskStack、DisplayContent,这些容器中,只有 DisplayContent 重写 WindowContainer 的 makeChildSurface() 方法。
(3)makeChildSurface
/frameworks/base/services/core/java/com/android/server/wm/DisplayContent.java
SurfaceControl.Builder makeChildSurface(WindowContainer child) {
//child 为 WindowState 对象
SurfaceSession s = child != null ? child.getSession() : getSession();
final SurfaceControl.Builder b = mWmService.makeSurfaceBuilder(s).setContainerLayer();
if (child == null) {
return b;
}
//mWindowingLayer 属于 SurfaceControl 类,在 DisplayContent 的构造方法中创建
return b.setName(child.getName()).setParent(mWindowingLayer);
}
(4)getSession
/frameworks/base/services/core/java/com/android/server/wm/WindowState.java
SurfaceSession getSession() {
if (mSession.mSurfaceSession != null) {
return mSession.mSurfaceSession;
} else {
return getParent().getSession();
}
}
说明:mSession.mSurfaceSession 在 WindowState 初始化时创建,具体流程为:在 WindowState 中调用 attach() 方法中,再调用 Session 的 windowAddedLocked() 方法,详见→View添加过程。
(5)makeSurfaceBuilder
/frameworks/base/services/core/java/com/android/server/wm/WindowManagerService.java
//将 SurfaceBuilderFactory 的 make() 方法映射到 SurfaceControl.Builder 的有参构造方法
SurfaceBuilderFactory mSurfaceBuilderFactory = SurfaceControl.Builder::new;
SurfaceControl.Builder makeSurfaceBuilder(SurfaceSession s) {
return mSurfaceBuilderFactory.make(s);
}
(6)make
/frameworks/base/services/core/java/com/android/server/wm/SurfaceBuilderFactory.java
interface SurfaceBuilderFactory {
SurfaceControl.Builder make(SurfaceSession s);
};
说明:将 SurfaceBuilderFactory 的 make() 方法映射到 SurfaceControl.Builder 的有参构造方法,SurfaceSession 对象来自 Session。
(7)Build
/frameworks/base/core/java/android/view/SurfaceControl.Build.java
public Builder(SurfaceSession session) {
mSession = session;
}
(8)SurfaceControl
/frameworks/base/core/java/android/view/SurfaceControl.Build.java
public SurfaceControl build() {
...
return new SurfaceControl(mSession, mName, mWidth, mHeight, mFormat, mFlags, mParent, mMetadata);
}
声明:本文转自【framework】Surface创建流程
【framework】Surface创建流程的更多相关文章
- android6.0 Activity(四) Surface创建
原文:http://blog.csdn.net/luoshengyang/article/details/8303098.原文代码比較老了,可是核心不变.在原文基础上改动了一些代码,以及增加自己 ...
- Magento代码之订单创建流程
Magento代码之订单创建流程 直接看代码吧.下面的代码是如何通过程序创建一个完美订单. <?php require_once 'app/Mage. ...
- ADF 项目创建流程
ADF 项目创建流程: 1.首先建好应用 2.创建model,UI 3.创建EO,VO,AO, VL 4.设置EO的属性 5.新建lov 6.设置VO的View Accessors,并设置Attrib ...
- MFC中SDI程序创建流程的回顾
SDI程序创建流程的回顾 从CWinApp.InitialInstance()开始, 1.首先应用程序对象创建文档模板; CSingleDocTemplate* pDocTemplate; pDocT ...
- 【Java基础】Java类的加载和对象创建流程的详细分析
相信我们在面试Java的时候总会有一些公司要做笔试题目的,而Java类的加载和对象创建流程的知识点也是常见的题目之一.接下来通过实例详细的分析一下. 实例问题 实例代码 Parent类 package ...
- Java类的加载和对象创建流程的详细分析
相信我们在面试Java的时候总会有一些公司要做笔试题目的,而Java类的加载和对象创建流程的知识点也是常见的题目之一.接下来通过实例详细的分析一下: package com.test; public ...
- OpenStack Nova虚拟机创建流程解析
https://yikun.github.io/2017/09/27/OpenStack-Nova%E8%99%9A%E6%8B%9F%E6%9C%BA%E5%88%9B%E5%BB%BA%E6%B5 ...
- 8 云计算系列之Horizon的安装与虚拟机创建流程
preface 在上一章节中,我们可以在无web管理界面上创建并启动虚拟机,虽然可以这么做,但是敲命令太繁琐,所以此时我们可以安装openstack web管理界面,通过web界面的图形化操作open ...
- iOS开发:Framework的创建
转载自:http://jonzzs.cn/2017/06/01/iOS%20开发笔记/[iOS%20开发]将自己的框架打包成%20Framework%20的方法/ 环境:Xcode 8 创建 Fram ...
- k8s 基础 pod创建流程
Pod是Kubernetes中最基本的部署调度单元,可以包含container,逻辑上表示某种应用的一个实例.例如一个web站点应用由前端.后端及数据库构建而成,这三个组件将运行在各自的容器中,那么我 ...
随机推荐
- 【KEIL】User's Guide
µVision User's Guide
- MoeCTF 2023(西电CTF新生赛)WP
个人排名 签到 hello CTFer 1.题目描述: [非西电] 同学注意: 欢迎你来到MoeCTF 2023,祝你玩的开心! 请收下我们送给你的第一份礼物: https://cyberchef.o ...
- Go-并发安全map
- Linux-用户管理-useradd-userdel-id
- JS逆向实战27——pdd的anti_content 分析与逆向
声明 本文章中所有内容仅供学习交流,抓包内容.敏感网址.数据接口均已做脱敏处理,严禁用于商业用途和非法用途,否则由此产生的一切后果均与作者无关,若有侵权,请联系我立即删除! 本文已在微信公众号发布 目 ...
- [转帖]shell脚本使用expect自动化交互登录远程主机进行批量关机
前文 1.目标主机登录用户都为root,且密码一致 2.目标主机开放启动了SSH服务且22号端口可访问(防火墙未进行拦截) 软件介绍 expect Expect是一个用来实现自动和交互式任务进行通信的 ...
- [转帖] q命令-用SQL分析文本文件
https://www.cnblogs.com/codelogs/p/16060830.html 简介# 在Linux上分析文本文件时,一般会使用到grep.sed.awk.sort.uniq等命令, ...
- Oracle存储过程的基本学习
Oracle存储过程的基本学习 摘要 这个简要学习应该会分为上下两部分 第一部分是存储过程的学习. 第二部分是python的学习. 核心目标是查询Oracle数据库中的主键数据. 如果有主键upper ...
- Nginx拆分配置文件的办法
Nginx拆分配置文件的办法 摘要 最近公司使用Nginx进行微服务的路由处理 但是发现随着业务发展, 配置文件越来越复杂. 修改起来也很容易出现错误. 基于此. 想通过拆分配置文件的方式来提高修改效 ...
- [转帖] GC耗时高,原因竟是服务流量小?
原创:扣钉日记(微信公众号ID:codelogs),欢迎分享,转载请保留出处. 简介# 最近,我们系统配置了GC耗时的监控,但配置上之后,系统会偶尔出现GC耗时大于1s的报警,排查花了一些力气,故 ...