Home
last modified time | relevance | path

Searched refs:up (Results 1 – 25 of 106) sorted by relevance

12345

/xen/tools/xenstore/
A DTODO2 are omissions of important but necessary things. It is up to the
9 - Multi-root transactions, for setting up front and back ends at same time.
/xen/tools/hotplug/Linux/
A Dxen-network-common.sh131 ip link set dev ${dev} up || true
139 ip link set dev ${dev} up
A Dvif-route28 ifconfig ${dev} ${main_ip} netmask 255.255.255.255 up
A Dvif-openvswitch85 do_or_die ip link set $dev up
A Dvif-nat169 do_or_die ip link set dev "${dev}" up arp on
/xen/tools/fuzz/
A DREADME.afl52 In order to speed up the process of checking total coverage,
54 the speed-up effect should be similar to that of using afl-clang-fast.
61 binary; so coverage data will always show up in the build directory no
A DREADME.oss-fuzz12 inside xen.git so that they can be kept up to date.
27 Please refer to official oss-fuzz documents for the most up-to-date
/xen/xen/arch/x86/
A Dsysctl.c117 bool up = (bool)data; in smt_up_down_helper() local
121 opt_smt = up; in smt_up_down_helper()
129 if ( !up && core_parking_remove(cpu) ) in smt_up_down_helper()
132 ret = up ? cpu_up_helper(_p(cpu)) in smt_up_down_helper()
154 up ? "enabled" : "disabled", CPUMASK_PR(&cpu_online_map)); in smt_up_down_helper()
/xen/
A DCODING_STYLE142 Passing errors up the stack should be used when the caller is already
146 domain_crash() should be used when passing errors up the stack is too
147 difficult, and/or when fixing up state of a guest is impractical, but
148 where fixing up the state of Xen will allow Xen to continue running.
152 BUG_ON() should be used when you can’t pass errors up the stack, and
171 * Programmers can try to handle the case gracefully -- fixing up
199 when fixing the state is straightforward, then fixing up the state and
231 Note however that domain_crash() has its own traps: callers far up the
/xen/docs/misc/
A Dnetif-staging-grants.pandoc20 only ones performing really good (up to 80 Gbit/s in few CPUs), usually
34 protocol by adding the possibility of guests setting up a list of grants that
35 are set up at device creation and revoked at device freeing - without taking
181 18) *Linux specific*: Setup up a `GNTTABOP_copy` to copy up to 128 bytes to this small
201 22) Set up gso info requested by frontend [optional]
215 27.1) Set up `GNTTABOP_unmap_grant_ref` ops for the designated packet pages.
327 [ It's up to the backend to choose how it fills this data. E.g. backend may
331 5) Sets up flags/checksum info on first request.
341 10) Sets up extra info (e.g. GSO descriptor) [optional] repeat step 8).
475 looked up in this table and uses the underlying page if it already exists a
[all …]
A Dvtd-pi.txt17 per vector, for up to 256 vectors).
113 look-up an entry from the memory-resident interrupt-remap-table. Unlike
132 5. Introduce a new global vector which is used for waking up the blocked vCPU.
217 - Introduce a new global vector which is used to wake up the blocked vCPU.
257 - Set 'NV' to ' pi_wakeup_vector ', so we can wake up the
281 case is that vCPU0 will never be woken up again since the wakeup event
283 another global vector, naming 'pi_wakeup_vector' to wake up the blocked vCPU.
A D9pfs.pandoc51 The transport protocol supports multiple rings up to the maximum
53 and can span multiple pages, up to the maximum supported by the backend
375 - write to array at position *prod* up to *cons*, wrapping around the circular
387 - read from array at position *cons* up to *prod*, wrapping around the circular
394 up to *cons*. The consumer takes care of reading only as many bytes as available
395 in the buffer up to *prod*.
/xen/docs/features/
A Dqemu-deprivilege.pandoc38 ## Setting up a group and userid range
43 aside for it. Setting up a group for all devicemodels to run at is
55 1. Most modern systems have 32-bit UIDs, and so can in theory go up
69 A final way to set up a separate process for qemus is to allocate one
/xen/tools/hotplug/NetBSD/
A Dvif-ip27 ifconfig $iface $xip up
A Dvif-bridge27 ifconfig $iface up
/xen/tools/hotplug/FreeBSD/
A Dvif-bridge28 ifconfig $iface_dev up
/xen/xen/arch/arm/
A DKconfig128 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI
150 erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected
173 erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache
195 erratum 832075 on Cortex-A57 parts up to r1p2.
214 erratum 834220 on Cortex-A57 parts up to r1p2.
/xen/docs/man/
A Dxen-vbd-interface.7.pandoc77 202 << 8 | disk << 4 | partition xvd, disks and partitions up to 15
78 8 << 8 | disk << 4 | partition sd, disks and partitions up to 15
84 The 1<<28 format handles disks up to (1<<20)-1 and partitions up to
/xen/m4/
A Dax_compare_version.m435 # eq0 - equal up to the length of the shorter version
36 # ne0 - not equal up to the length of the shorter version
37 # eqN - equal up to N sub-version levels
38 # neN - not equal up to N sub-version levels
A DREADME.source4 m4 sources we have picked up or developed.
/xen/xen/tools/kconfig/tests/auto_submenu/
A DKconfig26 This should line up with A0.
/xen/automation/build/suse/
A Dopensuse-leap.dockerfile10 RUN zypper ref && zypper up -y --no-recommends
A Dopensuse-tumbleweed.dockerfile10 RUN zypper ref && zypper up -y --no-recommends
/xen/xen/arch/x86/mm/shadow/
A Dprivate.h528 && sp->up == 0 ) in sh_get_ref()
529 sp->up = entry_pa; in sh_get_ref()
549 && sp->up == entry_pa ) in sh_put_ref()
550 sp->up = 0; in sh_put_ref()
/xen/tools/flask/policy/modules/
A Dguest_features.te30 # Linux, so without this they will show up in the logs. Since these

Completed in 23 milliseconds

12345