Gitiles
Code Review Sign In
gerrit-dev.monogon.dev / monogon / fa99799583dfc3b485012dd0575287643f568b72
commitfa99799583dfc3b485012dd0575287643f568b72[log] [tgz]
authorSerge Bazanski <serge@nexantic.com>Tue Mar 23 17:29:42 2021 +0100
committerLeopold Schabel <leo@nexantic.com>Thu Apr 01 18:58:25 2021 +0200
tree8bde1e2205ef987181a1bbbb1c8f33fbd29e402d
parent55f01c3c338166f2ca7e67ae5d6c3ae6b7ac75c4 [diff]
third_party/qemu: better explain tb_invalidate_phys_range patch

At a glance, this change looks somewhat scary, and might be interpreted
as an attempt to backdoor qemu.

This better explains what's going on, and adds an extra always-firing
assert to prove that there's nothing up our sleeves, and that this
branch should never be taken in the first place.

Test Plan: Refactor, should be covered by tests.

X-Origin-Diff: phab/D744
GitOrigin-RevId: c86638cf9e90041d2ad19d26715c7d4dd5a43e98
1 file changed
tree: 8bde1e2205ef987181a1bbbb1c8f33fbd29e402d
  1. build/
  2. intellij/
  3. metropolis/
  4. scripts/
  5. third_party/
  6. .bazelignore
  7. .bazelproject
  8. .bazelrc
  9. BUILD
  10. LICENSE
  11. nogo_config.json
  12. README.md
  13. WORKSPACE
README.md

Monogon Monorepo

This is the main repository containing the source code for the Monogon Project.

⚠️ This is pre-release software that happens to be publicly available. Nothing to see here, please move along.

Environment

Our build environment required a working podman or docker environment.

Usage

Spinning up: scripts/create_container.sh

Spinning down: scripts/destroy_container.sh

Running commands: scripts/run_in_container.sh <...>

Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)

IntelliJ

This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.

The following steps are necessary:

  • Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.

  • Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:

    -Dbazel.bep.path=/home/leopold/.cache/bazel-nxt

  • Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.

  • Use File → Import Bazel project... to create a new project from .bazelproject.

After running the first sync, everything should now resolve in the IDE, including generated code.

It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:

bazel run intellij/localconfig $(pwd)

Metropolis

Run a single node cluster

Launch the node:

scripts/bin/bazel run //:launch

Run a kubectl command:

scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe

Run tests:

scripts/bin/bazel test //...