Home
last modified time | relevance | path

Searched refs:hypervisor (Results 1 – 25 of 113) sorted by relevance

12345

/Linux-v4.19/Documentation/ABI/stable/
Dsysfs-hypervisor-xen1 What: /sys/hypervisor/compilation/compile_date
6 Contains the build time stamp of the Xen hypervisor
8 in the hypervisor.
10 What: /sys/hypervisor/compilation/compiled_by
15 Contains information who built the Xen hypervisor
17 in the hypervisor.
19 What: /sys/hypervisor/compilation/compiler
24 Compiler which was used to build the Xen hypervisor
26 in the hypervisor.
28 What: /sys/hypervisor/properties/capabilities
[all …]
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-hypervisor-xen1 What: /sys/hypervisor/guest_type
12 What: /sys/hypervisor/pmu/pmu_mode
22 privileged (e.g. dom0), the hypervisor
23 "all" -- The guest can profile itself, the hypervisor
27 What: /sys/hypervisor/pmu/pmu_features
36 What: /sys/hypervisor/properties/buildid
41 Build id of the hypervisor, needed for hypervisor live patching.
43 in the hypervisor.
Dsysfs-bus-event_source-devices-hv_gpci5 '0' if the hypervisor is configured to forbid access to event
36 hypervisor reports supporting.
/Linux-v4.19/Documentation/virtual/kvm/arm/
Dhyp-abi.txt4 hypervisor layer when running Linux as a hypervisor (for example
6 hypervisor when running as a guest (under Xen, KVM or any other
7 hypervisor), or any hypervisor-specific interaction when the kernel is
10 On arm and arm64 (without VHE), the kernel doesn't run in hypervisor
12 hypervisor to be either installed or torn down.
19 Unless specified otherwise, any built-in hypervisor must implement
25 Set HVBAR/VBAR_EL2 to 'vectors' to enable a hypervisor. 'vectors'
34 hypervisor.
46 Any other value of r0/x0 triggers a hypervisor-specific handling,
/Linux-v4.19/Documentation/misc-devices/
Dibmvmc.rst23 interface between the hypervisor and a management partition. This interface
46 application using a combination of HMC to hypervisor interfaces and
49 The set of HMC to hypervisor messages supported by the management
50 application component are passed to the hypervisor over a VMC interface,
67 for communicating between the management application and the hypervisor. It
74 defined that must take place to establish that both the hypervisor and
79 when the hypervisor detects one of the peer partitions has abnormally
85 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer,
101 from the hypervisor to partition are also reported in this queue.
118 resources available in both the management partition and the hypervisor.
[all …]
/Linux-v4.19/arch/arm/boot/dts/
Dxenvm-4.2.dts20 /* this field is going to be adjusted by the hypervisor */
50 /* this field is going to be adjusted by the hypervisor */
71 hypervisor {
73 /* this field is going to be adjusted by the hypervisor */
75 /* this field is going to be adjusted by the hypervisor */
/Linux-v4.19/Documentation/devicetree/bindings/arm/
Dxen.txt1 * Xen hypervisor device tree bindings
3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with
21 under /hypervisor with following parameters:
43 hypervisor {
58 they differ because they are provided by the Xen hypervisor, together with a set
/Linux-v4.19/Documentation/virtual/kvm/
Dmsr.txt28 whose data will be filled in by the hypervisor. The hypervisor is only
67 whose data will be filled in by the hypervisor periodically. Only one
70 The hypervisor may update this structure at any time it sees fit until
110 coordinated between the guest and the hypervisor. Availability
177 the hypervisor at the time of asynchronous page fault (APF)
218 whose data will be filled in by the hypervisor periodically. Only one
221 The hypervisor may update this structure at any time it sees fit until
242 the hypervisor doesn't support this field.
252 written to by the hypervisor, typically at the time of interrupt
256 later be polled by the hypervisor.
[all …]
Damd-memory-encryption.rst11 virtual machines (VMs) under the control of a hypervisor. When enabled,
15 The hypervisor can determine the SEV support through the CPUID
52 key management interface to perform common hypervisor activities such as
62 The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform
181 The KVM_SEV_DEBUG_DECRYPT command can be used by the hypervisor to request the
201 The KVM_SEV_DEBUG_ENCRYPT command can be used by the hypervisor to request the
221 The KVM_SEV_LAUNCH_SECRET command can be used by the hypervisor to inject secret
237 __u64 trans_uaddr; /* the hypervisor memory region which contains the secret */
Dppc-pv.txt9 instructions that needlessly return us to the hypervisor even though they
13 and transforms them into unprivileged ones with some help from the hypervisor.
22 Linux is running on KVM, a node /hypervisor exists. That node contains a
31 Inside the device tree's /hypervisor node there's a property called
66 To enable communication between the hypervisor and guest there is a new shared
118 The MSR contains bits that require hypervisor intervention and bits that do
119 not require direct hypervisor intervention because they only get interpreted
120 when entering the guest or don't have any impact on the hypervisor's behavior.
203 These are the same hypercalls that pHyp, the POWER hypervisor implements. Some of
Dhypercalls.txt5 instruction. The hypervisor can replace it with instructions that are
28 property inside the device tree's /hypervisor node.
71 Purpose: To enable communication between the hypervisor and guest there is a
84 time-interval. Execution of HLT instruction would cause the hypervisor to put
/Linux-v4.19/drivers/virt/
DKconfig16 tristate "Freescale hypervisor management driver"
20 The Freescale hypervisor management driver provides several services
21 to drivers and applications related to the Freescale hypervisor:
/Linux-v4.19/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt37 This property may be used in virtualized environments where the hypervisor
81 The Freescale hypervisor and msi-address-64
87 In a virtualized environment, the hypervisor may need to create an IOMMU
88 mapping for MSIIR. The Freescale ePAPR hypervisor has this requirement
90 (PAMU), which is currently the only IOMMU that the hypervisor supports.
106 Therefore, the hypervisor has to create a subwindow inside the same
110 address of MSIIR. The hypervisor configures the PAMU to map that address to
/Linux-v4.19/arch/powerpc/kvm/
DKconfig83 tristate "KVM for POWER7 and later using hypervisor mode in host"
91 hypervisor mode available to the host.
104 tristate "KVM support without using hypervisor mode in host"
109 without using hypervisor mode in the host, by running the
113 This is not as fast as using hypervisor mode, but works on
114 machines where hypervisor mode is not available or not usable,
120 bool "Detailed timing for hypervisor real-mode code"
/Linux-v4.19/Documentation/networking/
Dnet_failover.rst24 datapath. It also enables hypervisor controlled live migration of a VM with
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
34 To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY
79 net_failover also enables hypervisor controlled live migration to be supported
84 the source hypervisor.
/Linux-v4.19/arch/sparc/mm/
Dtsb.c129 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user()
143 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user()
162 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page()
177 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page()
273 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in setup_tsb_params()
291 if (tlb_type == hypervisor) { in setup_tsb_params()
505 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in tsb_grow()
/Linux-v4.19/Documentation/admin-guide/
Dl1tf.rst104 only possible, when the hypervisor does not sanitize the content of the
174 the hypervisor flushes the L1D before entering the guest.
195 address space layout of the hypervisor.
228 host OS (hypervisor) context and the other in guest context. The amount
353 managed and sanitized by the hypervisor. Though disabling EPT has a
357 EPT can be disabled in the hypervisor via the 'kvm-intel.ept' parameter.
385 flush Leaves SMT enabled and enables the default hypervisor
394 flush,nosmt Disables SMT and enables the default hypervisor mitigation,
406 off Disables hypervisor mitigations and doesn't emit any
418 The KVM hypervisor mitigation mechanism, flushing the L1D cache when
[all …]
/Linux-v4.19/arch/sparc/kernel/
Dsetup_64.c180 if (tlb_type != hypervisor) { in per_cpu_patch()
202 case hypervisor: in per_cpu_patch()
284 if (tlb_type != hypervisor) in sun4v_patch()
540 else if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap()
580 if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap()
646 if (tlb_type == hypervisor) in setup_arch()
Dpcr.c254 if (tlb_type == hypervisor) { in register_perf_hsvc()
301 if (tlb_type != hypervisor) in unregister_perf_hsvc()
345 case hypervisor: in pcr_arch_init()
Dsmp_64.c110 if (tlb_type == hypervisor) in smp_callin()
365 if (tlb_type == hypervisor) { in smp_boot_one_cpu()
944 if (tlb_type == hypervisor) in smp_flush_dcache_page_impl()
985 if (tlb_type == hypervisor) in flush_dcache_page_all()
1030 if (tlb_type == hypervisor && in smp_fetch_global_pmu()
1331 if (tlb_type != hypervisor) in __cpu_up()
1346 if (tlb_type == hypervisor) { in cpu_play_dead()
1510 if (tlb_type != hypervisor) in smp_init_cpu_poke()
1544 if (tlb_type == hypervisor) { in smp_send_stop()
1684 if (tlb_type == hypervisor) in setup_per_cpu_areas()
Dunaligned_64.c482 if (tlb_type == hypervisor) in handle_ldf_stq()
492 if (tlb_type == hypervisor) in handle_ldf_stq()
508 if (tlb_type == hypervisor) in handle_ldf_stq()
534 if (tlb_type == hypervisor) in handle_ldf_stq()
649 if (tlb_type == hypervisor) in handle_lddfmna()
700 if (tlb_type == hypervisor) in handle_stdfmna()
/Linux-v4.19/net/vmw_vsock/
DKconfig9 allowing communication between Virtual Machines and hypervisor
12 You should also select one or more hypervisor-specific transports
35 hypervisor.
/Linux-v4.19/Documentation/virtual/
Dparavirt_ops.txt4 Linux provides support for different hypervisor virtualization technologies.
8 hypervisors. It allows each hypervisor to override critical operations and
/Linux-v4.19/drivers/xen/
DKconfig120 information with each other and with the hypervisor.
138 bool "Create xen entries under /sys/hypervisor"
143 Create entries under /sys/hypervisor describing the Xen
144 hypervisor environment. When running native or in another
145 virtual environment, /sys/hypervisor will still be present,
304 hypervisor.
307 said information to the Xen hypervisor. Then the Xen hypervisor can
346 Exports hypervisor symbols (along with their types and addresses) via
/Linux-v4.19/arch/arm/kernel/
Dhyp-stub.S128 @ Now install the hypervisor stub:
130 mcr p15, 4, r7, c12, c0, 0 @ set hypervisor vector base (HVBAR)

12345