/xen/xen/arch/x86/cpu/mcheck/ |
A D | mctelem.c | 314 int which = MCTE_CLASS(tep) == MCTE_F_CLASS_URGENT ? in mctelem_processing_hold() local 317 BUG_ON(tep != mctctl.mctc_processing_head[which]); in mctelem_processing_hold() 326 int which = MCTE_CLASS(tep) == MCTE_F_CLASS_URGENT ? in mctelem_processing_release() local 329 BUG_ON(tep != mctctl.mctc_processing_head[which]); in mctelem_processing_release() 332 mctctl.mctc_processing_head[which] = tep->mcte_next; in mctelem_processing_release() 375 mctelem_cookie_t mctelem_reserve(mctelem_class_t which) in mctelem_reserve() argument 397 if (which == MC_URGENT) in mctelem_reserve() 458 static void mctelem_append_processing(mctelem_class_t which) in mctelem_append_processing() argument 460 mctelem_class_t target = which == MC_URGENT ? in mctelem_append_processing() 510 mctelem_class_t target = (which == MC_URGENT) ? in mctelem_consume_oldest_begin() [all …]
|
/xen/xen/include/public/arch-x86/ |
A D | xen-x86_32.h | 116 #define __DECL_REG_LO8(which) union { \ argument 117 uint32_t e ## which ## x; \ 118 uint16_t which ## x; \ 120 uint8_t which ## l; \ 121 uint8_t which ## h; \ 130 #define __DECL_REG_LO8(which) uint32_t e ## which ## x argument
|
A D | xen-x86_64.h | 135 #define __DECL_REG_LOHI(which) union { \ argument 136 uint64_t r ## which ## x; \ 137 uint32_t e ## which ## x; \ 138 uint16_t which ## x; \ 140 uint8_t which ## l; \ 141 uint8_t which ## h; \
|
A D | xen.h | 61 __DeFiNe__ __DECL_REG_LO8(which) uint32_t e ## which ## x 68 __DeFiNe__ __DECL_REG_LO8(which) e ## which ## x
|
/xen/tools/libxl/ |
A D | idl.txt | 18 The idl.Type base class has several other properties which apply to 24 The namespace in which the type resides. Usually this is "libxl_" but 32 Defines the manner in which a type should be passed to C 39 The name of the C function which will free all dynamically allocated 49 The name of the C function which will deep copy all fields within 68 The name of the C function which will initialist Type. 82 The name of the C function which will parse a libxl JSON structure 103 Instances of this class represent types which are predefined within 148 Base class for type-Classes which contain a number of other types 179 A subclass of idl.Aggregate which represents the C union type [all …]
|
/xen/docs/features/ |
A D | feature-levelling.pandoc | 30 Many factors affect the featureset which a VM may use: 56 directly. However, `CPUID` is an unprivileged instruction which doesn't 88 which Xen recognises as a deliberate attempt to get the fully-controlled 94 AMD CPUs from the `K8` onwards support _Feature Override_ MSRs, which allow 97 which are not actually supported. 100 _Feature Mask_ MSRs, which are a simple AND-mask applied to all `CPUID` 133 the *raw_featureset* into the *host_featureset*, which is the set of 138 *hvm_featureset*, which are the maximum featuresets Xen is willing to offer 156 guest cpuid policy is reflected in the MSRs, which are context switched with 173 Please ask on xen-devel for help identifying more specific tests which could [all …]
|
/xen/tools/hotplug/Linux/ |
A D | xen-network-common.sh | 29 if ! which ifup >/dev/null 2>/dev/null 114 if which brctl >&/dev/null; then 134 if which brctl >&/dev/null; then
|
A D | vif2 | 10 if which brctl >&/dev/null; then 19 if which brctl >&/dev/null; then
|
A D | vif-bridge | 35 if which brctl >&/dev/null; then 87 if which brctl >&/dev/null; then
|
/xen/tools/python/ |
A D | pylintrc | 48 # note).You have access to the variables errors warning, statement which 101 # Regular expression which should only match functions or classes name which do 109 # Regular expression which should only match correct module names 112 # Regular expression which should only match correct class names 115 # Regular expression which should only match correct function names 118 # Regular expression which should only match correct method names 121 # Regular expression which should only match correct argument names 124 # Regular expression which should only match correct variable names 127 # Good variable names which should always be accepted, separated by a comma 130 # Bad variable names which should always be refused, separated by a comma [all …]
|
/xen/xen/arch/arm/arm32/ |
A D | debug-pl011.inc | 23 * rb: register which contains the UART base address 40 * rb: register which contains the UART base address 52 * rb: register which contains the UART base address 53 * rt: register which contains the character to transmit
|
A D | debug-8250.inc | 21 * rb: register which contains the UART base address 33 * rb: register which contains the UART base address 34 * rt: register which contains the character to transmit
|
A D | debug-exynos4210.inc | 23 * rb: register which contains the UART base address 35 * rb: register which contains the UART base address 36 * rt: register which contains the character to transmit
|
A D | debug-scif.inc | 32 * rb: register which contains the UART base address 44 * rb: register which contains the UART base address 45 * rt: register which contains the character to transmit
|
/xen/xen/arch/arm/arm64/ |
A D | debug-pl011.inc | 23 * xb: register which containts the UART base address 39 * xb: register which contains the UART base address 51 * xb: register which contains the UART base address 52 * wt: register which contains the character to transmit
|
A D | debug-8250.inc | 23 * xb: register which contains the UART base address 36 * xb: register which contains the UART base address 37 * wt: register which contains the character to transmit
|
A D | debug-cadence.inc | 25 * xb: register which contains the UART base address 37 * xb: register which contains the UART base address 38 * wt: register which contains the character to transmit
|
A D | debug-mvebu.inc | 26 * xb: register which contains the UART base address 38 * xb: register which contains the UART base address 39 * wt: register which contains the character to transmit
|
A D | debug-meson.inc | 32 * xb: register which contains the UART base address 43 * xb: register which contains the UART base address 44 * wt: register which contains the character to transmit
|
A D | debug-scif.inc | 26 * xb: register which contains the UART base address 38 * xb: register which contains the UART base address 39 * wt: register which contains the character to transmit
|
/xen/docs/man/ |
A D | xl-network-configuration.5.pod | 32 Each device has a C<DEVID> which is its index within the vif list, starting from 0. 88 Specifies the name of the network bridge which this VIF should be 96 Specifies the name of the network interface which has an IP and which 115 device to the guest and also as a paravirtualised device which the 181 What, if any, effect this has depends on the hotplug script which is 189 Specifies the backend domain which this device should attach to. This 191 driver domain which is outside the scope of this document. 196 Specifies the rate at which the outgoing traffic will be limited to. 226 It determines the frequency at which the vif transmission credit
|
A D | xl-disk-configuration.5.pod | 40 pairs, flags and positional parameters. Parameters which are not bare 41 keywords and which do not contain "=" symbols are assigned to the 87 such as commas and (in some cases) colons, which would otherwise be 92 not be legal as vdevs. Targets which might match that syntax 165 C<rw> unless devtype=cdrom, in which case C<r> 220 Specifies the backend domain which this device should attach to. This 222 driver domain which is outside the scope of this document. 243 Automatically determine which backend to use. 248 which software implementation of the Xen backend driver is used. 306 not all backends versions which use the workaround understand this [all …]
|
/xen/docs/hypervisor-guide/x86/ |
A D | how-xen-boots.rst | 33 not, either an EFI stub is included which nops/fails applicable setup and 43 is via the start of the binary image, which is the ``start`` symbol. This 55 which indicates the ability to use the PVH boot protocol, and registers 62 The objects are linked together to form ``xen-syms`` which is an ELF64 68 Any bootloader which unzips the binary and follows the ELF headers will place 69 it at the 2M boundary and jump to ``start`` which is the identified entry
|
/xen/docs/admin-guide/ |
A D | microcode-loading.rst | 6 Like many other pieces of hardware, CPUs themselves have errata which are 22 TSX errata which necessitated disabling the feature entirely), or the addition 61 Xen handles microcode blobs in the binary form shipped by vendors, which is 62 also the format which the processor accepts. This format contains header 63 information which Xen and various userspace tools can use to identify the 66 Tools such as Dracut will identify the correct blob for the current CPU, which 82 identify which multiboot module contains the microcode, including negative 98 which contains contains one of these two files:: 136 It will pass the blob to Xen, which will check to see whether the blob is
|
/xen/tools/pygrub/ |
A D | README | 5 1) Libraries of ext2fs, which is the following package (depend on your Linux distribution): 11 2) Libraries of reiserfs, which is the following package (depend on your Linux distribution):
|