Searched full:having (Results 1 – 25 of 174) sorted by relevance
1234567
117 # get in between it having started and it having completed)136 # path, so there is no point in having them in this list
5 # which requires padding while having a NULL qiov.
110 * having the 20-byte structure padded to 24 bytes on 64-bit architectures.138 * bytes, so it needs to be packed to avoid having it padded to 56228 * so it needs to be packed to avoid having it padded to 40 bytes on
16 sequential stream. Having the pages at fixed offsets also allows the54 that's the ideal scenario for mapped-ram migration. Not having to81 Instead of having a sequential stream of pages that follow the
103 # (1) Grow an image without having to allocate a new L2 table.104 # (2) Grow an image, having to allocate a new L2 table.105 # (3) Grow an image, having to grow the L1 table.
60 # having a multiple of 2^32 clusters64 # An offset of 32 PB results in qemu-img check having to allocate an in-memory
14 * having a functioning jump
7 having to make a full bootable image. It is very useful for fast Linux
9 useful for debugging hypervisors without having to jump through the
20 * Having both SpaprMachineState and MachineState as arguments
31 * SNaN inputs having no significant bits in the upper 23 bits of the in main()
6 * Currently ARM and RISC-V are unique in having support for
12 * already via xen_native.h, and having __XEM_TOOLS__ defined will have
31 * as well as both having struct attributes appended.
35 # created them for us having recognised and handled SVE.
89 * truly random sequence having the same proportion of zeros and ones as the117 * This represents the probability of a truly random sequence having the same
65 /* code path for having successfully executed the syscall */
74 * The LPCR:HR bit is a shortcut that avoids having to
71 * export a second time (which would decrease the refcount without having
48 * of children depend on their parent's callback having completed first.
64 /* code path for having successfully executed the syscall */
75 /* code path for having successfully executed the syscall */
77 /* code path for having successfully executed the syscall */
43 /// It is also possible to use printf-style formatting, as well as having a
78 /* code path for having successfully executed the syscall */