| /xen-4.10.0-shim-comet/docs/misc/arm/ |
| A D | booting.txt | 30 Xen relies on some settings the firmware has to configure in EL3 before starting Xen.
|
| /xen-4.10.0-shim-comet/tools/libxl/ |
| A D | libxl_pci.c | 112 …bxl__device_pci_add_xenstore(libxl__gc *gc, uint32_t domid, libxl_device_pci *pcidev, int starting) in libxl__device_pci_add_xenstore() argument
137 if (!starting && domtype == LIBXL_DOMAIN_TYPE_PV) { in libxl__device_pci_add_xenstore()
148 if (!starting) in libxl__device_pci_add_xenstore()
982 static int do_pci_add(libxl__gc *gc, uint32_t domid, libxl_device_pci *pcidev, int starting) in do_pci_add() argument
1104 if (!starting) in do_pci_add()
1105 rc = libxl__device_pci_add_xenstore(gc, domid, pcidev, starting); in do_pci_add()
1185 int libxl__device_pci_add(libxl__gc *gc, uint32_t domid, libxl_device_pci *pcidev, int starting) in libxl__device_pci_add() argument
1275 if ( do_pci_add(gc, domid, pcidev, starting) ) in libxl__device_pci_add()
|
| A D | libxl_internal.h | 1407 …n int libxl__device_pci_add(libxl__gc *gc, uint32_t domid, libxl_device_pci *pcidev, int starting);
|
| /xen-4.10.0-shim-comet/tools/hotplug/Linux/init.d/ |
| A D | sysconfig.xencommons.in | 86 # Additional arguments for starting the xenstore domain.
|
| /xen-4.10.0-shim-comet/tools/ocaml/xenstored/ |
| A D | parse_arg.ml | 55 ("--restart", Arg.Set restart, "Read database on starting");
|
| A D | xenstored.ml | 384 debug "periodic_ops starting";
|
| /xen-4.10.0-shim-comet/docs/man/ |
| A D | xen-vbd-interface.markdown.7 | 30 conventionally starting at 0 for the first disk.
120 to use pure xvd* devices starting at xvde. Modern PV-on-HVM drivers
|
| A D | xl-numa-placement.pod.7 | 73 If using the credit1 scheduler, and starting from Xen 4.3, the scheduler
83 less strict than what it (also starting from 4.5) is called hard affinity,
183 scheduler and starting from Xen 4.3) will comply with it. Starting from
|
| A D | xl-network-configuration.pod.5 | 32 Each device has a C<DEVID> which is its index within the vif list, starting from 0.
|
| A D | xen-tscmode.pod.7 | 44 will see, this is the default starting in Xen 4.0.
264 This bit is used by some OS's, and specifically by Linux starting with
|
| A D | xl.cfg.pod.5.in | 136 Allow the guest to bring up a maximum of M vCPUs. When starting the guest, if
|
| /xen-4.10.0-shim-comet/docs/features/ |
| A D | sched_credit.pandoc | 57 Dealing with such complexity is starting to be an issue. Odd behavior
|
| A D | migration.pandoc | 93 scenarios, which will involve starting with VMs from Xen 4.5
|
| /xen-4.10.0-shim-comet/docs/misc/arm/device-tree/ |
| A D | booting.txt | 29 Xen will examine each module, starting from the second
|
| /xen-4.10.0-shim-comet/docs/misc/ |
| A D | pvh.markdown | 55 this hypercall allows starting the vCPU in several modes (16/32/64bits),
|
| A D | vtd-pi.txt | 321 (starting from Nehalem) ignore TPR value, and instead supported two other
|
| A D | livepatch.markdown | 735 - The CHECKED state is the starting one achieved with *XEN_SYSCTL_LIVEPATCH_UPLOAD* hypercall.
|
| /xen-4.10.0-shim-comet/ |
| A D | INSTALL | 135 Instead of starting the tools in dom0 with sysv runlevel scripts they
137 receive the communication socked directly from systemd. So starting it
|
| /xen-4.10.0-shim-comet/stubdom/grub.patches/ |
| A D | 10graphics.diff | 2249 /* If no acceptable config file, goto command-line, starting
|
| /xen-4.10.0-shim-comet/xen/tools/kconfig/ |
| A D | zconf.tab.c_shipped | 568 First, the terminals, then, starting at YYNTOKENS, nonterminals. */
|
| /xen-4.10.0-shim-comet/stubdom/ |
| A D | lwip.patch-cvs | 298 + it is set when we succeeded starting. */
|
| /xen-4.10.0-shim-comet/tools/ |
| A D | configure | 2001 something starting with __ and the normal name is an alias. */
|
| /xen-4.10.0-shim-comet/tools/firmware/rombios/ |
| A D | rombios.c | 8967 ;; diskette 0,1 operational starting state
|