vm_tools: Use a dedicated dbus thread in concierge

This is needed to support async vm_concierge

BUG=b:151695024
TEST=Run crostini.*, pita.Boot
TEST=Launch terminal, close terminal, reseat ethernet cable, and relaunch terminal

Cq-Depend: chromium:2568914, chromium:2562038, chromium:2574150
Change-Id: I6a6b1adf0ecc83fd465d32bb213d42d2bc63df95
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/2549481
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Commit-Queue: Woody Chow <woodychow@google.com>
Tested-by: Woody Chow <woodychow@google.com>
GitOrigin-RevId: af2fe252bed3130cd6d5137b6c1969193f810ff1
2 files changed
tree: a0830d2676185cf91726c060c3d9b5c08b3e60da
  1. brillo/
  2. install_attributes/
  3. policy/
  4. BUILD.gn
  5. libpolicy.ver
  6. OWNERS
  7. PRESUBMIT.cfg
  8. README.md
  9. testrunner.cc
README.md

libbrillo: platform utility library

libbrillo is a shared library meant to hold common utility code that we deem useful for platform projects. It supplements the functionality provided by libbase/libchrome since that project, by design, only holds functionality that Chromium (the browser) needs. As a result, this tends to be more OS-centric code.

AOSP Usage

This project is also used by Update Engine which is maintained in AOSP. However, AOSP doesn't use this codebase directly, it maintains its own libbrillo fork.

To help keep the projects in sync, we have a gsubtree set up on our GoB: https://chromium.googlesource.com/chromiumos/platform2/libbrillo/

This allows AOSP to cherry pick or merge changes directly back into their fork.