Searched refs:previous (Results 1 – 25 of 30) sorted by relevance
12
/xen/xen/common/ |
A D | bunzip2.c | 515 int pos, xcurrent, previous, gotcount; in read_bunzip() local 559 previous = xcurrent; in read_bunzip() 568 if (xcurrent != previous) in read_bunzip() 574 xcurrent = previous; in read_bunzip() 599 previous = get_next_block(bd); in read_bunzip() 600 if (previous) { in read_bunzip() 601 bd->writeCount = previous; in read_bunzip() 602 return (previous != RETVAL_LAST_BLOCK) ? previous : gotcount; in read_bunzip()
|
/xen/docs/features/ |
A D | hypervisorfs.pandoc | 52 previous interface versions, too (this implies that additions will always
|
/xen/docs/misc/arm/device-tree/ |
A D | guest.txt | 33 | | pointed to in previous entry.
|
A D | booting.txt | 91 The previous examples are compatible with Xen 4.5+ only.
|
/xen/xen/arch/x86/x86_64/compat/ |
A D | entry.S | 365 .previous 390 .previous
|
/xen/docs/ |
A D | configure | 1693 … "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 1694 $as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} 1698 $as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} 1708 $as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} 1712 $as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
|
/xen/docs/man/ |
A D | xl.conf.5.pod | 78 be in the previous releases. With the default option, hotplug scripts 149 previous C<xm> toolstack this can be configured to use the old C<SXP>
|
A D | xen-vtpmmgr.7.pod | 192 There is no direct upgrade supported from previous versions of the vtpmmgr
|
A D | xen-vtpm.7.pod | 30 This mini-os vTPM subsystem was built on top of the previous vTPM work done by
|
A D | xl-numa-placement.7.pod | 212 to previous placement and/or plain vCPU pinning) are considered
|
/xen/ |
A D | configure | 1709 … "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 1710 $as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} 1714 $as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} 1724 $as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} 1728 $as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
|
A D | CONTRIBUTING | 74 (b) The contribution is based upon previous work that, to the best
|
/xen/tools/ocaml/xenstored/ |
A D | history.ml | 32 * since the next element is the previous commit *)
|
/xen/docs/process/ |
A D | branching-checklist.txt | 94 Send message to committers and RM. Use previous mail as a template.
|
A D | release-technician-checklist.txt | 153 stable branch: usually, copy text from previous
|
/xen/xen/include/asm-x86/ |
A D | asm_defns.h | 70 .previous
|
/xen/stubdom/ |
A D | configure | 1787 … "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 1788 $as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} 1792 $as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} 1802 $as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} 1806 $as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
|
/xen/docs/misc/ |
A D | hypfs-paths.pandoc | 85 compatible with the previous functionality.
|
A D | kconfig-language.rst | 297 dependencies. If a menu entry somehow depends on the previous entry, it 298 can be made a submenu of it. First, the previous (parent) symbol must 681 in the previous subsection, work has been done however to express in boolean
|
A D | livepatch.pandoc | 559 * previous payload build-id dependency (.livepatch.depends section) 1064 * A single large patch that subsumes and replaces all previous ones. 1093 the previous payload or hypervisor during build time). 1096 the build-id of the previous payload in the stack.
|
A D | xen-command-line.pandoc | 640 is what tells for how long we give value to previous history 642 what happens is that we discard all previous history entirely. 645 to load changes, but also short-sighted about previous history 647 make the load balancer thoughtful of previous history (and 1357 all the necessary tables from the previous one following kexec which makes
|
/xen/xen/arch/arm/ |
A D | Kconfig | 86 This enables mitigation of bypassing of previous stores by speculative
|
/xen/xen/arch/x86/x86_64/ |
A D | entry.S | 741 subq $8,UREGS_rsp(%rsp) # add ec/ev to previous stack frame
|
/xen/docs/specs/ |
A D | libxc-migration-stream.pandoc | 102 _V_. If the previous Xen release produced version _V_ - 1 images,
|
/xen/tools/ |
A D | configure | 2390 … "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 2391 $as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} 2395 $as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} 2405 $as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} 2409 $as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
|
Completed in 56 milliseconds
12