Searched refs:zeroed (Results 1 – 19 of 19) sorted by relevance
| /openbmc/phosphor-mboxd/vpnor/test/ |
| H A D | tmpd.hpp | 48 std::vector<char> zeroed(part.data.actual, 0); in VpnorRoot() local 51 .write(zeroed.data(), zeroed.size()); in VpnorRoot()
|
| /openbmc/hiomapd/vpnor/test/ |
| H A D | tmpd.hpp | 53 std::vector<char> zeroed(part.data.actual, 0); in VpnorRoot() local 56 .write(zeroed.data(), zeroed.size()); in VpnorRoot()
|
| /openbmc/qemu/hw/nvme/ |
| H A D | dif.c | 357 bool zeroed; in nvme_dif_mangle_mdata() local 382 zeroed = !!(ret & BDRV_BLOCK_ZERO); in nvme_dif_mangle_mdata() 384 trace_pci_nvme_block_status(offset, bytes, pnum, ret, zeroed); in nvme_dif_mangle_mdata() 386 if (zeroed) { in nvme_dif_mangle_mdata()
|
| H A D | trace-events | 41 …64_t bytes, int64_t pnum, int ret, bool zeroed) "offset %"PRId64" bytes %"PRId64" pnum %"PRId64" r…
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | blkverify.rst | 49 And test.img is corrupt, its first sector is zeroed when it shouldn't be::
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 237.out | 37 …dk"}, "hwversion": "4", "size": 67108864, "subformat": "monolithicSparse", "zeroed-grain": false}}} 64 … "TEST_DIR/PID-t.vmdk"}, "size": 33554432, "subformat": "monolithicSparse", "zeroed-grain": true}}}
|
| H A D | 244.out | 144 --- Using a non-zeroed data file ---
|
| H A D | 024.out | 190 Check the last cluster is zeroed in overlay before the rebase
|
| H A D | 059.out | 23 qemu-img: TEST_DIR/t.IMGFMT: Flat image can't enable zeroed grain
|
| /openbmc/qemu/docs/interop/ |
| H A D | qed_spec.rst | 148 which should also be zeroed. 165 Zero data clusters are a space-efficient way of storing zeroed regions of the image.
|
| H A D | qcow2.rst | 244 zeroed, so that if some existing (or future) additional field will fall into
|
| /openbmc/u-boot/ |
| H A D | Kconfig | 191 will return the pointer to the zeroed memory. But this 199 should be replaced by calloc - if one expects zeroed memory.
|
| /openbmc/u-boot/doc/ |
| H A D | README.gpt | 95 16 4 B CRC32 of header (0 to header size), with this field zeroed
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | README.txt | 432 and zeroed before the driver's ofdata_to_platdata() method is called. The 662 is allocated for the device and zeroed. It will be accessible as 671 zeroed. It will be accessible as dev->platdata. 674 then this space is allocated and zeroed also. It is allocated for and
|
| H A D | of-plat.txt | 272 the platform data is allocated, and starts zeroed. In this case the
|
| H A D | spi-howto.txt | 307 after the remove method is called. It will be zeroed when the probe
|
| /openbmc/qemu/tcg/s390x/ |
| H A D | tcg-target.c.inc | 1840 /* swapped unsigned halfword load with upper bits zeroed */ 1858 /* swapped unsigned int load with upper bits zeroed */
|
| /openbmc/qemu/target/ppc/translate/ |
| H A D | vmx-impl.c.inc | 1821 * real hardware would do a partial insert, e.g. if VRT is zeroed and
|
| /openbmc/openbmc/meta-raspberrypi/recipes-multimedia/rpidistro-ffmpeg/files/ |
| H A D | 0001-ffmpeg-5.1.4-rpi_24.patch | 1241 + * @reserved: padding field. Should be zeroed by applications. 1330 + * @reserved: padding field. Should be zeroed by applications. 1377 + * @reserved: padding field. Should be zeroed by applications. 1476 + * @reserved0: padding field. Should be zeroed by applications. 1487 + * @reserved1: padding field. Should be zeroed by applications. 1557 + * @reserved: padding field. Should be zeroed by applications.
|