Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
, , ,Used in:
Used in:
, ,A request made to the crosvm main process that affects the global aspects of the VM.
The type of the message is determined by which of these oneof fields is present in the protobuf.
Common method for instantiating a new object of any type.
Common method for destroying an object of any type.
Method for a Memory type object for retrieving the dirty bitmap. Only valid if the memory object was created with dirty_log set.
Used in:
Used in:
(message has no fields)
Every message under the Create namespace will instantiate an object with the given ID. The type of object is determined by the oneof constructor field.
Used in:
This message also requires a memfd sent over the socket.
Used in:
Used in:
Used in:
Must be true for the MemoryDirtyLog method to work on this object.
No matter what the type an object is, it can be destroyed using this common method.
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
The in memory representation of certain state, depending on the value of the StateSet.
Used in:
(message has no fields)
Each type refers to certain piece of VM state (such as PIT state). The structure of the data corresponds to the kvm structure.
Used in:
,struct kvm_pic_state
struct kvm_pic_state
struct kvm_ioapic_state
struct kvm_pit_state2
struct kvm_clock_data
This is zero on success, and a negative integer on failure.
The field present here is always the same as the one present in the corresponding MainRequest.
Used in:
Used in:
Depending on the object that was created, an fd might also come from the socket.
Used in:
(message has no fields)
Used in:
(message has no fields)
GetNetConfig messages also return a file descriptor for the tap device.
Used in:
Used in:
(message has no fields)
Used in:
The in memory representation of a state, depending on what StateSet was requested in GetState.
This message should also receive a socket fd per VCPU along with the data from reading this socket. The VcpuRequest/VcpuResponse protocol is run over each of the returned fds.
Used in:
(message has no fields)
Used in:
Used in:
NewMessage receives a socket fd along with the data from reading this socket. The returned socket can be used totally independently of the original socket, and can perform requests and responses independent of the other sockets.
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
A request made for a specific VCPU. These requests are sent over the sockets returned from the GetVcpu MainRequest.
The type of the message is determined by which of these oneof fields is present in the protobuf.
Used in:
(message has no fields)
Used in:
Used in:
The entry data will be returned in the same order as this in the VcpuResponse::GetMsrs::entry_data array.
Used in:
Used in:
Used in:
The data is only necessary for non-write (read) I/O accesses. In all other cases, data is ignored.
The following tracks what deferred set calls to apply.
Used in:
Used in:
Used in:
The in memory representation of a struct kvm_regs, struct kvm_sregs, struct kvm_fpu, struct kvm_debugregs, struct kvm_lapic_state, struct kvm_mp_state, struct kvm_xcrs or struct kvm_vcpu_events depending on the value of the StateSet.
Used in:
(message has no fields)
Each type refers to certain piece of VCPU state (a set registers, or something else). The structure of the data corresponds to the kvm structure.
Used in:
,struct kvm_regs
struct kvm_sregs
struct kvm_fpu
struct kvm_debugregs
struct kvm_lapic_state
struct kvm_mp_state
struct kvm_xcrs
struct kvm_vcpu_events
This message will block until a non-empty response can be sent. The first response will always be an Init wait reason.
Used in:
(message has no fields)
This is zero on success, and a negative integer on failure.
The field present here is always the same as the one present in the corresponding VcpuRequest.
resume was 3 but no longer gets a reply.
Used in:
Used in:
(message has no fields)
Used in:
The order of the entry_data values is the same order as the array of indices given in the corresponding request.
Used in:
The in memory representation of a struct kvm_regs, struct kvm_sregs, struct kvm_fpu, struct kvm_debugregs, struct kvm_lapic_state, struct kvm_mp_state, struct kvm_xcrs or struct kvm_vcpu_events depending on the value of the StateSet.
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
(message has no fields)
Depending on the reason a VCPU has exited, the Wait request will unblock and return a field in the oneof exit. This is called the "wait reason."
Used in:
Used in:
Used in:
This request will always be the first wait reason returend by the first wait request.
Used in:
(message has no fields)
This type of wait reason is only generated if the access occurred on this VCPU on an address previously reserved by a ReserveRange main request.
Used in:
The following can be eagerly provided.
This type of wait reason is only generated after a PauseVcpus request on this VCPU.
Used in:
Used in:
(message has no fields)
Used in:
(message has no fields)
Used in:
2-16 buckets of memory working set.
actual size of balloon in bytes.
Used in:
age of bucket in milliseconds.
file-back memory, in bytes.
anonymous memory, in bytes.