Searched refs:was (Results 1 – 25 of 82) sorted by relevance
1234
| /xen/xen/common/ |
| A D | README.source | 15 This file was originally imported from the Linux tree 21 This file was originally imported from the compcache project at 28 This directory was opriginally imported from the libelf 34 This directory was originally imported from the Device Tree 41 This file was originally imported from the LZ4 project 48 This directory was imported from the XZ Utils project
|
| /xen/docs/misc/ |
| A D | hvm-emulated-unplug.pandoc | 78 During xen-3.0.4 timeframe an unofficial unplug protocol was added to 79 the xen-platform-pci kernel module. The value 0x1 was written to offset 80 0x4 in the memory region of the Xen Platform PCI Device. This was done 82 unplug of all NIC, IDE and SCSI devices. This was used in all SUSE 84 SLES11SP4/SLE12 the official protocol was used. 88 During Xen-3.0 timeframe an unofficial unplug protocol was used in 89 Novells VMDP. Depending on how VMDP was configured it would control all 91 was written to offset 0x4 in the memory region of the Xen Platform PCI 92 Device. This was supposed to unplug NIC, IDE and SCSI devices. If VMDP 93 was configured to control just NIC devices it would write the value 0x2 [all …]
|
| A D | xenmon.txt | 18 o The number of times that a domain was scheduled to run (ie, dispatched) over 42 the amount of time the domain spent not needing/wanting the cpu because it was 51 This is how much cpu time was allocated to the domain by the scheduler; This is
|
| A D | dump-core-format.txt | 8 Its format was changed to be based on ELF format because elf format is easily 244 - EI_CLASS member of elf header was changed to ELFCLASS64 independent of 247 - .xen_ia64_mapped_regs section was made only for ia64 PV domain.
|
| A D | efi.pandoc | 2 recommended, as 4.5.x was probably never really tested for this purpose) and 62 Specifies the section to use for booting, if none was specified on the command
|
| A D | xenstore.txt | 222 <epath> is the event's path, ie the actual path that was 223 modified; however if the event was the recursive removal of an 225 <wpath> (rather than the actual path which was removed). So 228 Iff <wpath> for the watch was specified as a relative pathname,
|
| A D | crashdb.txt | 45 There is code which was once intended to make it possible to resume
|
| /xen/m4/ |
| A D | README.source | 8 This file was fetched from 25 The last synch was from commit: 40 systemd.m4 was contributed to by Luis R. Rodriguez <mcgrof@do-not-panic.com>,
|
| /xen/xen/tools/kconfig/ |
| A D | README.source | 8 The kconfig directory was originally imported from the linux kernel
|
| /xen/xen/crypto/ |
| A D | README.source | 12 This file was developed by Ted Krovetz and Wei Dai (more details
|
| /xen/xen/include/crypto/ |
| A D | README.source | 12 This file was developed by Ted Krovetz and Wei Dai (more details
|
| /xen/stubdom/grub.patches/ |
| A D | 11graphics-keyboard.diff | 12 /* Key was pressed, show which entry is selected before GETKEY,
|
| A D | 40ext3_256byte_inode.diff | 56 + __u32 s_mkfs_time; /* When the filesystem was created */
|
| /xen/tools/libxl/ |
| A D | libxl_fork.c | 328 struct sigaction was; in sigchld_removehandler_core() local 334 r = sigaction(SIGCHLD, &sigchld_saved_action, &was); in sigchld_removehandler_core() 336 assert(!(was.sa_flags & SA_SIGINFO)); in sigchld_removehandler_core() 337 assert(was.sa_handler == sigchld_handler); in sigchld_removehandler_core()
|
| A D | CODING_STYLE | 309 printf("a was 5.\n"); 311 printf("a was 6.\n"); 313 printf("a was something else entirely.\n"); 317 printf("a was 5.\n");
|
| /xen/tools/xl/ |
| A D | CODING_STYLE | 182 printf("a was 5.\n"); 184 printf("a was 6.\n"); 186 printf("a was something else entirely.\n"); 190 printf("a was 5.\n");
|
| /xen/tools/flask/policy/modules/ |
| A D | guest_features.te | 14 # Without XSM, this is enabled only if the Xen was compiled in debug mode.
|
| /xen/tools/firmware/etherboot/ |
| A D | README | 22 Previously, an image from Rom-o-matic.net was provided here, fetched
|
| /xen/docs/misc/arm/device-tree/ |
| A D | booting.txt | 34 treated by Xen as if its compatible string was 39 if its compatible string was "multiboot,ramdisk"; for the 47 Note: This XSM Magic detection behavior was introduced by Xen 4.7.
|
| /xen/ |
| A D | configure | 1419 It was created by Xen Hypervisor $as_me 4.14, which was 1420 generated by GNU Autoconf 2.69. Invocation command line was 1714 $as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} 2859 This file was extended by Xen Hypervisor $as_me 4.14, which was 2860 generated by GNU Autoconf 2.69. Invocation command line was
|
| A D | CONTRIBUTING | 70 (a) The contribution was created in whole or in part by me and I 82 (c) The contribution was provided directly to me by some other
|
| /xen/docs/man/ |
| A D | xen-tscmode.7.pod | 135 On most older SMP and early multi-core machines, TSC was not synchronized 137 one processor, then was moved by the OS to another processor, then read 145 machines, the TSC was synchronized but if one processor were to enter 237 was properly initialized to zero on all processors at boot-time
|
| A D | xl-disk-configuration.5.pod | 85 the target was already specified as a positional parameter. This 469 In xend and old versions of libxl it was necessary to specify the 490 In xend and old versions of libxl it was necessary to specify the
|
| /xen/docs/specs/ |
| A D | libxc-migration-stream.pandoc | 169 xen_major The Xen major version when this image was saved. 171 xen_minor The Xen minor version when this image was saved. 546 > *This record was only present for transitionary purposes during 776 This assumes the presence of the extended-info chunk which was
|
| A D | libxl-migration-stream.pandoc | 32 * The legacy `libxc` format was inextensible, causing inextensibility in the 83 bit 1: Legacy Format. If set, this stream was created by
|
Completed in 46 milliseconds
1234