Home
last modified time | relevance | path

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

/linux-4.4.14/Documentation/virtual/kvm/arm/
Dvgic-mapped-irqs.txt6 allowing software to inject virtual interrupts to a VM, which the guest
12 lets a guest OS program the hardware device directly to raise an
15 event as a virtual interrupt to the guest. Another example could be a
17 by the host, but the device driver for the device lives in the guest OS
19 the physical one to the guest OS.
31 Virtual interrupts are signalled to the guest by programming the List
34 Active, or Pending+Active). When the guest ACKs and EOIs a virtual
46 interrupt on the physical distributor when the guest deactivates the
58 interface is going to present it to the guest.
59 - LR.Pending will stay set as long as the guest has not acked the interrupt.
[all …]
/linux-4.4.14/tools/perf/Documentation/
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 …]
Dperf-list.txt30 G - guest counting (in KVM guests)
71 registers: event, umask, edge, inv, cmask. Esp. guest/host only and
Dperf-report.txt95 on guest machine
97 guest machine
Dintel-pt.txt182 G guest
/linux-4.4.14/Documentation/virtual/kvm/
Dmmu.txt5 for presenting a standard x86 mmu to the guest, while translating guest
10 - correctness: the guest should not be able to determine that it is running
14 - security: the guest must not be able to touch host memory not assigned
19 - integration: Linux memory management code must be in control of guest memory
22 - dirty tracking: report writes to guest memory to enable live migration
34 gfn guest frame number
35 gpa guest physical address
36 gva guest virtual address
37 ngpa nested guest physical address
38 ngva nested guest virtual address
[all …]
Dmsr.txt19 in guest RAM. This memory is expected to hold a copy of the following
33 version: guest has to check version before and after grabbing
53 guest RAM, plus an enable bit in bit 0. This memory is expected to hold
75 version: guest has to check version before and after grabbing
110 coordinated between the guest and the hypervisor. Availability
120 | | guest vcpu has been paused by
168 64 byte memory area which must be in guest RAM and must be
182 fault guest must reset the reason to 0 before it does
188 be used to notify a guest when missing page becomes
199 type 1 was, but guest should not rely on that.
[all …]
Dreview-checklist.txt29 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean
33 11. New guest visible features must either be documented in a hardware manual
37 host/guest memory must be unshared to prevent the host from writing to
38 guest memory that the guest has not reserved for this purpose.
Dhypercalls.txt43 Purpose: Trigger guest exit so that the host can check for pending
57 Purpose: Expose hypercall availability to the guest. On x86 platforms, cpuid
66 Purpose: To enable communication between the hypervisor and guest there is a
68 The guest can map this shared page to access its supervisor register through
76 Usage example : A vcpu of a paravirtualized guest that is busywaiting in guest
81 same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall,
Dcpuid.txt5 A guest running on a kvm host, can check some of its features using
8 a guest.
53 KVM_FEATURE_PV_UNHALT || 7 || guest checks this feature bit
57 KVM_FEATURE_CLOCKSOURCE_STABLE_BIT || 24 || host will warn if no guest-side
Dnested-vmx.txt8 to easily and efficiently run guest operating systems. Normally, these guests
12 The "Nested VMX" feature adds this missing capability - of running guest
14 allowing a guest to use VMX instructions, and correctly and efficiently
30 L0, the guest hypervisor, which we call L1, and its nested guest, which we
38 Only 64-bit guest hypervisors are supported.
40 Additional patches for running Windows under guest KVM, and Linux under
41 guest VMware server, and support for nested EPT, are currently running in
64 implementation for the a guest hypervisor to use. As such, the official
Dppc-pv.txt66 To enable communication between the hypervisor and guest there is a new shared
67 page that contains parts of supervisor visible register state. The guest can
70 With this hypercall issued the guest always gets the magic page mapped at the
91 a second return value is passed to the guest. This second return value contains
106 feature we also have a channel for a guest to tell the guest whether it's capable
111 The following flags are currently available for a guest to expose:
120 when entering the guest or don't have any impact on the hypervisor's behavior.
122 The following bits are safe to be set inside the guest:
137 guest. Implementing any of those mappings is optional, as the instruction traps
Dapi.txt38 actually running guest code.
115 corresponds to guest physical address zero. Use of mmap() on a VM fd
141 This ioctl returns the guest msrs that are supported. The list varies
223 Userspace can control the threading (SMT) mode of the guest by its
225 single-threaded guest vcpus, it should make all vcpu ids be a multiple
284 This ioctl is used to run a guest virtual cpu. While there are no
432 This injects an edge type external interrupt into the guest once it's ready
443 This injects a level type external interrupt into the guest context. The
661 should not present interrupts to the guest as active-low unless this
745 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
[all …]
Dlocking.txt14 Fast page fault is the fast path which fixes the guest page fault out of
23 the gfn is writable on guest mmu and it is not write-protected by shadow
52 gfn2 by the guest:
Dtimekeeping.txt20 division of time beyond the control of the guest CPU.
339 allows the guest visible TSC to be offset by a constant. Newer implementations
482 be able to deliver the proper number of interrupts per second, and so guest
491 additional interrupts into the guest in order to increase the effective
493 where host load or guest lag is too much to compensate for, and thus another
494 solution to the problem has risen: the guest may need to become aware of lost
555 delivered, and after which, the guest time may need to be caught up. NTP may
563 faster clock cannot be made visible to a guest without the potential of time
566 simply storing multipliers and offsets against the TSC for the guest to convert
574 distributed, but in contrived as well as real scenarios (guest device access,
[all …]
Ds390-diag.txt15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
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.
53 What: guest/chipsetready
57 Description: This entry is used by Unisys application software on the guest
60 guest to operate correctly. The interface accepts one of two
72 guest, and triggered by a udev event. The support script is
74 PF device is being recovered in another guest.
91 guest, and triggered by a udev event. The support script is
[all …]
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt10 allow guest partitions on the same server to share devices that would
20 commonly referred to as "guest drivers" or "client drivers". All drivers
21 except visorbus expose a device of a specific usable class to the Linux guest
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
216 clientpartition handle identifying the guest (client) side
[all …]
Dproc-entries.txt19 guest can be considered running and is shown as running in the s-Par
74 read/write, however, the guest can only reset them to 0, or report an
91 /proc/visorchipset/partition: This directory contains the guest
/linux-4.4.14/tools/virtio/virtio-trace/
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.
109 the guest will stop by specification of chardev in QEMU. This blocking mode may
[all …]
/linux-4.4.14/arch/powerpc/kvm/
DKconfig53 Support running unmodified book3s_32 guest kernels
68 Support running unmodified book3s_64 and book3s_32 guest kernels
83 Support running unmodified book3s_64 guest kernels in
89 guest operating systems will run at full hardware speed
102 Support running guest kernels in virtual machines on processors
104 guest in user mode (problem state) and emulating all
117 Calculate time taken for each vcpu in the real-mode guest entry,
118 exit, and interrupt handling code, plus time spent in the guest
120 in the guest. The total, minimum and maximum times in nanoseconds
148 Support running unmodified E500 guest kernels in virtual machines on
[all …]
/linux-4.4.14/tools/lguest/
Dlguest.txt27 - The easiest way to run lguest is to use same kernel as guest and host.
33 "Paravirtualized guest support" = Y
34 "Lguest guest support" = Y
86 inside the guest.
94 eth0 inside the guest at 192.168.19.2.
97 using --tunnet=bridge:<bridgename>, and perhaps run dhcp on the guest
109 Then use --tunnet=bridge:lg0 when launching the guest.
118 /dev/hwrng in the guest that will read from the host's /dev/random.
120 to provide entropy to the guest kernel's /dev/random.
/linux-4.4.14/fs/proc/
Dstat.c85 u64 guest, guest_nice; in show_stat() local
93 guest = guest_nice = 0; in show_stat()
106 guest += kcpustat_cpu(i).cpustat[CPUTIME_GUEST]; in show_stat()
129 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(guest)); in show_stat()
143 guest = kcpustat_cpu(i).cpustat[CPUTIME_GUEST]; in show_stat()
154 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(guest)); in show_stat()
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt11 registers; their location is communicated to the guest's UEFI firmware in the
12 DTB that QEMU places at the bottom of the guest's DRAM.
14 The guest writes a selector value (a key) to the selector register, and then
16 the selected entry is writable, the guest can rewrite it through the data
27 The interface allows guest firmware to download various parameters and blobs
28 that affect how the firmware works and what tables it installs for the guest
48 The guest kernel is not expected to use these registers (although it is
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-hypervisor-pmu9 "self" -- The guest can profile itself
10 "hv" -- The guest can profile itself and, if it is
12 "all" -- The guest can profile itself, the hypervisor
Dsysfs-driver-pciback7 the format of DDDD:BB:DD.F-REG:SIZE:MASK will allow the guest
12 will allow the guest to read and write to the configuration
/linux-4.4.14/Documentation/virtual/kvm/devices/
Dvm.txt25 Clear the CMMA status for all guest pages, so any pages the guest marked
29 Parameters: in attr->addr the address for the new limit of guest memory
32 -E2BIG if the given guest memory is to big for that machine
34 -ENOMEM if not enough memory is available for a new shadow guest mapping
38 the maximum guest memory size. The limit will be rounded up to
Ds390_flic.txt14 - enable/disable for the guest transparent async page faults
41 interrupts. No interrupts are injected into the guest.
44 Enables async page faults for the guest. So in case of a major page fault
45 the host is allowed to handle this async and continues the guest.
48 Disables async page faults for the guest and waits until already pending
88 perform a gmap translation for the guest address provided in addr,
Darm-vgic.txt13 Creating a guest GICv3 device requires a host GICv3 as well.
14 GICv3 implementations with hardware compatibility support allow a guest GICv2
21 Base address in the guest physical address space of the GIC distributor
26 Base address in the guest physical address space of the GIC virtual cpu
31 Base address in the guest physical address space of the GICv3 distributor
36 Base address in the guest physical address space of the GICv3
80 guest. This interface always exposes four register APR[0-3] describing the
Dmpic.txt21 Access an MPIC register, as if the access were made from the guest.
/linux-4.4.14/arch/arm/kvm/
Dinterrupts.S115 @ Store hardware CP15 state and load guest state
122 @ Set FPEXC_EN so the guest doesn't trap floating point instructions
151 @ We're all done, just restore the GPRs and go to the guest
202 @ Store guest CP15 state and restore host state
469 4: pop {r0, r1} @ Failed translation, return to guest
488 @ Switch VFP/NEON hardware state to the guest's
DMakefile21 obj-y += arm.o handle_exit.o guest.o mmu.o emulate.o reset.o
DKconfig37 Support hosting virtualized guest machines.
Dinterrupts_head.S235 @ Store other guest registers
548 @ Disallow physical timer access for the guest
/linux-4.4.14/arch/mips/kvm/
D00README.txt24 …Linux-3.7-rc2 based SMP guest hangs due to the following code sequence in the generated TLB handle…
26 when we ERET back to the guest. This causes the guest to hang in an infinite loop.
Dlocore.S233 mtc0 k0, CP0_ERROREPC #01: Save guest k0
/linux-4.4.14/drivers/media/pci/zoran/
Dzoran_device.h41 unsigned guest,
45 unsigned guest,
Dzoran_device.c132 unsigned int guest, in post_office_write() argument
139 ZR36057_POR_PODir | ZR36057_POR_POTime | ((guest & 7) << 20) | in post_office_write()
148 unsigned int guest, in post_office_read() argument
153 por = ZR36057_POR_POTime | ((guest & 7) << 20) | ((reg & 7) << 16); in post_office_read()
170 int i, guest[8]; in dump_guests() local
173 guest[i] = post_office_read(zr, i, 0); in dump_guests()
179 printk(" 0x%02x", guest[i]); in dump_guests()
188 int timeout, i, j, res, guest[8], guest0[8], change[8][3]; in detect_guest_activity() local
195 guest0[i] = guest[i] = post_office_read(zr, i, 0); in detect_guest_activity()
206 if (res != guest[i]) { in detect_guest_activity()
[all …]
/linux-4.4.14/arch/x86/xen/
DKconfig6 bool "Xen guest support"
55 bool "Support for running as a PVH guest"
/linux-4.4.14/drivers/vhost/
DKconfig8 guest networking with virtio_net. Not to be confused with virtio_net
9 module itself which needs to be loaded in guest kernel.
/linux-4.4.14/Documentation/tpm/
Dxen-tpmfront.txt11 The goal of this work is to provide a TPM functionality to a virtual guest
14 system. Each guest gets its own unique, emulated, software TPM. However, each
17 these domains (manager, vTPM, and guest) is trusted, the vTPM subsystem extends
66 * Linux DomU: The Linux based guest that wants to use a vTPM. There may be
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt96 The ATMU is programmed with the guest physical address, and the PAMU
102 be used to cover all of the guest's memory space.
105 subwindow can have its own address mapping ("guest physical" to "true
113 lives). The first subwindow after the end of guest memory is used for
/linux-4.4.14/arch/mips/paravirt/
DPlatform2 # Generic para-virtualized guest.
/linux-4.4.14/Documentation/vm/
Duserfaultfd.txt96 page faults in the guest scheduler so those guest processes that
98 the guest vcpus.
102 generating userfaults for readonly guest regions.
113 guest (UFFDIO_ZEROCOPY is used if the source page was a zero page).
Dfrontswap.txt109 optimize RAM utilization. And when guest OS's are induced to surrender
223 Similarly, a KVM guest-side implementation could do in-guest compression
Dzswap.txt21 impact to the guest workload and guests sharing the I/O subsystem
Dhwpoison.txt44 KVM can inject the machine check into the guest with the proper
Dtranshuge.txt31 TLB can be mapped of larger size only if both KVM and the Linux guest
49 immediately in the buddy or through the VM), guest physical memory
Dcleancache.txt129 optimize RAM utilization. And when guest OS's are induced to surrender
/linux-4.4.14/drivers/misc/vmw_vmci/
DKconfig10 high-speed communication between host and guest in a virtual
/linux-4.4.14/arch/x86/lguest/
DKconfig2 bool "Lguest guest support"
/linux-4.4.14/drivers/hv/
DKconfig1 menu "Microsoft Hyper-V guest support"
/linux-4.4.14/net/9p/
DKconfig23 guest partitions and a host partition.
/linux-4.4.14/arch/tile/kvm/
DKconfig26 Support hosting paravirtualized guest machines.
/linux-4.4.14/arch/arm64/kvm/
DMakefile20 kvm-$(CONFIG_KVM_ARM_HOST) += guest.o debug.o reset.o sys_regs.o sys_regs_generic_v8.o
DKconfig40 Support hosting virtualized guest machines.
/linux-4.4.14/drivers/s390/net/
DKconfig38 running on the other VM guest. To compile as a module, choose M.
47 from other VM guest systems.
/linux-4.4.14/Documentation/networking/
Di40evf.txt20 The guest OS loading the i40evf driver must support MSI-X interrupts.
Dixgbevf.txt23 The guest OS loading the ixgbevf driver must support MSI-X interrupts.
Dvxge.txt90 Enable learning the mac address of the guest OS interface in
Digbvf.txt25 The guest OS loading the igbvf driver must support MSI-X interrupts.
Dixgbe.txt329 with KVM and a Microsoft Windows Server 2008 guest try the following
331 when using qemu to create the KVM guest:
/linux-4.4.14/Documentation/w1/masters/
Dds249057 with a OHCI controller, ds2490 running in the guest would operate
65 reattaching would clear the problem. usbmon output in the guest and
/linux-4.4.14/Documentation/s390/
Dmonreader.txt19 The z/VM guest on which you want to access this API needs to be configured in
38 guest virtual storage around the address range of the DCSS.
49 Your guest virtual storage has to end below the starting address of the DCSS
55 This defines 140MB storage size for your guest, the parameter "mem=160M" is
D3270.txt90 with emulated 3270s, as soon as you dial into your vm guest using the
95 3. Define graphic devices to your vm guest machine, if you
148 dial my-vm-guest-name
152 see instead the line "DIALED TO my-vm-guest-name 0620".
175 "HCPDIA047E my-vm-guest-name 0620 does not exist"?
DDebugging390.txt1081 On a SMP guest issue a command to all CPUs try prefixing the command with cpu
1084 If you are running on a guest with several cpus & you have a IO related problem
1479 If you have a guest with certain privileges you may be able to see devices
1494 of another VM guest so he can ftp the logfile back to his own machine. I'll do
1498 SP PRT TO (another vm guest ) or * for the local vm guest
1527 you can alternatively spool it to another readers guest.
1538 ATT <devno range> <guest>
1539 attach a device to guest * for your own guest
1554 2 need to be defined on each guest for the CTC driver to use.
/linux-4.4.14/drivers/xen/
DKconfig59 int "Hotplugged memory limit (in GiB) for a PV guest"
66 Maxmium amount of memory (in GiB) that a PV guest can be
69 A PV guest can have more memory than this limit if is
181 devices to appear in the guest. You can choose the default (0) where
/linux-4.4.14/arch/s390/kvm/
DKconfig33 Support hosting paravirtualized guest machines using the SIE
/linux-4.4.14/arch/x86/include/asm/
Dperf_event.h266 u64 host, guest; member
/linux-4.4.14/tools/testing/ktest/examples/
DREADME19 kvm.conf - A example of a config that is used to test a virtual guest running
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt2 that contains the filesystem used by the guest-OS kernel. There are
/linux-4.4.14/tools/
DMakefile55 cgroup firewire hv guest usb virtio vm net iio: FORCE target
/linux-4.4.14/Documentation/
Dgdb-kernel-debugging.txt32 o Install that kernel on the guest.
56 o Attach to the booted guest:
Dintel_txt.txt110 guest for the APs. When they run in this guest, they will
D00-INDEX455 - info on Virtual Function I/O used in guest/hypervisor instances.
Dvfio.txt474 create those in run-time if the guest driver supports 64bit DMA.
Dkernel-parameters.txt1755 kvm.ignore_msrs=[KVM] Ignore guest accesses to unhandled MSRs.
1774 [KVM,Intel] Enable emulation of invalid guest states
1786 [KVM,Intel] Disable unrestricted guest feature
4177 Disables the PV optimizations forcing the HVM guest to
4178 run as generic HVM guest with no PV drivers.
/linux-4.4.14/Documentation/ia64/
Dxen.txt51 Making a disk image for guest OS
86 FYI, virt-manager can also make a disk image for guest OS.
/linux-4.4.14/arch/mips/pci/
DMakefile25 obj-$(CONFIG_MIPS_PCI_VIRTIO) += pci-virtio-guest.o
/linux-4.4.14/drivers/virtio/
DKconfig47 of memory within a KVM guest.
/linux-4.4.14/arch/x86/kvm/
DKconfig48 Support hosting fully virtualized guest machines using hardware
Dvmx.c548 struct vmx_msr_entry guest[NR_AUTOLOAD_MSRS]; member
1699 if (m->guest[i].index == msr) in clear_atomic_switch_msr()
1705 m->guest[i] = m->guest[m->nr]; in clear_atomic_switch_msr()
1761 if (m->guest[i].index == msr) in add_atomic_switch_msr()
1774 m->guest[i].index = msr; in add_atomic_switch_msr()
1775 m->guest[i].value = guest_val; in add_atomic_switch_msr()
4837 vmcs_write64(VM_ENTRY_MSR_LOAD_ADDR, __pa(vmx->msr_autoload.guest)); in vmx_vcpu_setup()
8520 if (msrs[i].host == msrs[i].guest) in atomic_switch_perf_msrs()
8523 add_atomic_switch_msr(vmx, msrs[i].msr, msrs[i].guest, in atomic_switch_perf_msrs()
/linux-4.4.14/arch/s390/kernel/
Dentry.S208 stg %r3,__SF_EMPTY+8(%r15) # save guest register save area
210 TSTMSK __LC_CPU_FLAGS,_CIF_FPU # load guest fp/vx registers ?
212 brasl %r14,load_fpu_regs # load guest fp/vx regs
214 lmg %r0,%r13,0(%r3) # load guest gprs 0-13
240 lg %r14,__SF_EMPTY+8(%r15) # load guest register save area
241 stmg %r0,%r13,0(%r14) # save guest gprs 0-13
/linux-4.4.14/Documentation/hwmon/
Damc682111 Tomaz Mertelj <tomaz.mertelj@guest.arnes.si>
/linux-4.4.14/drivers/gpu/drm/vmwgfx/
Dvmwgfx_surface.c272 body->guest.ptr = *ptr; in vmw_surface_dma_encode()
273 body->guest.ptr.offset += cur_offset->bo_offset; in vmw_surface_dma_encode()
274 body->guest.pitch = svga3dsurface_calculate_pitch(desc, in vmw_surface_dma_encode()
294 body->guest.pitch); in vmw_surface_dma_encode()
Dvmwgfx_kms.c302 if (cmd->dma.guest.ptr.offset % PAGE_SIZE || in vmw_kms_cursor_snoop()
314 cmd->dma.guest.ptr.offset); in vmw_kms_cursor_snoop()
318 kmap_offset = cmd->dma.guest.ptr.offset >> PAGE_SHIFT; in vmw_kms_cursor_snoop()
333 if (box->w == 64 && cmd->dma.guest.pitch == 64*4) { in vmw_kms_cursor_snoop()
339 virtual + i * cmd->dma.guest.pitch, in vmw_kms_cursor_snoop()
Dvmwgfx_stdu.c797 vmw_bo_get_guest_ptr(&ddirty->buf->base, &cmd->body.guest.ptr); in vmw_stdu_dmabuf_fifo_commit()
798 cmd->body.guest.pitch = ddirty->pitch; in vmw_stdu_dmabuf_fifo_commit()
Dvmwgfx_execbuf.c1687 &cmd->dma.guest.ptr, in vmw_cmd_dma()
1694 if (unlikely(cmd->dma.guest.ptr.offset > bo_size)) { in vmw_cmd_dma()
1699 bo_size -= cmd->dma.guest.ptr.offset; in vmw_cmd_dma()
/linux-4.4.14/drivers/pci/
DKconfig57 when it is going to be assigned to a guest operating system.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dqe.txt76 the hypervisor to the guest.
/linux-4.4.14/arch/x86/kernel/cpu/
Dperf_event_intel.c2576 arr[0].guest = x86_pmu.intel_ctrl & ~cpuc->intel_ctrl_host_mask; in intel_guest_get_msrs()
2584 arr[1].guest = 0; in intel_guest_get_msrs()
2600 arr[idx].host = arr[idx].guest = 0; in core_guest_get_msrs()
2605 arr[idx].host = arr[idx].guest = in core_guest_get_msrs()
2611 arr[idx].guest &= ~ARCH_PERFMON_EVENTSEL_ENABLE; in core_guest_get_msrs()
/linux-4.4.14/arch/powerpc/platforms/85xx/
DKconfig256 This option enables support for running as a QEMU guest using
/linux-4.4.14/drivers/gpu/drm/vmwgfx/device_include/
Dsvga3d_cmd.h502 SVGAGuestImage guest; member
/linux-4.4.14/drivers/misc/
DKconfig421 by reserving them in the guest and invalidating them in the
424 to allow the guest to use more physical memory.
/linux-4.4.14/arch/mips/
DKconfig953 bool "Para-Virtualized guest system"
969 This option supports guest running under ????
2021 Select this option if building a guest kernel for KVM (Trap & Emulate) mode
2028 Set this to non-zero if building a guest kernel for KVM to skip RTC
2029 emulation when determining guest CPU Frequency. Instead, the guest's
/linux-4.4.14/arch/s390/
DKconfig776 will be reused by VM for other guest systems. The interface
874 Select this option if you want to run the kernel as a guest under
/linux-4.4.14/mm/
DKconfig235 used within a guest, thus imposing performance penalties associated
237 by the guest workload. Allowing the compaction & migration for memory
/linux-4.4.14/arch/tile/
DKconfig414 or as a KVM guest, you must run at PL1. (The current
/linux-4.4.14/Documentation/filesystems/
Dproc.txt324 gtime guest time of the task in jiffies
325 cgtime guest time of the task children in jiffies
1303 - guest: running a normal guest
1304 - guest_nice: running a niced guest
/linux-4.4.14/drivers/net/
DKconfig385 If you are compiling a kernel for use as Xen guest, you
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt445 The NMI watchdog is disabled by default if the kernel is running as a guest
450 to the guest kernel command line (see Documentation/kernel-parameters.txt).
/linux-4.4.14/arch/x86/
DKconfig650 bool "Linux guest support"
657 disabled, and Linux guest support won't be built in.
701 underlying device model, the host provides the guest with
709 This option enables collection of various statistics for KVM guest.
/linux-4.4.14/Documentation/filesystems/cifs/
DREADME382 guest Although ignored by the kernel component, the mount.cifs
384 if guest is specified on the mount options. If no
DCHANGES60 are authenticated as guest, as reconnections, invalidating the earlier
/linux-4.4.14/drivers/char/
DKconfig165 transfer between the guest and host. Character devices at
/linux-4.4.14/arch/arm64/
DKconfig564 bool "Xen guest support on ARM64"
/linux-4.4.14/tools/perf/util/
Devsel.c320 MOD_PRINT(guest, 'G'); in perf_evsel__add_modifiers()
/linux-4.4.14/drivers/platform/x86/
DKconfig932 (guest) communicate panic events to the host.
/linux-4.4.14/drivers/scsi/
DKconfig590 within another guest OS (usually Dom0).
591 Only needed if the kernel is running in a XEN guest and generic
/linux-4.4.14/drivers/watchdog/
DKconfig1448 provide a virtual watchdog timer to their guest that cause a
/linux-4.4.14/arch/arm/
DKconfig1808 bool "Xen guest support on ARM"
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt1808 my guest. Remember, the idea is to get a number that causes us
/linux-4.4.14/Documentation/RCU/
DRTFP.txt2443 Use of RCU permits KVM to increase the size of guest OSes from
/linux-4.4.14/Documentation/trace/
Dftrace.txt357 to correlate events across hypervisor/guest if