Home
last modified time | relevance | path

Searched refs:order (Results 1 – 25 of 154) sorted by relevance

1234567

/qemu/docs/system/
A Dbootindex.rst1 Managing device boot order with bootindex properties
5 which order it should look for a bootable OS on which devices.
6 A simple way to set this order is to use the ``-boot order=`` option,
11 The ``bootindex`` properties are used to determine the order in which
14 boot priority. There is no particular order in which devices with no
19 not support ``-boot order=``; on those machines you must always
69 Mixing bootindex and boot order parameters
73 with the ``-boot order=...`` (or ``-boot once=...``) parameter. The guest
/qemu/target/s390x/
A Dsigp.c355 static int handle_sigp_single_dst(S390CPU *cpu, S390CPU *dst_cpu, uint8_t order, in handle_sigp_single_dst() argument
370 order != SIGP_CPU_RESET && in handle_sigp_single_dst()
371 order != SIGP_INITIAL_CPU_RESET) { in handle_sigp_single_dst()
375 switch (order) { in handle_sigp_single_dst()
451 int handle_sigp(CPUS390XState *env, uint8_t order, uint64_t r1, uint64_t r3) in handle_sigp() argument
464 switch (order) { in handle_sigp()
471 ret = handle_sigp_single_dst(cpu, dst_cpu, order, param, status_reg); in handle_sigp()
476 trace_sigp_finished(order, CPU(cpu)->cpu_index, in handle_sigp()
A Dtrace-events15 sigp_finished(uint8_t order, int cpu_index, int dst_index, int cc) "SIGP: Finished order %u on cpu …
/qemu/qapi/
A Dintrospect.json40 # The order of the various SchemaInfo is unspecified; however, all
93 # particular order. (since 4.1 for object types, 4.2 for
157 # @members: the enum type's members, in no particular order (since
161 # order. Redundant with @members. Just for backward
185 # particular order.
212 # order.
219 # The variants are in no particular order, and may even differ
220 # from the order of the values of the enum type of the @tag.
247 # particular order. (since 5.0)
276 # @members: the alternate type's members, in no particular order. The
A Dqapi-schema.json39 # Documentation generated with qapi-gen.py is in source order, with
42 # stable order, it's best to include each sub-schema just once, or
/qemu/hw/ppc/
A Dmac_oldworld.c199 for (i = 0; machine->boot_config.order[i] != '\0'; i++) { in ppc_heathrow_init()
206 if (machine->boot_config.order[i] >= 'a' && in ppc_heathrow_init()
207 machine->boot_config.order[i] <= 'f') { in ppc_heathrow_init()
208 ppc_boot_device = machine->boot_config.order[i]; in ppc_heathrow_init()
212 if (machine->boot_config.order[i] >= 'c' && in ppc_heathrow_init()
213 machine->boot_config.order[i] <= 'd') { in ppc_heathrow_init()
214 ppc_boot_device = machine->boot_config.order[i]; in ppc_heathrow_init()
A Dmac_newworld.c244 for (i = 0; machine->boot_config.order[i] != '\0'; i++) { in ppc_core99_init()
245 if (machine->boot_config.order[i] >= 'c' && in ppc_core99_init()
246 machine->boot_config.order[i] <= 'f') { in ppc_core99_init()
247 ppc_boot_device = machine->boot_config.order[i]; in ppc_core99_init()
/qemu/target/i386/
A Dops_sse.h421 r0 = v->Q(((order & 1) & 1) + i); in glue()
425 order >>= 2; in glue()
2258 order >>= 2; in glue()
2430 switch (order & 3) { in helper_vpermdq_ymm()
2450 switch ((order >> 4) & 3) { in helper_vpermdq_ymm()
2474 if (order & 0x8) { in helper_vpermdq_ymm()
2478 if (order & 0x80) { in helper_vpermdq_ymm()
2487 r0 = s->Q(order & 3); in helper_vpermq_ymm()
2488 r1 = s->Q((order >> 2) & 3); in helper_vpermq_ymm()
2489 r2 = s->Q((order >> 4) & 3); in helper_vpermq_ymm()
[all …]
/qemu/storage-daemon/qapi/
A Dqapi-schema.json18 # Documentation generated with qapi-gen.py is in source order, with
21 # stable order, it's best to include each sub-schema just once, or
/qemu/docs/devel/testing/
A Dacpi-bits.rst26 in order to write our test routines that exercise and test the bios. This is
79 for their tests. In order to enable debugging, you can set **V=1**
86 In order to run this test, please perform the following steps from the QEMU
98 for more information about the run or in order to diagnoze issues.
128 example, in order to change cpuid related tests, copy the following
145 The tests have an extension .py2 in order to indicate that:
A Dblkdebug.rst63 (optional) the engine must be in this state number in order for this
73 (optional) a sector number that the request must overlap in order to
132 the attribute in order for the rule to match.
159 (optional) the engine must be in this state number in order for this
/qemu/contrib/gitdm/
A Dfiletypes.txt30 # The list should keep an order, so filetypes can be counted properly.
33 # If there is an filetype which is not in order but has values, it will
36 order build,interface,tests,code,documentation,devel-doc,blobs
/qemu/docs/devel/
A Datomics.rst7 CPUs perform independent memory operations effectively in random order.
10 to instruct the compiler and the CPU to restrict the order to something
53 optimizations already ensures the correct order of execution. In this
66 operations of all the processors were executed in some sequential order,
68 in the order specified by its program".
120 other accesses of which at least one is a write. In order to ensure this,
159 Memory barriers control the order of references to shared memory.
394 opposite order as the "reading" thread. This is expected: stores
458 sequential consistency: there is a single order in which the
461 - however, according to the C11 memory model that QEMU uses, this order
A Dtcg.rst23 evaluate instructions. In order to achieve a good speed, the
52 In order to accelerate the cases where the TB for the new
148 matches the target instructions in memory in order to handle
178 In order to avoid flushing the translated code each time the MMU
182 In order to avoid invalidating the basic block chain when MMU mappings
A Dreplay.rst76 While the unlocks are usually in the reverse order, this is not
91 host clock. And VM state changes should preserve their order. Their relative
92 order in replay mode must replicate the order of callbacks in record mode.
93 To preserve this order we use checkpoints. When a specific clock is processed
211 Avoid accessing other devices' state, because the order of saving/restoring
/qemu/tests/qapi-schema/
A Dreserved-type-list.json4 # in order to let this compile
/qemu/hw/nvram/
A Dfw_cfg.c822 void fw_cfg_set_order_override(FWCfgState *s, int order) in fw_cfg_set_order_override() argument
825 s->fw_cfg_order_override = order; in fw_cfg_set_order_override()
850 int order; member
909 return fw_cfg_order[i].order; in get_fw_cfg_order()
927 int order = 0; in fw_cfg_add_file_callback() local
944 order = get_fw_cfg_order(s, filename); in fw_cfg_add_file_callback()
946 index > 0 && order < s->entry_order[index - 1]; in fw_cfg_add_file_callback()
990 s->entry_order[index] = order; in fw_cfg_add_file_callback()
/qemu/scripts/coccinelle/
A Dtcg_gen_extract.cocci37 def Mn(order): # Mersenne number
38 return (1 << order) - 1
/qemu/docs/specs/
A Divshmem-spec.rst7 and the host. In order for all guests to be able to pick up the
187 On connect, the server sends the following messages in order:
203 vector 0,..,N-1, in order. If the client is configured for fewer
210 order. If the client is configured for fewer vectors, it closes
238 byte order to the respective file descriptor.
/qemu/scripts/
A Dgit.orderfile2 # order file for git, to produce patches which are easier to review
/qemu/hw/block/
A Dxen-block.c182 unsigned int order, nr_ring_ref, *ring_ref, event_channel, protocol; in xen_block_connect() local
200 &order) != 1) { in xen_block_connect()
211 order <= blockdev->props.max_ring_page_order) { in xen_block_connect()
214 nr_ring_ref = 1 << order; in xen_block_connect()
231 error_setg(errp, "invalid ring-page-order (%d)", order); in xen_block_connect()
/qemu/docs/interop/
A Dqmp-spec.rst41 be in a certain order. However, in real protocol usage they can be in
42 ANY order, thus no particular order should be assumed. On the other
43 hand, use of json-array elements presumes that preserving order is
80 baseline specification; the order of elements in this array has no
127 order.
/qemu/docs/devel/migration/
A Duadk-compression.rst118 UADK and char devices are created in dev directory. In order to access resources
138 IO page tables. This may impact the performance. In order to mitigate this,
/qemu/docs/
A Dmemory-hotplug.txt12 In order to be able to hotplug memory, QEMU has to be told how many
80 In order to be able to hot unplug pc-dimm device, QEMU has to be told the ids
/qemu/.gitlab-ci.d/
A Dbase.yml13 # The order of rules defined here is critically important.
14 # They are evaluated in order and first match wins.

Completed in 64 milliseconds

1234567