vm_tools: system_api: Add vtpm_proxy option

Add a new option to enable the virtio-tpm connection to vtpm daemon.

TEST=vmc start --vtpm-proxy termina

Change-Id: I7de06321d1abd96f4ad9710de186b58b8113aac9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3697690
Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
Commit-Queue: Yi Chou <yich@google.com>
Tested-by: Yi Chou <yich@google.com>
Reviewed-by: Abhishek Bhardwaj <abhishekbh@chromium.org>
GitOrigin-RevId: 16bb6778db35d5582b80706274a7a5d07fad0315
1 file changed
tree: 6bbb207e7c00ea1be42f71744a4dc1edb7653aa7
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  11. OWNERS
  12. README.md
  13. system_api.pc

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. “Required is Forever” and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.