| /kernel/linux/linux-5.10/arch/s390/kvm/ |
| D | gaccess.h | 3 * access guest memory
20 * kvm_s390_real_to_abs - convert guest real address to guest absolute address
21 * @prefix - guest prefix
22 * @gra - guest real address
24 * Returns the guest absolute address that corresponds to the passed guest real
37 * kvm_s390_real_to_abs - convert guest real address to guest absolute address
38 * @vcpu - guest virtual cpu
39 * @gra - guest real address
41 * Returns the guest absolute address that corresponds to the passed guest real
42 * address @gra of a virtual guest cpu by applying its prefix.
[all …]
|
| /kernel/linux/linux-6.6/arch/s390/kvm/ |
| D | gaccess.h | 3 * access guest memory
20 * kvm_s390_real_to_abs - convert guest real address to guest absolute address
21 * @prefix - guest prefix
22 * @gra - guest real address
24 * Returns the guest absolute address that corresponds to the passed guest real
37 * kvm_s390_real_to_abs - convert guest real address to guest absolute address
38 * @vcpu - guest virtual cpu
39 * @gra - guest real address
41 * Returns the guest absolute address that corresponds to the passed guest real
42 * address @gra of a virtual guest cpu by applying its prefix.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| D | mmu.rst | 8 for presenting a standard x86 mmu to the guest, while translating guest
14 the guest should not be able to determine that it is running
19 the guest must not be able to touch host memory not assigned
28 Linux memory management code must be in control of guest memory
32 report writes to guest memory to enable live migration
47 gfn guest frame number
48 gpa guest physical address
49 gva guest virtual address
50 ngpa nested guest physical address
51 ngva nested guest virtual address
[all …]
|
| D | running-nested-guests.rst | 5 A nested guest is the ability to run a guest inside another guest (it
7 example is a KVM guest that in turn runs on a KVM guest (the rest of
13 | (Nested Guest) | | (Nested Guest) |
17 | L1 (Guest Hypervisor) |
31 - L1 – level-1 guest; a VM running on L0; also called the "guest
34 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
44 (guest hypervisor), L3 (nested guest).
59 Provider, using nested KVM lets you rent a large enough "guest
60 hypervisor" (level-1 guest). This in turn allows you to create
64 - Live migration of "guest hypervisors" and their nested guests, for
[all …]
|
| D | amd-memory-encryption.rst | 50 The SEV guest key management is handled by a separate processor called the AMD
53 encrypting bootstrap code, snapshot, migrating and debugging the guest. For more
94 context. To create the encryption context, user must provide a guest policy,
105 __u32 policy; /* guest's policy */
107 … __u64 dh_uaddr; /* userspace address pointing to the guest owner's PDH key */
110 … __u64 session_addr; /* userspace address which points to the guest session information */
125 of the memory contents that can be sent to the guest owner as an attestation
145 data encrypted by the KVM_SEV_LAUNCH_UPDATE_DATA command. The guest owner may
146 wait to provide the guest with confidential information until it can verify the
147 measurement. Since the guest owner knows the initial contents of the guest at
[all …]
|
| D | s390-pv.rst | 10 access VM state like guest memory or guest registers. Instead, the
15 Each guest starts in non-protected mode and then may make a request to
16 transition into protected mode. On transition, KVM registers the guest
20 The Ultravisor will secure and decrypt the guest's boot memory
22 starts/stops and injected interrupts while the guest is running.
24 As access to the guest's state, such as the SIE state description, is
29 reduce exposed guest state.
40 field (offset 0x54). If the guest cpu is not enabled for the interrupt
50 access to the guest memory.
72 Secure Interception General Register Save Area. Guest GRs and most of
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/kvm/x86/ |
| D | mmu.rst | 8 for presenting a standard x86 mmu to the guest, while translating guest
14 the guest should not be able to determine that it is running
19 the guest must not be able to touch host memory not assigned
28 Linux memory management code must be in control of guest memory
32 report writes to guest memory to enable live migration
47 gfn guest frame number
48 gpa guest physical address
49 gva guest virtual address
50 ngpa nested guest physical address
51 ngva nested guest virtual address
[all …]
|
| D | running-nested-guests.rst | 7 A nested guest is the ability to run a guest inside another guest (it
9 example is a KVM guest that in turn runs on a KVM guest (the rest of
15 | (Nested Guest) | | (Nested Guest) |
19 | L1 (Guest Hypervisor) |
33 - L1 – level-1 guest; a VM running on L0; also called the "guest
36 - L2 – level-2 guest; a VM running on L1, this is the "nested guest"
46 (guest hypervisor), L3 (nested guest).
61 Provider, using nested KVM lets you rent a large enough "guest
62 hypervisor" (level-1 guest). This in turn allows you to create
66 - Live migration of "guest hypervisors" and their nested guests, for
[all …]
|
| D | amd-memory-encryption.rst | 52 The SEV guest key management is handled by a separate processor called the AMD
55 encrypting bootstrap code, snapshot, migrating and debugging the guest. For more
101 context. To create the encryption context, user must provide a guest policy,
112 __u32 policy; /* guest's policy */
114 … __u64 dh_uaddr; /* userspace address pointing to the guest owner's PDH key */
117 … __u64 session_addr; /* userspace address which points to the guest session information */
132 of the memory contents that can be sent to the guest owner as an attestation
152 data encrypted by the KVM_SEV_LAUNCH_UPDATE_DATA command. The guest owner may
153 wait to provide the guest with confidential information until it can verify the
154 measurement. Since the guest owner knows the initial contents of the guest at
[all …]
|
| D | msr.rst | 25 in guest RAM. This memory is expected to hold a copy of the following
40 guest has to check version before and after grabbing
64 guest RAM, plus an enable bit in bit 0. This memory is expected to hold
87 guest has to check version before and after grabbing
127 coordinated between the guest and the hypervisor. Availability
139 | | | guest vcpu has been paused by |
196 which must be in guest RAM and must be zeroed. This memory is expected
221 a token that will be used to notify the guest when missing page becomes
225 is currently supported, when set, it indicates that the guest is dealing
227 'flags' is '0' it means that this is regular page fault. Guest is
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | tdx.rst | 7 Intel's Trust Domain Extensions (TDX) protect confidential guest VMs from
8 the host and physical attacks by isolating the guest register state and by
9 encrypting the guest memory. In TDX, a special module running in a special
10 mode sits between the host and the guest and manages the guest/host
13 Since the host cannot directly access guest registers or memory, much
14 normal functionality of a hypervisor must be moved into the guest. This is
16 guest kernel. A #VE is handled entirely inside the guest kernel, but some
20 guest to the hypervisor or the TDX module.
64 indicates a bug in the guest. The guest may try to handle the #GP with a
70 The "just works" MSRs do not need any special guest handling. They might
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/hyperv/ |
| D | vmbus.rst | 5 VMbus is a software construct provided by Hyper-V to guest VMs. It
7 devices that Hyper-V presents to guest VMs. The control path is
8 used to offer synthetic devices to the guest VM and, in some cases,
10 channels for communicating between the device driver in the guest VM
12 signaling primitives to allow Hyper-V and the guest to interrupt
16 entry in a running Linux guest. The VMbus driver (drivers/hv/vmbus_drv.c)
37 Guest VMs may have multiple instances of the synthetic SCSI
47 the device in the guest VM. For example, the Linux driver for the
65 guest, and the "out" ring buffer is for messages from the guest to
67 viewed by the guest side. The ring buffers are memory that is
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | perf.rst | 23 The kernel runs at EL2 with VHE and EL1 without. Guest kernels always run
29 For the guest this attribute will exclude EL1. Please note that EL2 is
30 never counted within a guest.
43 guest/host transitions.
45 For the guest this attribute has no effect. Please note that EL2 is
46 never counted within a guest.
52 These attributes exclude the KVM host and guest, respectively.
57 The KVM guest may run at EL0 (userspace) and EL1 (kernel).
61 must enable/disable counting on the entry and exit to the guest. This is
65 exiting the guest we disable/enable the event as appropriate based on the
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-kvm.txt | 6 perf-kvm - Tool to trace/measure kvm guest os
11 'perf kvm' [--host] [--guest] [--guestmount=<path>
14 'perf kvm' [--host] [--guest] [--guestkallsyms=<path> --guestmodules=<path>
23 a performance counter profile of guest os in realtime
28 default behavior of perf kvm as --guest, so if neither --host nor --guest
29 is input, the perf data file name is perf.data.guest. If --host is input,
31 perf.data.host, please input --host --no-guest. The behaviors are shown as
33 Default('') -> perf.data.guest
35 --guest -> perf.data.guest
36 --host --guest -> perf.data.kvm
[all …]
|
| /kernel/linux/linux-6.6/tools/virtio/ringtest/ |
| D | virtio_ring_0_9.c | 41 struct guest { struct
52 } guest; argument
78 guest.avail_idx = 0; in alloc_ring()
79 guest.kicked_avail_idx = -1; in alloc_ring()
80 guest.last_used_idx = 0; in alloc_ring()
83 guest.free_head = 0; in alloc_ring()
89 guest.num_free = ring_size; in alloc_ring()
98 /* guest side */
107 if (!guest.num_free) in add_inbuf()
111 head = (ring_size - 1) & (guest.avail_idx++); in add_inbuf()
[all …]
|
| /kernel/linux/linux-5.10/tools/virtio/ringtest/ |
| D | virtio_ring_0_9.c | 41 struct guest { struct
52 } guest; argument
78 guest.avail_idx = 0; in alloc_ring()
79 guest.kicked_avail_idx = -1; in alloc_ring()
80 guest.last_used_idx = 0; in alloc_ring()
83 guest.free_head = 0; in alloc_ring()
89 guest.num_free = ring_size; in alloc_ring()
98 /* guest side */
107 if (!guest.num_free) in add_inbuf()
111 head = (ring_size - 1) & (guest.avail_idx++); in add_inbuf()
[all …]
|
| /kernel/linux/linux-6.6/arch/mips/kvm/ |
| D | tlb.c | 92 * Sets the root GuestID to match the current guest GuestID, for TLB operation
121 /* Set root GuestID for root probe and write of guest TLB entry */ in kvm_vz_host_tlb_inv()
153 * kvm_vz_guest_tlb_lookup() - Lookup a guest VZ TLB mapping.
155 * @gpa: Guest virtual address in a TLB mapped guest segment.
156 * @gpa: Pointer to output guest physical address it maps to.
158 * Converts a guest virtual address in a guest TLB mapped segment to a guest
159 * physical address, by probing the guest TLB.
161 * Returns: 0 if guest TLB mapping exists for @gva. *@gpa will have been
163 * -EFAULT if no guest TLB mapping exists for @gva. *@gpa may not
175 /* Probe the guest TLB for a mapping */ in kvm_vz_guest_tlb_lookup()
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/vboxvideo/ |
| D | vboxvideo.h | 10 * The last 4096 bytes of the guest VRAM contains the generic info for all
24 * The Virtual Graphics Adapter information in the guest VRAM is stored by the
25 * guest video driver using structures prepended by VBOXVIDEOINFOHDR.
27 * When the guest driver writes dword 0 to the VBE_DISPI_INDEX_VBOX_VIDEO
30 * actual information chain. That way the guest driver can have some
40 * The guest driver writes dword 0xffffffff to the VBE_DISPI_INDEX_VBOX_VIDEO
46 * The guest writes the VBE_DISPI_INDEX_VBOX_VIDEO index register, the
67 * Guest starts writing to the buffer by initializing a record entry in the
69 * written. As data is written to the ring buffer, the guest increases
146 /* guest->host commands */
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vboxvideo/ |
| D | vboxvideo.h | 10 * The last 4096 bytes of the guest VRAM contains the generic info for all
24 * The Virtual Graphics Adapter information in the guest VRAM is stored by the
25 * guest video driver using structures prepended by VBOXVIDEOINFOHDR.
27 * When the guest driver writes dword 0 to the VBE_DISPI_INDEX_VBOX_VIDEO
30 * actual information chain. That way the guest driver can have some
40 * The guest driver writes dword 0xffffffff to the VBE_DISPI_INDEX_VBOX_VIDEO
46 * The guest writes the VBE_DISPI_INDEX_VBOX_VIDEO index register, the the
67 * Guest starts writing to the buffer by initializing a record entry in the
69 * written. As data is written to the ring buffer, the guest increases
146 /* guest->host commands */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/virt/kvm/s390/ |
| D | s390-pv.rst | 10 access VM state like guest memory or guest registers. Instead, the
15 Each guest starts in non-protected mode and then may make a request to
16 transition into protected mode. On transition, KVM registers the guest
20 The Ultravisor will secure and decrypt the guest's boot memory
22 starts/stops and injected interrupts while the guest is running.
24 As access to the guest's state, such as the SIE state description, is
29 reduce exposed guest state.
40 field (offset 0x54). If the guest cpu is not enabled for the interrupt
50 access to the guest memory.
72 Secure Interception General Register Save Area. Guest GRs and most of
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 10 allow guest partitions on the same server to share devices that would
20 driver set are commonly referred to as "guest drivers" or "client drivers".
22 Linux guest environment (e.g., block, network, or input), and are collectively
27 with each guest partition sharing that device through an area of shared memory
32 Each virtual device requires exactly 1 dedicated channel, which the guest
40 because this requires no specific support in the guest partitions, it will
45 guest, the already-existing efifb Linux driver is used to provide guest
47 provide a guest graphics console are for keyboard and mouse (via visorinput).
86 special control channel called the "controlvm channel" (each guest partition
197 clientpartition handle identifying the guest (client) side
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | guest-files.txt | 4 Guest OS /proc/kallsyms file copy. perf reads it to get guest
5 kernel symbols. Users copy it out from guest OS.
8 Guest OS /proc/modules file copy. perf reads it to get guest
9 kernel module information. Users copy it out from guest OS.
12 Guest OS kernel vmlinux.
14 --guest-code::
15 Indicate that guest code can be found in the hypervisor process,
|
| /kernel/linux/linux-5.10/arch/mips/kvm/ |
| D | tlb.c | 94 kvm_info("Guest TLBs:\n"); in kvm_mips_dump_guest_tlbs()
95 kvm_info("Guest EntryHi: %#lx\n", kvm_read_c0_guest_entryhi(cop0)); in kvm_mips_dump_guest_tlbs()
200 kvm_debug("%s: Invalidated guest user entryhi %#lx @ idx %d\n", in kvm_mips_host_tlb_inv()
204 kvm_debug("%s: Invalidated guest kernel entryhi %#lx @ idx %d\n", in kvm_mips_host_tlb_inv()
230 * Sets the root GuestID to match the current guest GuestID, for TLB operation
259 /* Set root GuestID for root probe and write of guest TLB entry */ in kvm_vz_host_tlb_inv()
291 * kvm_vz_guest_tlb_lookup() - Lookup a guest VZ TLB mapping.
293 * @gpa: Guest virtual address in a TLB mapped guest segment.
294 * @gpa: Ponter to output guest physical address it maps to.
296 * Converts a guest virtual address in a guest TLB mapped segment to a guest
[all …]
|
| /kernel/linux/linux-6.6/drivers/misc/vmw_vmci/ |
| D | vmci_route.c | 34 * guest. in vmci_route()
49 * If this message already came from a guest then we in vmci_route()
57 * We must be acting as a guest in order to send to in vmci_route()
87 * If it is not from a guest but we are acting as a in vmci_route()
88 * guest, then we need to send it down to the host. in vmci_route()
100 * an "outer host" through the guest device. in vmci_route()
122 * Otherwise we already received it from a guest and in vmci_route()
132 * If it came from a guest then it must have a in vmci_route()
149 * a guest. in vmci_route()
152 /* It will have a context if it is meant for a guest. */ in vmci_route()
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/vmw_vmci/ |
| D | vmci_route.c | 34 * guest. in vmci_route()
49 * If this message already came from a guest then we in vmci_route()
57 * We must be acting as a guest in order to send to in vmci_route()
87 * If it is not from a guest but we are acting as a in vmci_route()
88 * guest, then we need to send it down to the host. in vmci_route()
100 * an "outer host" through the guest device. in vmci_route()
122 * Otherwise we already received it from a guest and in vmci_route()
132 * If it came from a guest then it must have a in vmci_route()
149 * a guest. in vmci_route()
152 /* It will have a context if it is meant for a guest. */ in vmci_route()
[all …]
|