/xen/xen/arch/x86/ |
A D | arch.mk | 16 $(call as-option-add,CFLAGS,CC,"vmcall",-DHAVE_AS_VMX) 17 $(call as-option-add,CFLAGS,CC,"crc32 %eax$$(comma)%eax",-DHAVE_AS_SSE4_2) 18 $(call as-option-add,CFLAGS,CC,"invept (%rax)$$(comma)%rax",-DHAVE_AS_EPT) 19 $(call as-option-add,CFLAGS,CC,"rdrand %eax",-DHAVE_AS_RDRAND) 20 $(call as-option-add,CFLAGS,CC,"rdfsbase %rax",-DHAVE_AS_FSGSBASE) 21 $(call as-option-add,CFLAGS,CC,"xsaveopt (%rax)",-DHAVE_AS_XSAVEOPT) 22 $(call as-option-add,CFLAGS,CC,"rdseed %eax",-DHAVE_AS_RDSEED) 23 $(call as-option-add,CFLAGS,CC,"clwb (%rax)",-DHAVE_AS_CLWB) 24 $(call as-option-add,CFLAGS,CC,".equ \"x\"$$(comma)1",-DHAVE_AS_QUOTED_SYM) 30 $(call as-option-add,CFLAGS,CC,\ [all …]
|
/xen/xen/scripts/ |
A D | Kbuild.include | 13 # Name of target with a '.' as filename prefix. foo/bar.o => foo/.bar.o 29 # as-insn: Check whether assembler supports an instruction. 30 # Usage: cflags-y += $(call as-insn,CC FLAGS,"insn",option-yes,option-no) 31 as-insn = $(if $(shell echo 'void _(void) { asm volatile ( $(2) ); }' \ 35 # as-option-add: Conditionally add options to flags 36 # Usage: $(call as-option-add,CFLAGS,CC,"insn",option-yes,option-no) 37 as-option-add = $(eval $(call as-option-add-closure,$(1),$(2),$(3),$(4),$(5))) 38 define as-option-add-closure 39 ifeq ($$(call as-insn,$$($(2)) $$($(1)),$(3),y,n),y) 66 # if_changed_rule - as if_changed but execute rule instead
|
/xen/docs/man/ |
A D | xen-vbd-interface.7.pandoc | 5 provided as Xen VBDs; for HVM guests they may also be provided as 14 available _both_ via emulated IDE resp. SCSI controller, _and_ as a 17 underlying devices as the corresponding Xen VBD (ie, multipath). 21 For PV guests every device is made available to the guest only as a 42 treat each vbd as it would a partition or slice or LVM volume (for 72 The information above is encoded in the concrete interface as an 74 encodes the information above as follows: 101 Notes on Linux as a guest 108 as 119 supply as few hd* devices as possible, and for the rest of the disks, [all …]
|
A D | xen-tscmode.7.pod | 44 This last is the US$64,000 question as it may be very difficult 47 that uses rdtsc must be assumed to be TSC-sensitive and, as we 74 This is the same as prior to Xen 4.0 and is the best choice if it 128 so it is often used as a foundation for performance monitoring. 131 sometimes used as a random number or a unique sequence identifier, 157 invariant as "TSC-safe" and any hardware on which TSC is not (or 158 may not remain) synchronized as "TSC-unsafe". 166 machine as "TSC-sensitive"; apps that don't use TSC, or do use 168 are unimportant as "TSC-resilient". 229 as will be seen in the next section. [all …]
|
A D | xl-numa-placement.7.pod | 18 defined as a set of processor cores (typically a physical CPU package) and 21 NUMA awareness becomes very important as soon as many domains start 49 created, as the most of its memory is allocated at that time and can 60 such a I<cpupool> with the "pool=" config option (as documented in our 84 as the vCPU can potentially run everywhere, it just prefers some pCPUs 144 affects NUMA placement and memory accesses as, in this case, the 196 spot for the domain with at least as much free memory as it has configured 197 to have, and as much pCPUs as it has vCPUs. After that, the actual 226 performance for the guest, as it avoid spreading its memory among 248 bits set, as it is by default), or domain creation will fail with [all …]
|
/xen/docs/misc/ |
A D | xenstore.txt | 90 Except as otherwise noted, reserved values are believed to be sent as 96 Error replies are as follows: 120 Integer domid, represented as decimal number 0..65535. 123 represented as integers; unless otherwise specified it 129 reply payloads as applicable: 164 GET_PERMS <path>| <perm-as-string>|+ 165 SET_PERMS <path>|<perm-as-string>|+? 166 <perm-as-string> is one of the following 220 as described above. req_id and tx_id are both 0. 330 print <string> to syslog (xenstore runs as daemon) or [all …]
|
A D | efi.pandoc | 2 recommended, as 4.5.x was probably never really tested for this purpose) and 10 normal Image format, so a single binary may be booted as an Image file or as an 11 EFI application. When booted as an EFI application, Xen requires a 12 configuration file as described below unless a bootloader, such as GRUB, has 20 `EFI_MOUNTPOINT` is overridden as needed, should the default of `/boot/efi` not 28 separators will be tried) to be present in the same directory as the binary. 44 thus look like this (`#` serving as comment character): 76 The options should in general be the same as is used when booting
|
A D | stubdom.txt | 34 - Block devices for target domain are connected as PV disks to stubdomain, 36 - Network devices for target domain are connected as PV nics to stubdomain, 86 - Block devices for target domain are connected as PV disks to stubdomain, 88 - Network devices for target domain are connected as PV nics to stubdomain, 96 /vm/<target-uuid>/image/dm-argv xenstore dir, each argument as separate key 107 - target domain's disks are available as /dev/xvd[a-z] 144 - use pv-grub.gz as kernel: 148 - set the path to menu.lst, as seen from the domU, in extra: 152 or you can provide the content of a menu.lst stored in dom0 by passing it as a 179 will be seen by PV-GRUB as (hd0), not (hd0,6), since GRUB will not see any [all …]
|
A D | kconfig-macro-language.rst | 24 and handles as if the source file were input like follows:: 47 dependency as explained in kconfig-language.txt. 53 Like in Make, a variable in Kconfig works as a macro variable. A macro 57 a syntax error. The curly brace form as in ${CC} is not supported either. 67 Its righthand side is simply stored as the value of the variable without 73 side was originally defined as a simple variable. Otherwise, its evaluation is 80 You can consider the parameterized reference as a function. (more precisely, 100 zero argument for built-in functions, such as $(fileno), $(lineno). You could 101 consider those as "built-in variable", but it is just a matter of how we call 111 and returned as the value of the function. Every newline in the output is [all …]
|
A D | printk-formats.txt | 6 Raw buffer as hex string: 21 Print a bitmap as either a hex string, or a range list. Bitmap length 48 The domain part as above, with the vcpu_id printed in decimal.
|
A D | netif-staging-grants.pandoc | 29 region. In some (physical) NICs this is known as header/data split. 38 when one wants to resort to a copy-based as opposed to grant copy/map. 113 network stack goes as following: 190 remaining slots as frags for the rest of the data ] 271 on backend, as opposed to a grant copy. 318 aggregating as much copies as possible.] 328 choose to merge as much as data from different pages into this single gref, 372 processed in the responses are then added as frags. 399 would need to aggregate as much as grant ops as possible (step 1) and could 401 as previously proposed [all …]
|
/xen/docs/hypervisor-guide/x86/ |
A D | how-xen-boots.rst | 13 A build of xen produces ``xen.gz`` and optionally ``xen.efi`` as final 47 image be loaded as high as possible below the 4G boundary, with 2M alignment. 48 Entry is still via the ``start`` symbol as with MB1, and still in 32bit mode. 51 ``ExitBootServices()`` not be called, and register ``__efi_mb2_start`` as an 56 ``__pvh_start`` as the entrypoint, entered in 32bit mode. 64 ``xen-syms``, then repackaging the result as an ELF32 object with a single 83 ``efi_start`` as its entry symbol.
|
/xen/docs/features/ |
A D | sched_rtds.pandoc | 24 RTDS is not in use by default. In order to use it as the Xen scheduler 29 Once the system is live, for creating a cpupool with RTDS as its 30 scheduler, either compile a cpupool configuration file, as described 31 in `docs/man/xlcpupool.cfg.pod.5` (and as exemplified in 37 as follows: 64 deterministic and statically analyzable behavior (as per the 77 * create a cpupool with RTDS as its scheduler, 91 * set the scheduling parameters such as it has a 50% reservation, with
|
A D | dom0less.pandoc | 5 system without an control domain (often referred to as "dom0"). Each 43 If we want to add one DomU with Image-DomU as the DomU kernel 44 and ramdisk-DomU as DomU ramdisk: 61 device tree adding a node under /chosen as follows: 101 - Some xl operations might not work as expected. xl is meant to be used 103 started by Xen at boot might not work as expected. 107 boot is the same as the native GIC version. 113 done from the control domain, using `xl vcpu-pin` as usual. It is not 134 node associated. By default DomU names are shown as '(null)' in the
|
A D | livepatch.pandoc | 23 Xen Live Patching has been available as tech preview feature since Xen 31 declare live patching as a 'Supported' feature on x86. 40 guests and it shall be treated as a security issue if this is not 47 functions are patched), it shall be treated as a security issue. 61 issue being inappropriate to live patch, this is not considered as a 65 Bugs in the live patch parsing code such as out-of-bounds reads 73 treated as a security issue.
|
A D | sched_credit2.pandoc | 18 Credit2 was designed as a general purpose scheduler, with particular 33 Once the system is live, for creating a cpupool with Credit2 as 34 its scheduler, either compile a cpupool configuration file, as 35 described in `docs/man/xlcpupool.cfg.pod.5` (and as exemplified 56 Global scheduling parameters, such as context switching rate 73 where Credit2 is used as the scheduler of a cpupool, and by also doing the
|
/xen/xen/arch/arm/ |
A D | Kconfig | 78 Allows a guest to use SBSA Generic UART as a console. The 132 to occur at the same time as another transaction to the same address 139 as it depends on the alternative framework, which will only patch 154 write instruction at the same time as a processor in another 157 incorrectly marked as dirty. 162 workaround, as it depends on the alternative framework, which will 177 the same time as a processor in another cluster is executing a cache 184 as it depends on the alternative framework, which will only patch 203 as it depends on the alternative framework, which will only patch 217 fault as the result of a Stage 1 fault for load crossing a [all …]
|
/xen/tools/ocaml/xenstored/ |
A D | symbol.mli | 7 * it under the terms of the GNU Lesser General Public License as published 21 compared in constant time (as opposite to strings) and should help the ocaml GC. *) 35 - mark all the knowns symbols as unused (with [mark_all_as_unused]); 36 - mark all the symbols really usefull as used (with [mark_as_used]); and
|
/xen/tools/examples/ |
A D | xlexample.pvhlinux | 14 # 128-bit UUID for the domain as a hexadecimal number. 35 # A list of 'vifspec' entries as described in 40 # A list of `diskspec' entries as described in
|
A D | xlexample.pvlinux | 11 # 128-bit UUID for the domain as a hexadecimal number. 37 # A list of 'vifspec' entries as described in 42 # A list of `diskspec' entries as described in
|
A D | xlexample.hvm | 14 # 128-bit UUID for the domain as a hexadecimal number. 36 # A list of 'vifspec' entries as described in 41 # A list of `diskspec' entries as described in
|
/xen/xen/tools/kconfig/tests/preprocess/escape/ |
A D | Kconfig | 6 # You can not pass commas directly to a function since they are treated as 12 # The following prints the text as-is. 37 # The following should print "$(X)" as well.
|
/xen/docs/designs/ |
A D | dmop.pandoc | 13 itself, such as with Track dirty VRAM (as used in VGA emulation). 15 to ensure it is not within restricted address ranges, such as kernel 26 DMOP hypercalls will continue to function as they can be audited. 82 doing this would be written as below. Note that care is taken to prevent 116 This leaves do_dm_op easy to implement as below:
|
/xen/docs/admin-guide/ |
A D | introduction.rst | 6 Xen is an open source, bare metal hypervisor. It runs as the most privileged 13 When Xen boots, dom0 is automatically started as well. Dom0 is a virtual 38 and knows how to drive various CPU internal devices such as IOMMUs, but
|
/xen/ |
A D | CODING_STYLE | 5 Xen hypervisor itself (xen/*) as well as various associated low-level 23 same as the code _outside_ the block. e.g. 37 Space characters are used to spread out logical statements, such as in 187 particularly as the code evolves over time 191 - To detect violations of assumptions as early as possible 225 ASSERT() will allow violation of assumptions to be detected as soon as 232 call stack may not realize that the domain is now dying as a result of
|