mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-10-15 20:45:32 +00:00
4fad8c7c64
We will rework NMClient entirely. Then, the synchronous initialization will also use the asynchronous code paths. The difference will be that with synchronous initialization, all D-Bus interaction will be done with an internal GMainContext as current thread default, and that internal context will run until initialization completes. Note that even after initialization completes, it cannot be swapped back to the user's (outer) GMainContext. That is because contexts are essentially the queue for our D-Bus events, and we cannot swap from one queue to the other in a race free manner (or a full resync). In other words, the two contexts are not in sync, so after using the internal context NMClient needs to stick to that (at least, until the name owner gets lost, which gives an opportunity to resync and switch back to the user's main context). We thus need to hook the internal (inner) GMainContext with the user's (outer) context, so when the user iterates the outer context, events on the inner context get dispatched. Add nm_utils_g_main_context_create_integrate_source() to create such a GSource for integrating two contexts. Note that the use-case here is limited: the integrated, inner main context must not be explicitly iterated except from being dispatched by the integrating source. Otherwise, you'd get recursive runs, possible deadlocks and general ugliness. NMClient must show restrain how to use the inner context while it is integrated. |
||
|---|---|---|
| .. | ||
| c-list | ||
| c-rbtree | ||
| c-siphash | ||
| c-stdaux | ||
| n-acd | ||
| n-dhcp4 | ||
| nm-glib-aux | ||
| nm-libnm-core-aux | ||
| nm-libnm-core-intern | ||
| nm-std-aux | ||
| nm-udev-aux | ||
| nm-utils | ||
| systemd | ||
| meson.build | ||
| nm-default.h | ||
| nm-meta-setting.c | ||
| nm-meta-setting.h | ||
| nm-test-libnm-utils.h | ||
| nm-test-utils-impl.c | ||
| nm-version-macros.h.in | ||