Home
last modified time | relevance | path

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

12345678910

/linux/tools/virtio/ringtest/
A Dvirtio_ring_0_9.c41 struct guest { struct
52 } guest; argument
78 guest.avail_idx = 0; in alloc_ring()
83 guest.free_head = 0; in alloc_ring()
107 if (!guest.num_free) in add_inbuf()
113 head = guest.free_head; in add_inbuf()
115 guest.num_free--; in add_inbuf()
192 guest.num_free++; in get_buf()
193 guest.last_used_idx++; in get_buf()
234 guest.avail_idx, in kick_available()
[all …]
A Dring.c59 struct guest { struct
65 } guest; variable
92 guest.avail_idx = 0; 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()
159 guest.num_free++; in get_buf()
160 guest.last_used_idx++; in get_buf()
195 guest.avail_idx, in kick_available()
[all …]
/linux/drivers/misc/cxl/
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()
191 afu->irqs_max = afu->guest->max_ints; in cxl_of_read_afu_properties()
271 afu->guest->p2n_phys, afu->guest->p2n_size); in cxl_of_read_afu_properties()
331 kfree(adapter->guest->irq_avail); in read_adapter_irq_config()
332 adapter->guest->irq_avail = NULL; in read_adapter_irq_config()
403 if (adapter->guest->status == NULL) in cxl_of_read_adapter_properties()
409 adapter->guest->vendor = val; in cxl_of_read_adapter_properties()
413 adapter->guest->device = val; in cxl_of_read_adapter_properties()
[all …]
A Dguest.c668 kfree(afu->guest); in guest_release_afu()
811 if (!(afu->p2n_mmio = ioremap(afu->guest->p2n_phys, afu->guest->p2n_size))) { in guest_map_slice_regs()
995 afu->guest->parent = afu; in cxl_guest_init_afu()
996 afu->guest->handle_err = true; in cxl_guest_init_afu()
1015 kfree(afu->guest); in cxl_guest_init_afu()
1027 afu->guest->handle_err = false; in cxl_guest_remove_afu()
1050 if (adapter->guest) { in free_adapter()
1058 kfree(adapter->guest->status); in free_adapter()
1059 kfree(adapter->guest); in free_adapter()
1114 adapter->guest->pdev = pdev; in cxl_guest_init_adapter()
[all …]
A Dflash.c190 unwa->unit_address = cpu_to_be64(adapter->guest->handle); in update_devicetree()
244 header->vendor = cpu_to_be16(adapter->guest->vendor); in handle_image()
245 header->device = cpu_to_be16(adapter->guest->device); in handle_image()
311 rc = fct(adapter->guest->handle, virt_to_phys(le), entries, in handle_image()
334 cxl_h_reset_adapter(adapter->guest->handle); in transfer_image()
343 cxl_h_reset_adapter(adapter->guest->handle); in transfer_image()
352 cxl_h_reset_adapter(adapter->guest->handle); in transfer_image()
500 cxl_h_reset_adapter(adapter->guest->handle); in device_close()
517 cdev_del(&adapter->guest->cdev); in cxl_guest_remove_chardev()
526 cdev_init(&adapter->guest->cdev, &fops); in cxl_guest_add_chardev()
[all …]
/linux/arch/mips/include/asm/
A Dcpu-features.h649 #define cpu_guest_has_conf1 (cpu_data[0].guest.conf & (1 << 1))
652 #define cpu_guest_has_conf2 (cpu_data[0].guest.conf & (1 << 2))
655 #define cpu_guest_has_conf3 (cpu_data[0].guest.conf & (1 << 3))
658 #define cpu_guest_has_conf4 (cpu_data[0].guest.conf & (1 << 4))
661 #define cpu_guest_has_conf5 (cpu_data[0].guest.conf & (1 << 5))
664 #define cpu_guest_has_conf6 (cpu_data[0].guest.conf & (1 << 6))
667 #define cpu_guest_has_conf7 (cpu_data[0].guest.conf & (1 << 7))
670 #define cpu_guest_has_fpu (cpu_data[0].guest.options & MIPS_CPU_FPU)
688 #define cpu_guest_has_htw (cpu_data[0].guest.options & MIPS_CPU_HTW)
694 #define cpu_guest_has_mvh (cpu_data[0].guest.options & MIPS_CPU_MVH)
[all …]
/linux/Documentation/arm64/
A Dperf.rst31 For the guest this attribute will exclude EL1. Please note that EL2 is
32 never counted within a guest.
45 guest/host transitions.
47 For the guest this attribute has no effect. Please note that EL2 is
48 never counted within a guest.
54 These attributes exclude the KVM host and guest, respectively.
59 The KVM guest may run at EL0 (userspace) and EL1 (kernel).
76 non-VHE guest however please note that EL2 is never counted within a guest.
84 enabling/disabling the counters and entering/exiting the guest. We are
86 entry/exit when counting guest events by filtering out EL2 for
[all …]
/linux/Documentation/virt/kvm/
A Drunning-nested-guests.rst5 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
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).
142 Starting a nested guest (x86)
185 Migrating an L1 guest, with a *live* nested guest in it, to another
189 On AMD systems, once an L1 guest has started an L2 guest, the L1 guest
192 or save-and-load an L1 guest while an L2 guest is running will result in
203 - Migrating a nested guest (L2) to another L1 guest on the *same* bare
[all …]
A Dmmu.rst8 for presenting a standard x86 mmu to the guest, while translating guest
47 gfn guest frame number
76 - when guest paging is disabled, we translate guest physical addresses to
78 - when guest paging is enabled, we translate guest virtual addresses, to
80 - when the guest launches a guest of its own, we translate nested guest
81 virtual addresses, to nested guest physical addresses, to guest physical
274 guest's cr3. This is expensive, so we keep all guest page tables write
280 protection from the guest page, and allowing the guest to modify it freely.
284 random guest data.
297 - a true guest fault (the guest translation won't allow the access) (*)
[all …]
A Damd-memory-encryption.rst105 __u32 policy; /* guest's policy */
147 measurement. Since the guest owner knows the initial contents of the guest at
171 issued to make the guest ready for the execution.
179 SEV-enabled guest.
188 __u32 handle; /* guest handle */
189 __u32 policy; /* guest policy */
193 SEV guest state:
275 used by the guest owner with the KVM_SEV_LAUNCH_MEASURE.
297 outgoing guest encryption context.
385 __u32 policy; /* guest's policy */
[all …]
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
106 KVM_FEATURE_CLOCKSOURCE_STABLE_BIT 24 host will warn if no guest-side
[all …]
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.
50 access to the guest memory.
84 instruction text, in order not to leak guest instruction text.
92 this instruction to be moved to the guest via the two data areas
[all …]
A Dhypercalls.rst54 :Purpose: Trigger guest exit so that the host can check for pending
83 The guest can map this shared page to access its supervisor register
93 A vcpu of a paravirtualized guest that is busywaiting in guest
107 :Purpose: Hypercall used to synchronize host and guest clocks.
111 a0: guest physical address where host copies
130 * tsc: guest TSC value used to calculate sec/nsec pair
133 The hypercall lets a guest compute a precise timestamp across
134 host and guest. The guest can use the returned TSC value to
152 The hypercall lets a guest send multicast IPIs, with at most 128
179 a0: the guest physical address of the start page
[all …]
A Dmsr.rst40 guest has to check version before and after grabbing
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 |
287 a sequence counter. In other words, guest has to check
321 EOI by clearing the bit in guest memory - this location will
335 guest and clear the least significant bit in the memory area
336 in the window between guest testing it to detect
337 whether it can skip EOI apic write and between guest
387 When a guest is started, bit 0 will be 0 if the guest has encrypted
[all …]
/linux/tools/perf/Documentation/
A Dperf-kvm.txt6 perf-kvm - Tool to trace/measure kvm guest os
11 'perf kvm' [--host] [--guest] [--guestmount=<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
33 Default('') -> perf.data.guest
35 --guest -> perf.data.guest
36 --host --guest -> perf.data.kvm
37 --host --no-guest -> perf.data.host
78 --guest::
79 Collect guest side performance profile.
[all …]
/linux/tools/testing/vsock/
A DREADME3 These tests exercise net/vmw_vsock/ host<->guest sockets for VMware, KVM, and
16 3. Install the kernel and tests inside the guest.
17 4. Boot the guest and ensure that the AF_VSOCK transport is enabled.
21 # host=server, guest=client
25 (guest)# $TEST_BINARY --mode=client \
30 # host=client, guest=server
31 (guest)# $TEST_BINARY --mode=server \
/linux/Documentation/ABI/testing/
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
A Dsysfs-driver-pciback7 the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
14 will allow the guest to read and write to the configuration
23 MSI, MSI-X) set by a connected guest. It is meant to be set
24 only when the guest is a stubdomain hosting device model (qemu)
27 to a PV guest. The device is automatically removed from this
/linux/drivers/staging/unisys/Documentation/
A Doverview.txt10 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".
32 Each virtual device requires exactly 1 dedicated channel, which the guest
45 guest, the already-existing efifb Linux driver is used to provide guest
261 guest by proxying buffer information between the guest and the service
263 between the guest and the service partition. The connectivity of this
264 interface with the shared interface and possibly other guest
266 service partition; the guest driver handles communication and link
322 visorbus is required for every Linux guest running under s-Par.
333 configurations where the Linux guest is provided with an SR-IOV NIC
[all …]
/linux/arch/x86/xen/
A DKconfig7 bool "Xen guest support"
19 bool "Xen PV guest support"
27 Support running as a Xen PV guest.
59 bool "Xen PVHVM guest support"
63 Support running as a Xen PVHVM guest.
79 bool "Xen PVH guest support"
84 Support for running as a Xen PVH guest.
93 Support running as a Xen Dom0 guest.
/linux/Documentation/virt/kvm/arm/
A Dpsci.rst9 and power-off to the guest.
15 This means that a guest booted on two different versions of KVM can
17 a given guest is tied to a particular PSCI revision (unlikely), or if
19 blue to an unsuspecting guest.
40 offered by KVM to the guest via a HVC call. The workaround is described
48 guest is unknown.
51 available to the guest and required for the mitigation.
54 is available to the guest, but it is not needed on this VCPU.
58 offered by KVM to the guest via a HVC call. The workaround is described
/linux/Documentation/ABI/stable/
A Dsysfs-hypervisor-xen33 Space separated list of supported guest system types. Each type
40 <major>: major guest interface version
41 <minor>: minor guest interface version
43 "x86_32": 32 bit x86 guest without PAE
44 "x86_32p": 32 bit x86 guest with PAE
45 "x86_64": 64 bit x86 guest
46 "armv7l": 32 bit arm guest
47 "aarch64": 64 bit arm guest
64 Features the Xen hypervisor supports for the guest as defined
96 UUID of the guest as known to the Xen hypervisor.
/linux/tools/virtio/virtio-trace/
A DREADME4 Trace agent is a user tool for sending trace data of a guest to a Host in low
48 For example, if a guest use three CPUs, the names are
83 example, if a guest use three CPUs, chardev names should be trace-path-cpu0,
86 3) Boot the guest
87 You can find some chardev in /dev/virtio-ports/ in the guest.
93 0) Build trace agent in a guest
96 1) Enable ftrace in the guest
100 2) Run trace agent in the guest
104 option, trace data are output via stdout in the guest.
113 A host injects read start order to the guest via virtio-serial.
[all …]
/linux/drivers/staging/unisys/Documentation/ABI/
A Dsysfs-platform-visorchipset29 the previous guest boot) has no effect.
37 this guest. Setting the flag will cause the guest to boot from
48 action to perform on the next guest boot-up. The meaning of the
50 commission the guest.
58 guest, and triggered by a udev event. The support script is
60 PF device is being recovered in another guest.
77 guest, and triggered by a udev event. The support script is
79 PF device is being recovered in another guest.
/linux/Documentation/filesystems/
A Dvirtiofs.rst6 virtiofs: virtio-fs host<->guest shared file system
14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a
15 guest to mount a directory that has been exported on the host.
24 expose the storage network to the guest. The virtio-fs device was designed to
28 guest and host to increase performance and provide semantics that are not
37 guest# mount -t virtiofs myfs /mnt
60 client. The guest acts as the FUSE client while the host acts as the FUSE
65 response portion of the buffer is filled in by the host and the guest handles

Completed in 75 milliseconds

12345678910