Home
last modified time | relevance | path

Searched full:however (Results 1 – 25 of 510) sorted by relevance

12345678910>>...21

/qemu/include/exec/
H A Dtarget_long.h14 * Usually this should only be included via cpu-defs.h however for
16 * object we can include directly. However the build-system must
/qemu/docs/devel/
H A Dlockcnt.rst15 by stashing away its ``next`` pointer. However, ``ioh->fd_write`` could
31 If however this loop must also be reentrant, i.e. it is possible that
138 However, critical sections are easy to forget since you have to do
157 However, these are usually not a problem if any of the following
170 frequent and can happen on a fast path; however: 1) it is almost never
H A Dtcg-plugins.rst20 process. However the project reserves the right to change or break the
86 However the following assumptions can be made:
103 instrument them directly. However asynchronous interrupts will not
H A Drust.rst24 However, QEMU's build system also tries to be easy to use for people who
67 code. Note however that you cannot *build* or run tests via ``cargo``, because
190 Sometimes however a name appears multiple times in the QOM class hierarchy,
208 In this case, however, no prefix is needed:
344 code and it's important that it is idiomatic. However, you should strive
H A Dstyle.rst146 However, if there is an obvious subsystem-specific prefix it should be
219 On the other hand, however, it's often best to move that #ifdef/#ifndef
413 you can use "include/qemu/typedefs.h" for example. However, as a matter
465 approach. However for larger allocations where we could realistically
555 argument...) However there are a few areas where we allow ourselves to
719 will ensure s->lock is released however the function is exited. The
832 However, you can use '0x' for such groups if you want. Anyway, be sure that
H A Dcontrol-flow-integrity.rst119 an assertion. However, other sanitizers such as address and ub sanitizers
122 There is, however, an interesting use case in using CFI in conjunction with
/qemu/docs/system/
H A Dvm-templating.rst18 new VMs are able to read template VM memory; however, any modifications
59 configure VM RAM to be based on a template VM RAM file; however, the VM
93 These technologies rely on shared memory, however, the template VMs
H A Dauthz.rst9 client this may be sufficient. It is common, however, for the identity database
28 It is possible, however, to enable mutual verification by requiring that
124 In most cases, however, the next driver will be more suitable.
/qemu/docs/interop/
H A Ddbus.rst27 easier to apprehend and debug than a mesh. However, it is wise to
42 various metadata attributes, however, this is alone is not generally
H A Dprl-xml.rst106 use padding set to 1; however this case is not covered
191 However, it is not recommended to use this
/qemu/docs/
H A Dpci_expander_bridge.txt40 however, PXBs can be placed only under the root bus.
49 …However, the bus behind is exposed through ACPI as a primary PCI bus and starts a new PCI hierarch…
H A Dxen-save-devices-state.txt8 however it is also possible to save the state of all devices to file,
/qemu/tests/qemu-iotests/
H A D21637 # fingers crossed. However, that sneaking does not work so well when
44 # A COR filter node, however, can request the proper permissions for
H A D21462 # 'qemu-img check' however doesn't see anything wrong because it
85 # The refcount data is however wrong because due to the increased size
/qemu/docs/devel/migration/
H A Dpostcopy.rst138 however when a page request is received from the destination, the dirty page
194 pages, however during postcopy the CPUs are stopped and nothing should
240 However, if any of the missing pages got accessed on destination VM, the VM
261 hugepages works well, however 1GB hugepages are likely to be problematic
/qemu/linux-user/openrisc/
H A Dtarget_syscall.h7 * However, elfload.c wants this name.
/qemu/semihosting/
H A Dconfig.c12 * linux-user targets. However in that use case no configuration of
15 * The config module is common to all system targets however as vl.c
/qemu/scripts/oss-fuzz/
H A Dinstrumentation-filter-template9 # We don't care about coverage over fuzzer-specific code, however we should
/qemu/.github/workflows/
H A Dlockdown.yml26 functionality). However, we get a lot of patches, and so we have some
/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h31 * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
80 * device driver can start with a clean state. However, in specific
/qemu/tests/uefi-test-tools/
H A DLICENSE22 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
/qemu/bsd-user/freebsd/
H A Dtarget_os_ucontext.h13 * included AFTER the MD target_mcontext_t is defined, however, so can't
/qemu/tests/tcg/x86_64/
H A DMakefile.softmmu-target5 # with standard compiler flags however so we can support both by
/qemu/tests/tcg/i386/
H A DMakefile.softmmu-target5 # with standard compiler flags however so we can support both by
/qemu/pc-bios/
H A Dedk2-licenses.txt49 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
130 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
332 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
553 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
646 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
712 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
772 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
833 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

12345678910>>...21