Android MC @ 2018 Report

	A	B	C	D	E
1
2		Android MC 2018 Progress Report
3
4	Lead	Topic	Wins	Work	Loses
5
6	Martijn	Symbol Namespace	positive response, no objections	get the patches in :-) Figure out granularity of namespaces
7	Suren	Android usage of memory pressure signals in userspace low memory killer	presented future plans, no major complains	need to consider the feedback
8	Christian	Dynamically Allocated Binder Devices
9	Patrick	How to be better citizens: from changes review to changes testing	presented a simple setup to evaluate power/perf effects of proposed patches	verify with Linaro if what they have is a suitable implementation of the proposed approach	limited interest in integrating such a solution in AOSP's gerrit
10	Daniel/Paul	Userdata fs Checkpointing	Presented checkpoint concept - people understood the need and were supportive	Attempt to reconcile our approach with more traditional checkpoint approaches
11	David	LVM, device mapper and dm-linear	Small, contained device mapper library was added in Android for this and for the most part this went without any doubts / concerns.	None needed. LVM may need re-consideration. However, its a big codebase to pull into Anroid compared to the small library that we have right now.	Couple of assumptions made about LVM metadata turned out to be wrong.
12	Sandeep	Readiness of ARM64 Kernels for Running on Any Device	ARM64 kernels has always been ready - confirmed	Expected work in IOMMU and potentially clock framework.
13	Joel	How to get ashmem out of staging	Deleting pin/unpin code from ashmem (Chrome study still in progress, but should be no problem doing that)	Make a plan for handling of /dev/ashmem opencoded usages
14	Sandeep	The Android DTS fstab node work Treble	Everybody agreed to the proposed solution and it doesn't need to be altered in AOSP.
15	Alistair	DRM/KMS for Android	everybody agrees we should do it	need to get i-g-t tests into aosp, and get at least one aosp device passing them
16	Laura	ION upstreaming update	getting the location for cache ops is a very hard problem	Going to try again with a wrapper to call cache ops, hopefully more successfully. Reviewing uncached patches.
17	Alistair	Cuttlefish	lots of interest in using cuttlefish	should add new virtio_gpu_3d enum for non-virgl control stream format. need to enable new gpu architecture. should have something better than emulated camera (virtio video?)
18
19		Notes:
20		"Wins" is any progress or agreement that has been made about the topic during the MC
21		"Work" is any work that was identified as being required to be done as a result of MC discussion
22		"Loses" is for highlighting issues which are clearly at an impass and are not forseen to be resolvable in their current form/approach
23		It's suggested to put major takeaways in bold. If, for example, within the 3 categories a given item is important enough that it should stand out in its meaningfulness (especially to outside observers) then making it bold (or underline) will help making it obvious "at a glance". For instance, if "Work" describes "Mergeable under condition that feature foo is made to use existing kernel API" and that's deemed an important advancement then that might be a good reason to put it in bold. Possibly end of week readouts should just call out the items in bold.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100