Home
last modified time | relevance | path

Searched refs:boundary (Results 1 – 25 of 26) sorted by relevance

12

/qemu/tests/qemu-iotests/
H A D004.out4 write before image boundary
8 write into image boundary
11 write at image boundary
14 write past image boundary
17 pwrite past image boundary
20 writev past image boundary
23 read before image boundary
27 read into image boundary
30 read at image boundary
33 read past image boundary
[all …]
H A D171.out19 write before image boundary
23 write across image boundary
26 write at image boundary
29 write after image boundary
35 read before image boundary
39 read across image boundary
42 read at image boundary
45 read after image boundary
118 write at image boundary
134 read at image boundary
[all …]
H A D263.out10 == write two 512 byte sectors on a cluster boundary ==
29 == write two 512 byte sectors on a cluster boundary ==
/qemu/hw/net/
H A Dne2000.c153 int avail, index, boundary; in ne2000_buffer_full() local
160 boundary = s->boundary << 8; in ne2000_buffer_full()
161 if (index < boundary) in ne2000_buffer_full()
162 avail = boundary - index; in ne2000_buffer_full()
164 avail = (s->stop - s->start) - (index - boundary); in ne2000_buffer_full()
311 s->boundary = val; in ne2000_ioport_write()
380 ret = s->boundary; in ne2000_ioport_read()
614 VMSTATE_UINT8(boundary, NE2000State),
H A Dne2000.h17 uint8_t boundary; member
/qemu/target/hexagon/imported/
H A Dmacros.def818 fRNDN, /* Rounding to a boundary */
824 fCRNDN, /* Rounding to a boundary */
830 fADD128, /* Rounding to a boundary */
835 fSUB128, /* Rounding to a boundary */
840 fSHIFTR128, /* Rounding to a boundary */
846 fSHIFTL128, /* Rounding to a boundary */
852 fAND128, /* Rounding to a boundary */
858 fCAST8S_16S, /* Rounding to a boundary */
863 fCAST16S_8S, /* Rounding to a boundary */
/qemu/docs/specs/
H A Dppc-spapr-numa.rst58 boundary is the most significant to application performance, followed by
61 that matches the relevancy of the boundary itself. Resources that belongs
62 to the same first boundary will have the shortest distance from each
113 P1 and P2 does not have a common performance boundary. Since this is a one level
114 NUMA configuration, distance between them is one boundary above the first
119 is considered to be on the same performance boundary:
133 P1 and P2 belongs to the same first order boundary. The distance between then
H A Drocker.txt173 byte boundary. Each descriptor ring will have these registers:
349 Various buffer address and sizes should be tested to verify no address boundary
350 issue exists. In particular, buffers that start on odd-8-byte boundary and/or
/qemu/host/include/generic/host/
H A Dload-extract-al16-al8.h.inc17 * cross an 16-byte boundary then the access must be 16-byte atomic,
/qemu/host/include/loongarch64/host/
H A Dload-extract-al16-al8.h.inc20 * cross an 16-byte boundary then the access must be 16-byte atomic,
/qemu/host/include/aarch64/host/
H A Dload-extract-al16-al8.h.inc20 * cross an 16-byte boundary then the access must be 16-byte atomic,
/qemu/docs/interop/
H A Dqcow2.txt72 starts. Must be aligned to a cluster boundary.
76 starts. Must be aligned to a cluster boundary.
86 starts. Must be aligned to a cluster boundary.
332 starts. Must be aligned to a cluster boundary.
346 boundary.
479 boundary.
572 cluster boundary. If the offset is 0 and bit 63 is clear,
583 cluster or sector boundary! If cluster_bits is
678 snapshot starts. Must be aligned to a cluster boundary.
760 a cluster boundary.
[all …]
H A Dparallels.txt182 Align header to 8 bytes boundary.
186 The above is followed by padding to the next 8 bytes boundary, then the
/qemu/host/include/x86_64/host/
H A Dload-extract-al16-al8.h.inc20 * cross an 16-byte boundary then the access must be 16-byte atomic,
/qemu/docs/devel/migration/
H A Dmapped-ram.rst96 | ... | | padding to next 1MB boundary |
106 | RAM_SAVE_FLAG_EOS | | padding to next 1MB boundary |
/qemu/accel/tcg/
H A Dldst_atomicity.c.inc62 * The pair exactly straddles the boundary.
68 * One of the pair crosses the boundary, and is non-atomic.
272 * not cross an 8-byte boundary. This means that we can perform an atomic
296 * boundary, but *does* cross an 8-byte boundary.
/qemu/docs/system/
H A Dgdb.rst233 in case of the TCG emulation, which is not considered a security boundary, this
/qemu/docs/
H A Dimage-fuzzer.txt176 vector (boundary values, e.g. max/min cluster size)
/qemu/docs/devel/
H A Dtcg.rst118 * The direct branch cannot cross a page boundary. Memory mappings
/qemu/hw/scsi/
H A Dtrace-events225 …offset, unsigned desc, uint32_t len) " offset=0x%x is out of a descriptor #%u boundary=0x%"PRIx32
/qemu/tcg/ppc/
H A Dtcg-target.c.inc801 /* Ensure that the prefixed instruction does not cross a 64-byte boundary. */
2545 * cross a page boundary. The trick is to add the access size-1
2547 * address overflow to the next page if we cross a page boundary,
/qemu/target/mips/tcg/
H A Dmicromips_translate.c.inc2979 /* make sure instructions are on a halfword boundary */
H A Dnanomips_translate.c.inc4503 /* make sure instructions are on a halfword boundary */
/qemu/tcg/mips/
H A Dtcg-target.c.inc1273 * verify that it does not cross a page boundary.
/qemu/target/s390x/tcg/
H A Dtranslate_vx.c.inc753 /* calculate the number of bytes until the next block boundary */

12