Home
last modified time | relevance | path

Searched refs:guest (Results 1 – 25 of 556) sorted by relevance

12345678910>>...23

/openbmc/linux/tools/virtio/ringtest/
H A Dvirtio_ring_0_9.c41 struct guest { struct
52 } guest; variable
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()
107 if (!guest.num_free) in add_inbuf()
111 head = (ring_size - 1) & (guest.avail_idx++); in add_inbuf()
113 head = guest.free_head; in add_inbuf()
[all …]
H A Dring.c59 struct guest { struct
65 } guest; argument
92 guest.avail_idx = 0; in alloc_ring()
93 guest.kicked_avail_idx = -1; in alloc_ring()
94 guest.last_used_idx = 0; in alloc_ring()
103 guest.num_free = ring_size; in alloc_ring()
116 if (!guest.num_free) in add_inbuf()
119 guest.num_free--; in add_inbuf()
120 head = (ring_size - 1) & (guest.avail_idx++); in add_inbuf()
145 unsigned head = (ring_size - 1) & guest.last_used_idx; in get_buf()
[all …]
/openbmc/qemu/qapi/
H A Drun-state.json16 # @finish-migrate: guest is paused to finish the migration process
18 # @inmigrate: guest is paused waiting for an incoming migration. Note
24 # @internal-error: An internal error that prevents further guest
30 # @paused: guest has been paused via the 'stop' command
32 # @postmigrate: guest is paused following a successful 'migrate'
34 # @prelaunch: QEMU was started with -S and guest has not started
36 # @restore-vm: guest is paused to restore VM state
38 # @running: guest is actively running
40 # @save-vm: guest is paused to save the VM state
42 # @shutdown: guest is shut down (and -no-shutdown is in use)
[all …]
H A Ddump.json8 # = Dump guest memory
14 # An enumeration of guest-memory-dump's format.
49 # @dump-guest-memory:
51 # Dump guest's memory to vmcore. It is a synchronous operation that
52 # can take very long depending on the amount of guest memory.
54 # @paging: if true, do paging to get guest's memory mapping. This
58 # of RAM. This can happen for a large guest, or a malicious guest
63 # 1. The guest may be in a catastrophic state or can have
65 # 2. The guest can be in real-mode even if paging is enabled. For
66 # example, the guest uses ACPI to sleep, and ACPI sleep state
[all …]
H A Dmisc-target.json9 # be used if another mechanism to synchronize guest time is in effect,
10 # for example QEMU guest agent's guest-set-time command.
27 # @uninit: The guest is uninitialized.
29 # @launch-update: The guest is currently being launched; plaintext
32 # @launch-secret: The guest is currently being launched; ciphertext
35 # @running: The guest is fully launched or migrated in.
37 # @send-update: The guest is currently being migrated out to another
40 # @receive-update: The guest is currently being migrated from another
53 # An enumeration indicating the type of SEV guest being run.
55 # @sev: The guest is a legacy SEV or SEV-ES guest.
[all …]
/openbmc/qemu/qga/
H A Dqapi-schema.json5 # = QEMU guest agent protocol commands and structs
19 'guest-file-open',
20 'guest-fsfreeze-freeze',
21 'guest-fsfreeze-freeze-list',
22 'guest-fsfreeze-status',
23 'guest-fsfreeze-thaw',
24 'guest-get-time',
25 'guest-set-vcpus',
26 'guest-sync',
27 'guest-sync-delimited' ],
[all …]
/openbmc/qemu/docs/system/i386/
H A Damd-memory-encryption.rst8 (code and data) secured such that only the guest itself has access to the
18 encrypted guest. These SEV commands can be issued via KVM_MEMORY_ENCRYPT_OP
22 support to additionally protect the guest register state. In order to allow a
23 hypervisor to perform functions on behalf of a guest, there is architectural
24 support for notifying a guest's operating system when certain types of VMEXITs
25 are about to occur. This allows the guest to selectively share information with
31 Boot images (such as bios) must be encrypted before a guest can be booted. The
38 For a SEV-ES guest, the ``LAUNCH_UPDATE_VMSA`` command is also used to encrypt the
39 guest register state, or VM save area (VMSA), for all of the guest vCPUs.
42 the firmware. To create this context, guest owner must provide a guest policy,
[all …]
H A Dxen.rst1 Xen HVM guest support
24 Additionally, virtual APIC support can be advertised to the guest through the
33 advertised to a Xen guest. If Hyper-V is also enabled, the Xen identification
44 Setting this property enables the Xen guest support. If Xen version 4.5 or
47 vector support to the guest.
59 Xen grant tables are the means by which a Xen guest grants access to its
62 table can reference 512 pages of guest memory. The default number of frames
63 is 64, allowing for 32768 pages of guest memory to be accessed by PV backends
70 The Xen PCI platform device is enabled automatically for a Xen guest. This
71 allows a guest to unplug all emulated devices, in order to use paravirtual
[all …]
/openbmc/linux/drivers/misc/cxl/
H A Dof.c88 afu->guest->handle = addr; in read_phys_addr()
91 afu->guest->p2n_phys += addr; in read_phys_addr()
92 afu->guest->p2n_size = size; in read_phys_addr()
133 if (read_handle(afu_np, &afu->guest->handle)) in cxl_of_read_afu_handle()
135 pr_devel("AFU handle: 0x%.16llx\n", afu->guest->handle); in cxl_of_read_afu_handle()
190 read_prop_dword(np, "ibm,max-ints-per-process", &afu->guest->max_ints); in cxl_of_read_afu_properties()
191 afu->irqs_max = afu->guest->max_ints; in cxl_of_read_afu_properties()
269 pr_devel("AFU handle: %#llx\n", afu->guest->handle); in cxl_of_read_afu_properties()
271 afu->guest->p2n_phys, afu->guest->p2n_size); in cxl_of_read_afu_properties()
301 adapter->guest->irq_avail = kcalloc(nranges, sizeof(struct irq_avail), in read_adapter_irq_config()
[all …]
H A Dguest.c117 rc = cxl_h_collect_vpd_adapter(adapter->guest->handle, in guest_collect_vpd()
120 rc = cxl_h_collect_vpd(afu->guest->handle, 0, in guest_collect_vpd()
158 return cxl_h_collect_int_info(ctx->afu->guest->handle, ctx->process_token, info); in guest_get_irq_info()
186 rc = cxl_h_read_error_state(afu->guest->handle, &state); in afu_read_error_state()
203 rc = cxl_h_get_fn_error_interrupt(afu->guest->handle, &serr); in guest_slice_irq_err()
214 rc = cxl_h_ack_fn_error_interrupt(afu->guest->handle, serr); in guest_slice_irq_err()
228 for (i = 0; i < adapter->guest->irq_nranges; i++) { in irq_alloc_range()
229 cur = &adapter->guest->irq_avail[i]; in irq_alloc_range()
252 for (i = 0; i < adapter->guest->irq_nranges; i++) { in irq_free_range()
253 cur = &adapter->guest->irq_avail[i]; in irq_free_range()
[all …]
/openbmc/linux/arch/mips/include/asm/
H A Dcpu-features.h666 #define cpu_guest_has_conf1 (cpu_data[0].guest.conf & (1 << 1))
669 #define cpu_guest_has_conf2 (cpu_data[0].guest.conf & (1 << 2))
672 #define cpu_guest_has_conf3 (cpu_data[0].guest.conf & (1 << 3))
675 #define cpu_guest_has_conf4 (cpu_data[0].guest.conf & (1 << 4))
678 #define cpu_guest_has_conf5 (cpu_data[0].guest.conf & (1 << 5))
681 #define cpu_guest_has_conf6 (cpu_data[0].guest.conf & (1 << 6))
684 #define cpu_guest_has_conf7 (cpu_data[0].guest.conf & (1 << 7))
687 #define cpu_guest_has_fpu (cpu_data[0].guest.options & MIPS_CPU_FPU)
690 #define cpu_guest_has_watch (cpu_data[0].guest.options & MIPS_CPU_WATCH)
693 #define cpu_guest_has_contextconfig (cpu_data[0].guest.options & MIPS_CPU_CTXTC)
[all …]
/openbmc/linux/Documentation/virt/kvm/x86/
H A Drunning-nested-guests.rst7 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
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
139 .. note:: If you suspect your L2 (i.e. nested guest) is running slower,
144 Starting a nested guest (x86)
[all …]
H A Dmmu.rst8 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 …]
H A Damd-memory-encryption.rst52 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 …]
H A Dcpuid.rst9 A guest running on a kvm host, can check some of its features using
12 a guest.
65 KVM_FEATURE_PV_UNHALT 7 guest checks this feature bit
69 KVM_FEATURE_PV_TLB_FLUSH 9 guest checks this feature bit
77 KVM_FEATURE_PV_SEND_IPI 11 guest checks this feature bit
85 KVM_FEATURE_PV_SCHED_YIELD 13 guest checks this feature bit
89 KVM_FEATURE_ASYNC_PF_INT 14 guest checks this feature bit
95 KVM_FEATURE_MSI_EXT_DEST_ID 15 guest checks this feature bit
99 KVM_FEATURE_HC_MAP_GPA_RANGE 16 guest checks this feature bit before
103 KVM_FEATURE_MIGRATION_CONTROL 17 guest checks this feature bit before
[all …]
/openbmc/linux/Documentation/arch/x86/
H A Dtdx.rst7 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 …]
/openbmc/qemu/docs/interop/
H A Dvirtio-balloon-stats.rst4 The virtio balloon driver supports guest memory statistics reporting. These
10 guest-stats-polling-interval property. This value can be:
21 polling the guest's balloon driver for new stats in the specified time
24 To retrieve those stats, clients have to query the guest-stats property,
27 * A key named 'stats', containing all available stats. If the guest
44 a buggy guest can't influence its value. The value is 0 if the guest
52 - As noted above, if a guest doesn't support a particular stat its value
53 will always be -1. However, it's also possible that a guest temporarily
57 - Polling can be enabled even if the guest doesn't have stats support
58 or the balloon driver wasn't loaded in the guest. If this is the case
[all …]
/openbmc/linux/tools/perf/Documentation/
H A Dguest-files.txt4 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.
14 --guest-code::
15 Indicate that guest code can be found in the hypervisor process,
H A Dperf-kvm.txt6 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 …]
/openbmc/qemu/hw/ppc/
H A Dspapr_nested.c67 SpaprMachineStateNestedGuest *guest; in spapr_get_nested_guest() local
69 guest = g_hash_table_lookup(spapr->nested.guests, GINT_TO_POINTER(guestid)); in spapr_get_nested_guest()
70 return guest; in spapr_get_nested_guest()
76 SpaprMachineStateNestedGuest *guest; in spapr_get_pate_nested_papr() local
78 guest = spapr_get_nested_guest(spapr, lpid); in spapr_get_pate_nested_papr()
79 if (!guest) { in spapr_get_pate_nested_papr()
83 entry->dw0 = guest->parttbl[0]; in spapr_get_pate_nested_papr()
84 entry->dw1 = guest->parttbl[1]; in spapr_get_pate_nested_papr()
562 static bool spapr_nested_vcpu_check(SpaprMachineStateNestedGuest *guest, in spapr_nested_vcpu_check() argument
575 if (!(vcpuid < guest->nr_vcpus)) { in spapr_nested_vcpu_check()
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-hypervisor-xen6 Type of guest:
7 "Xen": standard guest type on arm
8 "HVM": fully virtualized guest (x86)
9 "PV": paravirtualized guest (x86)
10 "PVH": fully virtualized guest without legacy emulation (x86)
22 "self" The guest can profile itself
23 "hv" The guest can profile itself and, if it is
25 "all" The guest can profile itself, the hypervisor
/openbmc/linux/Documentation/virt/hyperv/
H A Dvmbus.rst5 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)
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
68 shared between the guest and the host, and they follow the standard
[all …]
/openbmc/qemu/docs/system/
H A Dconfidential-guest-support.rst5 guest's memory and other state, meaning that a compromised hypervisor
14 this from other aspects of guest security (such as security against
20 To run a confidential guest you need to add two command line parameters:
22 1. Use ``-object`` to create a "confidential guest support" object. The
25 2. Set the ``confidential-guest-support`` machine parameter to the ID of
32 -machine ...,confidential-guest-support=sev0 \
33 -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1
38 Currently supported confidential guest mechanisms are:
/openbmc/linux/Documentation/virt/kvm/s390/
H A Ds390-pv.rst10 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.
84 instruction text, in order not to leak guest instruction text.
[all …]
/openbmc/qemu/docs/specs/
H A Dpvpanic.rst4 pvpanic device is a simulated device, through which a guest panic
9 and/or polling for guest-panicked RunState, to learn when the pvpanic
27 a guest panic has happened and should be processed by the host
29 a guest panic has happened and will be handled by the guest;
31 the execution of the guest.
33 a regular guest shutdown has happened and should be processed by the host
51 To determine whether guest panic notification is supported.
61 To send a guest panic event.

12345678910>>...23