searching for reviewer(jld)
7708abde9c7581d1013843ed19aa4c67edd4e518: Bug 1485696 - add aarch64 windows support to ipc's build_config.h; r=jld
Nathan Froyd <froydnj@mozilla.com> - Thu, 23 Aug 2018 13:27:57 -0400 - rev 831141
Push 118868 by bmo:zjz@zjz.name at Fri, 24 Aug 2018 07:04:39 +0000
Bug 1485696 - add aarch64 windows support to ipc's build_config.h; r=jld
8f5c17ac83aa8cd493b9b051820ccc4d61c46a14: Bug 1457092 - Implement sandboxing on OpenBSD. r=gcp, r=jld
Landry Breuil <landry@openbsd.org> - Thu, 23 Aug 2018 07:35:00 -0400 - rev 831084
Push 118868 by bmo:zjz@zjz.name at Fri, 24 Aug 2018 07:04:39 +0000
Bug 1457092 - Implement sandboxing on OpenBSD. r=gcp, r=jld Add StartOpenBSDSandbox method calling pledge() syscall, and use it where we're sandboxing processes. The pledge subsets are coming from two new prefs: - security.sandbox.pledge.content for the content process - security.sandbox.pledge.main for the main process
8a34342120f17e0bca6336b9a7038f481d6b8588: Bug 1480755 - Add support for new Mesa device probing. r=jld
Gian-Carlo Pascutto <gcp@mozilla.com> - Wed, 22 Aug 2018 01:52:44 +0000 - rev 830754
Push 118854 by bmo:a.beingessner@gmail.com at Wed, 22 Aug 2018 20:13:35 +0000
Bug 1480755 - Add support for new Mesa device probing. r=jld MozReview-Commit-ID: CD9ATGHUOZ1 Differential Revision: https://phabricator.services.mozilla.com/D3910
2f57c7c45953c3c813c607c89320a40192e8e90e: Bug 1480755 - Add support for new Mesa device probing. r?jld draft
Gian-Carlo Pascutto <gcp@mozilla.com> - Tue, 21 Aug 2018 20:10:39 +0200 - rev 830496
Push 118838 by bmo:gpascutto@mozilla.com at Tue, 21 Aug 2018 18:11:26 +0000
Bug 1480755 - Add support for new Mesa device probing. r?jld MozReview-Commit-ID: CD9ATGHUOZ1
6cc53c0f6efec1c590a5b3a6c0019a26e11e6843: Bug 1483309 - the IPC libFuzzer integration can now generated shared memory segments; r=jld,posidron
Alex Gaynor <agaynor@mozilla.com> - Mon, 20 Aug 2018 18:46:05 +0000 - rev 830473
Push 118832 by bmo:ntim.bugs@gmail.com at Tue, 21 Aug 2018 13:33:17 +0000
Bug 1483309 - the IPC libFuzzer integration can now generated shared memory segments; r=jld,posidron Uses the input bytes as metadata + data for shared memory segments. Differential Revision: https://phabricator.services.mozilla.com/D3352
060aa1c7072322d21ec4190fdb07dc1dd89abe0c: Bug 1481139 - fix GMP process IPC channel error on Android. r=jld,njn
John Lin <jolin@mozilla.com> - Fri, 17 Aug 2018 00:06:20 +0000 - rev 830046
Push 118809 by bmo:ntim.bugs@gmail.com at Sat, 18 Aug 2018 10:35:28 +0000
Bug 1481139 - fix GMP process IPC channel error on Android. r=jld,njn Bug 1481139 - p1: handle invalid file descriptors. Bug 1481139 - p2: add dummy fds for GMP process. Two file descriptors were added in bug 1438678 and 1471025 for content/child process but not GMP process, and it breaks the IPC channel on Android. Add dummy values to make it work for now before bug 1440207 clean up the mess. Differential Revision: https://phabricator.services.mozilla.com/D3541
995910a452a2160283d8f60e38c4c5700b3c1bf9: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 823832
Push 117797 by maglione.k@gmail.com at Sun, 29 Jul 2018 00:38:49 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld MozReview-Commit-ID: 4Mod1IdzJBw
33213060b07a4c2586ca42efde8d2c3a12995a8a: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 823831
Push 117797 by maglione.k@gmail.com at Sun, 29 Jul 2018 00:38:49 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld MozReview-Commit-ID: FvGhq6nhIde
0b0c243a1827e193d045d6b3566c87ca87035c48: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 823459
Push 117683 by dgottwald@mozilla.com at Fri, 27 Jul 2018 11:18:41 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld MozReview-Commit-ID: 4Mod1IdzJBw
236b366fdf3731ef95e0ba75b8f24f03181343ee: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 823458
Push 117683 by dgottwald@mozilla.com at Fri, 27 Jul 2018 11:18:41 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld MozReview-Commit-ID: FvGhq6nhIde
6c154f4d9dd93e3dac6045c3b8ead22702071fda: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 823362
Push 117646 by bmo:gl@mozilla.com at Fri, 27 Jul 2018 03:46:44 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld MozReview-Commit-ID: 4Mod1IdzJBw
d0ebb3aa8e0f0946eafc2e7cac4d5cbcf1694e2f: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 823361
Push 117646 by bmo:gl@mozilla.com at Fri, 27 Jul 2018 03:46:44 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld MozReview-Commit-ID: FvGhq6nhIde
89d6559a27ea5681c1415f71eeb837bfadd8351d: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld draft
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 823258
Push 117632 by maglione.k@gmail.com at Thu, 26 Jul 2018 23:37:59 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld MozReview-Commit-ID: 4Mod1IdzJBw
3d9ef99840da37bce0117515b03a165f6821e74d: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 823257
Push 117632 by maglione.k@gmail.com at Thu, 26 Jul 2018 23:37:59 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld MozReview-Commit-ID: FvGhq6nhIde
4fcb3713d88ca833268669fdc8ff2083884619a2: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld draft
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 823200
Push 117608 by maglione.k@gmail.com at Thu, 26 Jul 2018 20:24:30 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r=jld MozReview-Commit-ID: 4Mod1IdzJBw
7528f030506775a0d9b91c03c4a0755ca4424513: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 823199
Push 117608 by maglione.k@gmail.com at Thu, 26 Jul 2018 20:24:30 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r=erahm,jld MozReview-Commit-ID: FvGhq6nhIde
c7ea73331fc83097578c144a9fe5566eecf56088: Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow
Doug Thayer <dothayer@mozilla.com> - Sat, 05 May 2018 15:46:26 -0700 - rev 822048
Push 117269 by bwerth@mozilla.com at Tue, 24 Jul 2018 16:48:19 +0000
Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow There's a lot going on here, but it all fits under the idea of being able to communicate about texture locking statuses without spinning on IsReadLocked. This is a bit of a trade - we could just always allocate/grab a texture from the pool, which would put a smaller cap on the amount of time we can possibly spend when a texture is locked. However, this eats up more CPU and memory than waiting on the textures to unlock, and could take longer, especially if there were a large number of textures which we just need to wait for for a short amount of time. In any case, we very rarely hit the case where we actually need to wait on the sync IPC to the compositor - most of the time the textures are already unlocked. There is also an async IPC call in here, which we make before flushing async paints. This just causes the compositor to check whether the GPU is done with its textures or not and unlock them if it is. This helps us avoid the case where we take a long time painting asynchronously, turn IPC back on at the end of that, and then have to wait for the compositor to to get into TiledLayerBufferComposite::UseTiles before getting a response. Specifically this eliminates several talos regressions which use ASAP mode. Lastly, there seem to be no other cases of static Monitors being used. This seems like it falls under similar use cases as StaticMutexes, so I added it in. I can move it into its own file if we think it might be generally useful in the future. MozReview-Commit-ID: IYQLwUqMxg2
c141fb67cf9a43da6a698a3dd515e51958acc2e7: Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow
Doug Thayer <dothayer@mozilla.com> - Sat, 05 May 2018 15:46:26 -0700 - rev 821732
Push 117187 by bmo:alwu@mozilla.com at Tue, 24 Jul 2018 00:39:37 +0000
Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow There's a lot going on here, but it all fits under the idea of being able to communicate about texture locking statuses without spinning on IsReadLocked. This is a bit of a trade - we could just always allocate/grab a texture from the pool, which would put a smaller cap on the amount of time we can possibly spend when a texture is locked. However, this eats up more CPU and memory than waiting on the textures to unlock, and could take longer, especially if there were a large number of textures which we just need to wait for for a short amount of time. In any case, we very rarely hit the case where we actually need to wait on the sync IPC to the compositor - most of the time the textures are already unlocked. There is also an async IPC call in here, which we make before flushing async paints. This just causes the compositor to check whether the GPU is done with its textures or not and unlock them if it is. This helps us avoid the case where we take a long time painting asynchronously, turn IPC back on at the end of that, and then have to wait for the compositor to to get into TiledLayerBufferComposite::UseTiles before getting a response. Specifically this eliminates several talos regressions which use ASAP mode. Lastly, there seem to be no other cases of static Monitors being used. This seems like it falls under similar use cases as StaticMutexes, so I added it in. I can move it into its own file if we think it might be generally useful in the future. MozReview-Commit-ID: IYQLwUqMxg2
dc52c82903fcb7978a887893fd83d92363cd6d9d: Bug 1466877 Part 4 - Graphics shmem changes for sandboxing, r=jld.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:56:17 +0000 - rev 821393
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1466877 Part 4 - Graphics shmem changes for sandboxing, r=jld.
271b647d862700217f3fdbd9cce4f2b0e1e48274: Bug 1465287 Part 8 - Allow spawning recording/replaying child processes and saving recordings, r=jld,mrbkap.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:52:42 +0000 - rev 821388
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1465287 Part 8 - Allow spawning recording/replaying child processes and saving recordings, r=jld,mrbkap.
dedac27e743a71a9a927a35920dec871be37846a: Bug 1465287 Part 3 - Middleman side of record/replay IPC, r=mccr8,jld.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:49:17 +0000 - rev 821383
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1465287 Part 3 - Middleman side of record/replay IPC, r=mccr8,jld.
fd1477afca0df54d6e9a55c7901a8743bceef02f: Bug 1465287 Part 2 - Child side of record/replay IPC, r=mccr8,jld.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:48:46 +0000 - rev 821382
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1465287 Part 2 - Child side of record/replay IPC, r=mccr8,jld.
d910657e2fc2099d2a3475879ca3f8da052af69a: Bug 1465287 Part 1 - IPC channels, r=mccr8,jld.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:48:08 +0000 - rev 821381
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1465287 Part 1 - IPC channels, r=mccr8,jld.
68935ef593163b30172950789be82ec5730bc6c9: Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Fri, 20 Jul 2018 13:20:42 -0700 - rev 821041
Push 116998 by maglione.k@gmail.com at Fri, 20 Jul 2018 20:53:25 +0000
Bug 1476405: Part 2b - Use default thread size from nsIThreadManager in Linux PlatformThreads. r?jld MozReview-Commit-ID: 4Mod1IdzJBw
b1f0333414b0d716e874efb5e7916227d42b62b4: Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r?erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 821040
Push 116998 by maglione.k@gmail.com at Fri, 20 Jul 2018 20:53:25 +0000
Bug 1476405: Part 2a - Create nsThread wrappers/set names for chromium threads. r?erahm,jld MozReview-Commit-ID: FvGhq6nhIde
b479530b83204ad301a1163f66a71672c88d2cd7: Bug 1476405: Part 2 - Create nsThread wrappers/set names for chromium threads. r?erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Wed, 18 Jul 2018 22:31:30 -0700 - rev 820687
Push 116895 by maglione.k@gmail.com at Fri, 20 Jul 2018 02:54:35 +0000
Bug 1476405: Part 2 - Create nsThread wrappers/set names for chromium threads. r?erahm,jld MozReview-Commit-ID: FvGhq6nhIde
b5ba15b1a70f15b37b494bddc92c569799e1f974: Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow
Doug Thayer <dothayer@mozilla.com> - Sat, 05 May 2018 15:46:26 -0700 - rev 820339
Push 116787 by bmo:bpostelnicu@mozilla.com at Thu, 19 Jul 2018 12:19:59 +0000
Bug 1265824 - Wait on texture handles with IPC r=jld,mattwoodrow There's a lot going on here, but it all fits under the idea of being able to communicate about texture locking statuses without spinning on IsReadLocked. This is a bit of a trade - we could just always allocate/grab a texture from the pool, which would put a smaller cap on the amount of time we can possibly spend when a texture is locked. However, this eats up more CPU and memory than waiting on the textures to unlock, and could take longer, especially if there were a large number of textures which we just need to wait for for a short amount of time. In any case, we very rarely hit the case where we actually need to wait on the sync IPC to the compositor - most of the time the textures are already unlocked. There is also an async IPC call in here, which we make before flushing async paints. This just causes the compositor to check whether the GPU is done with its textures or not and unlock them if it is. This helps us avoid the case where we take a long time painting asynchronously, turn IPC back on at the end of that, and then have to wait for the compositor to to get into TiledLayerBufferComposite::UseTiles before getting a response. Specifically this eliminates several talos regressions which use ASAP mode. Lastly, there seem to be no other cases of static Monitors being used. This seems like it falls under similar use cases as StaticMutexes, so I added it in. I can move it into its own file if we think it might be generally useful in the future. MozReview-Commit-ID: IYQLwUqMxg2
c4cc057e04bd0e1658236df1e059807296cf0f0a: Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:20:55 -0700 - rev 820162
Push 116736 by maglione.k@gmail.com at Thu, 19 Jul 2018 00:58:01 +0000
Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r=erahm,jld The only real way to get memory mapping information on Linux is to read and parse /proc/self/maps, and infer information about a specific pointer based on its contents. This patch adds a helper which parses the entire contents of smaps, and returns an array of objects describing each region. It also updates resident unique reporter to use that helper. Later patches use it to map stack base addresses to VM regions, and report their usage data. MozReview-Commit-ID: 8VUu1kMT77L
d8438eed61d07e3d99aa4f64de7d677d9b6e5d81: Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:28:05 -0700 - rev 820161
Push 116736 by maglione.k@gmail.com at Thu, 19 Jul 2018 00:58:01 +0000
Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld This change stores the base allocation address and actual allocated stack size (as opposed to the requested size, which may be 0), so that we can map them to VM regions in a memory reporter. MozReview-Commit-ID: IZbbyQ9pKHr
e89ebe1f22f28d2b667514cb66d39606136a2f58: Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:20:55 -0700 - rev 820154
Push 116736 by maglione.k@gmail.com at Thu, 19 Jul 2018 00:58:01 +0000
Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r=erahm,jld The only real way to get memory mapping information on Linux is to read and parse /proc/self/maps, and infer information about a specific pointer based on its contents. This patch adds a helper which parses the entire contents of smaps, and returns an array of objects describing each region. It also updates resident unique reporter to use that helper. Later patches use it to map stack base addresses to VM regions, and report their usage data. MozReview-Commit-ID: 8VUu1kMT77L
391b97f0e5c029880d4a1ae697463cfcb8839116: Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:28:05 -0700 - rev 820153
Push 116736 by maglione.k@gmail.com at Thu, 19 Jul 2018 00:58:01 +0000
Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld This change stores the base allocation address and actual allocated stack size (as opposed to the requested size, which may be 0), so that we can map them to VM regions in a memory reporter. MozReview-Commit-ID: IZbbyQ9pKHr
42c69cdbb25b62681d35a1bbf9658f0f675093f4: Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r?erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:20:55 -0700 - rev 819055
Push 116423 by maglione.k@gmail.com at Tue, 17 Jul 2018 01:54:16 +0000
Bug 1475899: Part 3 - Add helper for parsing memory mappings on Linux. r?erahm,jld The only real way to get memory mapping information on Linux is to read and parse /proc/self/maps, and infer information about a specific pointer based on its contents. This patch adds a helper which parses the entire contents of smaps, and returns an array of objects describing each region. It also updates resident unique reporter to use that helper. Later patches use it to map stack base addresses to VM regions, and report their usage data. MozReview-Commit-ID: 8VUu1kMT77L
a2395487770e1362b5bb96ff47d64391d4caf121: Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld draft
Kris Maglione <maglione.k@gmail.com> - Sat, 14 Jul 2018 02:28:05 -0700 - rev 819054
Push 116423 by maglione.k@gmail.com at Tue, 17 Jul 2018 01:54:16 +0000
Bug 1475899: Part 2 - Store stack base pointer for nsThreads on Linux. r=erahm,jld This change stores the base allocation address and actual allocated stack size (as opposed to the requested size, which may be 0), so that we can map them to VM regions in a memory reporter. MozReview-Commit-ID: IZbbyQ9pKHr
a6971931a090c9ebbaa996362db24f33236ad5fb: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 13 Jul 2018 11:06:58 -0700 - rev 818459
Push 116268 by maglione.k@gmail.com at Sat, 14 Jul 2018 02:10:15 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld MozReview-Commit-ID: CTjDzVC9gcD
14e3a4118809564513576000048ad6806065e62d: Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:01:25 -0700 - rev 818458
Push 116268 by maglione.k@gmail.com at Sat, 14 Jul 2018 02:10:15 +0000
Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld Adding or removing an FD from this API currently requires changes in about a half dozen places. Ignoring the Java side of things. This patch changes the API to pass a struct, rather than additional arguments for each FD, so that adding and removing FDs only requires changing one declaration, and the two call sites that add and consume the FDs. MozReview-Commit-ID: CToSEVp1oqP
97f4e15738bc720693ae9c67acae7411f8223383: Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:40:38 -0700 - rev 818457
Push 116268 by maglione.k@gmail.com at Sat, 14 Jul 2018 02:10:15 +0000
Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn This adds an additional file descriptor to the set sent at content process startup, for the read-only preference map that we share between all content processes. This forms the base set of preferences. The other preferences FD contains changes that the content process will need to apply on top of the snapshot. MozReview-Commit-ID: 6hc0HIxFmHg
7c03b7dd00e9675f9ac045ed1ea733eb0486904f: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 13 Jul 2018 11:06:58 -0700 - rev 818353
Push 116255 by bmo:gl@mozilla.com at Fri, 13 Jul 2018 21:44:24 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld MozReview-Commit-ID: CTjDzVC9gcD
ff41551f5ff1b98b72ed771a6f2a3f66a8b79a57: Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:01:25 -0700 - rev 818352
Push 116255 by bmo:gl@mozilla.com at Fri, 13 Jul 2018 21:44:24 +0000
Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld Adding or removing an FD from this API currently requires changes in about a half dozen places. Ignoring the Java side of things. This patch changes the API to pass a struct, rather than additional arguments for each FD, so that adding and removing FDs only requires changing one declaration, and the two call sites that add and consume the FDs. MozReview-Commit-ID: CToSEVp1oqP
46a6f9d0773ba2d756d8801cee79bfa994165d44: Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:40:38 -0700 - rev 818351
Push 116255 by bmo:gl@mozilla.com at Fri, 13 Jul 2018 21:44:24 +0000
Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn This adds an additional file descriptor to the set sent at content process startup, for the read-only preference map that we share between all content processes. This forms the base set of preferences. The other preferences FD contains changes that the content process will need to apply on top of the snapshot. MozReview-Commit-ID: 6hc0HIxFmHg
38f690f30e78764763bb012045073fa781efa691: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld
Kris Maglione <maglione.k@gmail.com> - Fri, 13 Jul 2018 11:06:58 -0700 - rev 817954
Push 116229 by rwood@mozilla.com at Fri, 13 Jul 2018 19:20:22 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r=jld MozReview-Commit-ID: CTjDzVC9gcD
4b7a8a35ed956159e2f443c6211164c0cbf3d926: Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:01:25 -0700 - rev 817953
Push 116229 by rwood@mozilla.com at Fri, 13 Jul 2018 19:20:22 +0000
Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r=jld Adding or removing an FD from this API currently requires changes in about a half dozen places. Ignoring the Java side of things. This patch changes the API to pass a struct, rather than additional arguments for each FD, so that adding and removing FDs only requires changing one declaration, and the two call sites that add and consume the FDs. MozReview-Commit-ID: CToSEVp1oqP
e3bbc87b71af2f2ce1fa8bdf2cf26857c071ba5e: Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:40:38 -0700 - rev 817952
Push 116229 by rwood@mozilla.com at Fri, 13 Jul 2018 19:20:22 +0000
Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r=jld,njn This adds an additional file descriptor to the set sent at content process startup, for the read-only preference map that we share between all content processes. This forms the base set of preferences. The other preferences FD contains changes that the content process will need to apply on top of the snapshot. MozReview-Commit-ID: 6hc0HIxFmHg
ad6f23c34836b2f61797243ef0198805706e4719: Bug 1463587: Part 1 - Add helper class for creating snapshots of shared memory regions. r=jld,erahm draft
Kris Maglione <maglione.k@gmail.com> - Fri, 22 Jun 2018 20:30:23 -0700 - rev 816385
Push 115826 by maglione.k@gmail.com at Wed, 11 Jul 2018 05:19:48 +0000
Bug 1463587: Part 1 - Add helper class for creating snapshots of shared memory regions. r=jld,erahm This class allows us to map a read-write shared memory region, and then safely remap it read-only, so that it can be shared with sandboxed content processes. MozReview-Commit-ID: 2PJMQgOwA4V
7413e7fd2f52bf837910bdb00154ae84d6844368: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:17:48 -0700 - rev 815376
Push 115503 by maglione.k@gmail.com at Sat, 07 Jul 2018 19:50:37 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld MozReview-Commit-ID: CTjDzVC9gcD
2e574a3f1c4234758d9dd2f6b222f64c3aeb1971: Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:01:25 -0700 - rev 815375
Push 115503 by maglione.k@gmail.com at Sat, 07 Jul 2018 19:50:37 +0000
Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r?jld Adding or removing an FD from this API currently requires changes in about a half dozen places. Ignoring the Java side of things. This patch changes the API to pass a struct, rather than additional arguments for each FD, so that adding and removing FDs only requires changing one declaration, and the two call sites that add and comsume the FDs. MozReview-Commit-ID: CToSEVp1oqP
778ba8b508184b21c746449cc9740438a0d3b7ed: Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r?jld,njn draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:40:38 -0700 - rev 815374
Push 115503 by maglione.k@gmail.com at Sat, 07 Jul 2018 19:50:37 +0000
Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r?jld,njn This adds an additional file descriptor to the set sent at content process startup, for the read-only preference map that we share between all content processes. This forms the base set of preferences. The other preferences FD contains changes that the content process will need to apply on top of the snapshot. MozReview-Commit-ID: 6hc0HIxFmHg
096452aaf742794c5595edaa51b24fd28a557a5f: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:17:48 -0700 - rev 814611
Push 115276 by maglione.k@gmail.com at Thu, 05 Jul 2018 19:19:41 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld MozReview-Commit-ID: CTjDzVC9gcD
b046826d67594381200958c5ba900851b983791a: Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:01:25 -0700 - rev 814610
Push 115276 by maglione.k@gmail.com at Thu, 05 Jul 2018 19:19:41 +0000
Bug 1471025: Part 3b - Refactor Android shared FD API to require fewer modifications per change. r?jld Adding or removing an FD from this API currently requires changes in about a half dozen places. Ignoring the Java side of things. This patch changes the API to pass a struct, rather than additional arguments for each FD, so that adding and removing FDs only requires changing one declaration, and the two call sites that add and comsume the FDs. MozReview-Commit-ID: CToSEVp1oqP
0a78bfc09c644a3fbb4cd8247b01cd100652cf25: Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r?jld,njn draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:40:38 -0700 - rev 814609
Push 115276 by maglione.k@gmail.com at Thu, 05 Jul 2018 19:19:41 +0000
Bug 1471025: Part 3a - Pass shared preference map to (non-Android) content processes at startup. r?jld,njn This adds an additional file descriptor to the set sent at content process startup, for the read-only preference map that we share between all content processes. This forms the base set of preferences. The other preferences FD contains changes that the content process will need to apply on top of the snapshot. MozReview-Commit-ID: 6hc0HIxFmHg
67e2e220a47dc523d0be9cd18533e5908aadb64a: Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld draft
Kris Maglione <maglione.k@gmail.com> - Mon, 02 Jul 2018 15:17:48 -0700 - rev 814599
Push 115274 by maglione.k@gmail.com at Thu, 05 Jul 2018 18:42:15 +0000
Bug 1471025: Part 3c - Also pass the shared preference map handle to Android content processes. r?jld MozReview-Commit-ID: CTjDzVC9gcD