I found that the second surfaceflinger start at
DisplayHardware::init().
void DisplayHardware::init(uint32_t dpy)
{
mNativeWindow = new FramebufferNativeWindow();
...
}
The second surfaceflinger thread is FramebufferNativeWindow.
That manages only two buffers (the front and back buffer).
Thank all for attentions.
On 8월25일, 오후5시38분, Jae-Hong Bae <[email protected]> wrote:
> Hi, all
> I am inspecting a process/thread in theandroid-platform(FROYO).
> I found weird thing that there istwosurfaceflingerthread.
> I know the first SurfaceFinger start point at booting time but can't
> find the secondSurfaceFlingerstart point.
> My question is
> (1) Where is the secondSurfaceFlingerstarted ?
> (2) Whatdoesthe secondSurfaceFlingerdo ? (What is the
> 2ndSurfaceFlinger'srole?)Doesanyone know this?
> I attach my system log below.
> Thanks for your attention.
>
> ---------------------------------------------------------------------------------------------------
> $ ps
> ...
> system 1379 1266 252592 37996 ffffffff 00000000 S system_server
> ...
> $ cat /proc/1379/task/*/stat
> 1379 (system_server) S 1266 1266 0 0 -1 4194624 1949 0 96 0 41 9 0 0
> 20 0 59 0 1723 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 17 0 0 0 0 0 0
> 1380 (HeapWorker) S 1266 1266 0 0 -1 4194368 462 0 0 0 70 4 0 0 20 0
> 59 0 1723 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1381 (Signal Catcher) S 1266 1266 0 0 -1 4194368 4 0 0 0 0 0 0 0 20 0
> 59 0 1723 258654208 9575 4294967295 32768 38168 0 0 0 0 4096 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1382 (JDWP) S 1266 1266 0 0 -1 4194368 166 0 1 0 0 0 0 0 20 0 59 0
> 1724 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1383 (Compiler) S 1266 1266 0 0 -1 4194368 59 0 9 0 79 16 0 0 20 0 59
> 0 1724 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1384 (Binder Thread #1) S 1266 1266 0 0 -1 4194624 262 0 2 0 14 9 0 0
> 20 0 59 0 1725 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1385 (Binder Thread #2) S 1266 1266 0 0 -1 4194624 2990 0 1 0 17 21 0
> 0 20 0 59 0 1726 258654208 9575 4294967295 32768 38168 0 0 0 0 4612
> 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1386 (SurfaceFlinger) S 1266 1266 0 0 -1 4194624 401 0 154 0 358 657 0
> 0 12 -8 59 0 1743 258654208 9575 4294967295 32768 38168 0 0 0 0
> 1073748484 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1390 (DisplayEventThread) S 1266 1266 0 0 -1 4194624 0 0 0 0 0 0 0 0
> 12 -8 59 0 1751 258654208 9575 4294967295 32768 38168 0 0 0 0 4612
> 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1391 (SurfaceFlinger) S 1266 1266 0 0 -1 4194368 0 0 0 0 8 68 0 0 12
> -8 59 0 1752 258654208 9575 4294967295 32768 38168 0 0 0 0 1073748484
> 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1399 (er.ServerThread) S 1266 1266 0 0 -1 4194624 13087 0 2407 0 818
> 140 0 0 18 -2 59 0 1774 258654208 9575 4294967295 32768 38168 0 0 0 0
> 4612 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1403 (ActivityManager) S 1266 1266 0 0 -1 4194624 1307 0 24 0 39 5 0 0
> 18 -2 59 0 1785 258654208 9575 4294967295 32768 38168 0 0 0 0 4612
> 4096 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> 1406 (ProcessStats) S 1266 1266 0 0 -1 4194368 52 0 0 0 56 94 0 0 20 0
> 59 0 1830 258654208 9575 4294967295 32768 38168 0 0 0 0 4612 4096
> 1073777896 4294967295 0 0 -1 0 0 0 0 0 0
> ...
> ---------------------------------------------------------------------------------------------------
> system_server process pid is 1379. system_server process
> hastwosurfaceflingerthread(tid:1386, tid:1391)
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
