mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-05 18:20:34 +00:00
ARCHITECTURE.md: fix repeated word typo
Bug: N/A Test: N/A Change-Id: Ibd4b4077eb0e9c83e0907fbb63d05642f6684f9f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3488163 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Steven Moreland <smoreland@google.com>
This commit is contained in:
parent
45f1a419d4
commit
a7415e04bd
1 changed files with 1 additions and 1 deletions
|
@ -51,7 +51,7 @@ separation in case a device becomes compromised by a malicious guest. For exampl
|
|||
that is able to allocate MSI routes would not be able to use the same socket to (de)register guest
|
||||
memory. During the device initialization stage, each device that requires some aspect of VM control
|
||||
will have a constructor that requires the corresponding control socket. The control socket will get
|
||||
preserved when the device is sandboxed and and the other side of the socket will be waited on in the
|
||||
preserved when the device is sandboxed and the other side of the socket will be waited on in the
|
||||
main process's control loop.
|
||||
|
||||
The socket exposed by crosvm with the `--socket` command line argument is another form of the VM
|
||||
|
|
Loading…
Reference in a new issue