Home
last modified time | relevance | path

Searched full:virtualized (Results 1 – 25 of 61) sorted by relevance

123

/freebsd/share/man/man4/
H A Dxen.446 "para-virtualized" as the x86 instruction set was not fully virtualizable.
49 modify the TLB, although para-virtualized device drivers were also required
56 peripherals, or para-virtualized drivers, which are aware of virtualization,
59 PVH configurations rely on para-virtualized drivers exclusively for IO.
62 Para-virtualized device drivers are required in order to support certain
66 These para-virtualized drivers are supported:
H A Dkvmclock.431 .Nd Para-virtualized clock driver for x86 KVM guests
40 This driver reads time-keeping information from the para-virtualized clock
H A Dsysmouse.430 .Nd virtualized mouse driver
442 virtualized mouse driver
H A Dvirtio.447 VirtIO is a specification for para-virtualized I/O in a virtual machine (VM).
H A Dlinprocfs.4119 in different modes in a virtualized environment.
H A Dvxlan.4279 .%T "Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 …
/freebsd/sys/net/
H A Dvnet.c75 * - Virtualized SYSINIT's/SYSUNINIT's, which allow network stack subsystems
107 * The virtual network stack allocator provides storage for virtualized
115 * vs. modules in similar but different ways. In both cases, virtualized
131 * virtualized global variable, stored in a malloc'd block of memory
140 * Virtualized global variables are handled in a similar manner, but as each
142 * virtualized globals togther, we reserve space in the kernel's linker set
157 * size of all kernel virtualized global variables, and the malloc(9) type
167 * array declared as a virtualized global variable in the kernel itself, and
168 * we want the virtualized global variable space to be page-sized, we may
175 * Space to store virtualized global variables from loadable kernel modules,
[all …]
H A Dvnet.h39 * This header file defines several sets of interfaces supporting virtualized
46 * virtualized global variables via a special linker set, set_vnet.
48 * - Virtualized sysinits/sysuninits, which allow constructors and
52 * If VIMAGE isn't compiled into the kernel, virtualized global variables
53 * compile to normal global variables, and virtualized sysinits to regular
61 * struct vnet describes a virtualized network stack, and is primarily a
62 * pointer to storage for virtualized global variables. Expose to userspace
83 * for libkvm so that it can evaluate virtualized global variables.
299 * Virtualized global variable accessor macros.
315 * Interfaces to manipulate the initial values of virtualized global variables.
[all …]
/freebsd/share/man/man9/
H A DVNET.9187 Variables are virtualized by using the
201 Static initialization is not possible when the virtualized variable
215 to express that it is virtualized.
439 can be virtualized by adding the
/freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/
H A Dmsi-pic.txt37 This property may be used in virtualized environments where the hypervisor
87 In a virtualized environment, the hypervisor may need to create an IOMMU
/freebsd/sys/contrib/xen/arch-x86/
H A Dcpuid.h99 #define XEN_HVM_CPUID_APIC_ACCESS_VIRT (1u << 0) /* Virtualized APIC registers */
100 #define XEN_HVM_CPUID_X2APIC_VIRT (1u << 1) /* Virtualized x2APIC accesses */
/freebsd/usr.sbin/bhyve/amd64/
H A Dxmsr.c165 * PerfEvtSel MSRs are not properly virtualized so just in emulate_rdmsr()
176 * PerfCtr MSRs are not properly virtualized so just in emulate_rdmsr()
/freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/
H A Dfsl,mpic-msi.yaml17 In a virtualized environment, the hypervisor may need to create an IOMMU
99 This property may be used in virtualized environments where the hypervisor
/freebsd/sys/contrib/xen/
H A Dsched.h99 * in interpreting shutdown requests and reasons for fully-virtualized
100 * domains. A para-virtualized domain may use SCHEDOP_shutdown directly.
/freebsd/sys/contrib/device-tree/Bindings/iommu/
H A Dxen,grant-dma.yaml7 title: Xen specific IOMMU for virtualized devices (e.g. virtio)
/freebsd/sys/contrib/device-tree/Bindings/cpufreq/
H A Dqemu,virtual-cpufreq.yaml14 Virtual CPUFreq is a virtualized driver in guest kernels that sends performance
/freebsd/contrib/libarchive/libarchive/
H A Dlibarchive_internals.360 some public functions are virtualized.
317 and function pointers for virtualized API functions.
/freebsd/tools/tools/
H A DREADME59 vimage An interim utility for managing the virtualized network
/freebsd/contrib/tcpdump/
H A Dprint-vxlan.c37 * for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks
/freebsd/sys/contrib/xen/io/
H A Ddisplif.h312 * the virtualized device. If this is possible at the moment of error,
314 * new connection with backend. If the virtualized device is still in use and
316 * until either the virtualized device is removed or backend initiates a new
317 * connection. On the virtualized device removal frontend goes into the
322 * and thus cannot provide functionality of the virtualized device anymore.
323 * After backend is back to normal the virtualized device may still hold some
327 * frontend will make sure no new clients of the virtualized device are
330 * Once all the clients are gone frontend can reinitialize the virtualized
338 * client of the virtualized device has gone and the device can be removed
341 * the virtualized device.
H A Dsndif.h209 * Every virtualized sound frontend has a set of PCM devices and streams, each
380 * the virtualized device. If this is possible at the moment of error,
382 * new connection with backend. If the virtualized device is still in use and
384 * until either the virtualized device removed or backend initiates a new
385 * connection. On the virtualized device removal frontend goes into the
390 * and thus cannot provide functionality of the virtualized device anymore.
391 * After backend is back to normal the virtualized device may still hold some
395 * frontend will make sure no new clients of the virtualized device are
398 * Once all the clients are gone frontend can reinitialize the virtualized
406 * client of the virtualized device has gone and the device can be removed
[all …]
H A Dcameraif.h313 * the virtualized device. If this is possible at the moment of error,
315 * new connection with backend. If the virtualized device is still in use and
317 * until either the virtualized device is removed or backend initiates a new
318 * connection. On the virtualized device removal frontend goes into the
323 * and thus cannot provide functionality of the virtualized device anymore.
324 * After backend is back to normal the virtualized device may still hold some
328 * frontend will make sure no new clients of the virtualized device are
331 * Once all the clients are gone frontend can reinitialize the virtualized
339 * client of the virtualized device has gone and the device can be removed
342 * the virtualized device.
/freebsd/sys/contrib/device-tree/Bindings/dma/
H A Dqcom_hidma_mgmt.txt4 memcpy and memset capabilities. It has been designed for virtualized
/freebsd/tools/tools/vimage/
H A Dvimage.8186 Stiching NLNet, integrated virtualized network stack first appeared in
/freebsd/sys/dev/cxgbe/
H A Doffload.h181 struct t4_virt_res { /* virtualized HW resources */

123