vm_tools: concierge: add option to lock guest pages.

This adds parameters to lock guest pages upon request.
This is done in support of go/host-assisted-vm-swap (google-only).

Matching crosvm change: https://crrev.com/c/3725731

BUG=b:236210703

TEST=manual startup, roblox+instagram and various chrome sessions,
     with and without guest page locks. Verify that memory
     is locked and that balloon inflation results in correct
     freeing.

Change-Id: Iadddd98f57fe2a25898191fa82ce1da163b50ef3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3720525
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Auto-Submit: Alexandre Marciano Gimenez <raging@google.com>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
Commit-Queue: Alexandre Marciano Gimenez <raging@google.com>
Tested-by: Alexandre Marciano Gimenez <raging@google.com>
NOKEYCHECK=True
GitOrigin-RevId: efbc710d1666e43d45df8fc73afb2503e788e568
1 file changed
tree: 2c8a58cedb6fd4599bff0c1be8cff30070ca0a0c
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. LICENSE
  11. OWNERS
  12. README.md
  13. system_api.pc
README.md

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.