[NewEV] Making SystemSignals Service Run Out-of-process on Mac and Linux

Before this CL, the SystemSignals service was only running
out-of-process on Windows. However, some signals will require loading
file and heavier computing, such as going through all pids, on Mac and
Linux and, for stability purposes, should be run in a child process.

Most of the changes in this CL are about moving files from:
//components/device_signals/core/common
To
//components/device_signals/core/system_signals
Since these files should now solely be used in the system_signals child
process.

The main non-rename changes that are happening are:
- //chrome/utility/services.cc
  - This will now return a service on Mac and Linux as well.
- Pulling-up some common (win|mac|linux)system_signals_service into a
  base_system_signals_service.
- Consolidating some BUILD.gn files into one at
  //chrome/services/system_signals/BUILD.gn

Bug: b:231472924
Change-Id: I9a6e7a24875caad91828d73200276b7b81550ce8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3810653
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Hamda Mare <hmare@google.com>
Cr-Commit-Position: refs/heads/main@{#1031655}
51 files changed
tree: 2091cbca2e029e2d8db65c8236346a235e2669f3
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.