| /openbmc/qemu/contrib/plugins/ |
| H A D | hotpages.c | 45 uint64_t writes; member
58 r = (ea->reads + ea->writes) > (eb->reads + eb->writes) ? -1 : 1; in cmp_access_count()
64 r = ea->writes > eb->writes ? -1 : 1; in cmp_access_count()
95 rec->cpu_write, rec->writes); in plugin_exit()
141 count->writes++; in vcpu_haddr()
|
| H A D | hwprofile.c | 29 uint64_t writes; member
78 return ea->totals.reads + ea->totals.writes > in sort_cmp()
79 eb->totals.reads + eb->totals.writes ? -1 : 1; in sort_cmp()
97 rec->cpu_write, rec->writes); in fmt_iocount_record()
189 count->writes++; in inc_count()
|
| /openbmc/u-boot/doc/ |
| H A D | I2C_Edge_Conditions | 10 3) The I2C writes the device address.
15 2) The I2C controller writes the device address.
16 3) The I2C controller writes the offset.
|
| H A D | README.ubispl | 106 * FLASH chip to do subpage writes.
108 * If the flash chip supports subpage writes, then the VID
112 * If the flash chip does not support subpage writes then the
|
| /openbmc/qemu/tests/tcg/multiarch/system/ |
| H A D | validate-memory-counts.py | 75 writes = int(parts[2])
79 total_writes += writes
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | image-fleecing.out | 59 --- Confirming writes ---
129 --- Confirming writes ---
201 --- Confirming writes ---
285 --- Confirming writes ---
348 --- Confirming writes ---
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/unixodbc/files/ |
| H A D | CVE-2024-1013.patch | 6 These result in out-of-bounds stack writes on 64-bit architectures
7 (caller has 4 bytes, callee writes 8 bytes), and seem to have gone
|
| /openbmc/u-boot/fs/yaffs2/ |
| H A D | Kconfig | 7 writes are sequential regardless of filesystem activity.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-atomicwrites_1.4.1.bb | 1 SUMMARY = "Powerful Python library for atomic file writes"
|
| /openbmc/openbmc/poky/meta/recipes-graphics/glew/glew/ |
| H A D | 0001-Fix-build-race-in-Makefile.patch | 16 that the other target writes into.
19 fundamentally racy, and simply mkdir in each target which writes into it.
|
| /openbmc/qemu/docs/specs/ |
| H A D | acpi_nvdimm.rst | 92 writes _DSM input data to it, otherwise, it is owned by QEMU which
93 emulates _DSM access and writes the output data to it.
95 ACPI writes _DSM Input Data (based on the offset in the page):
119 QEMU writes Output Data (based on the offset in the page):
128 ACPI writes the address of the memory page allocated by BIOS to this
|
| H A D | fw_cfg.rst | 32 of 1 means the item's data can be overwritten by writes to the data
37 As of QEMU v2.4, writes to the fw_cfg data register are no
41 As of QEMU v2.9, writes are reinstated, but only through the DMA
56 * Read/Write (writes ignored as of QEMU v2.4, but see the DMA interface)
78 value of 0x00, and all writes will be ignored.
190 64-bit addresses can be triggered with one 64-bit write or two 32-bit writes,
225 with the current selector (i.e., the item cannot be resized). Truncated writes
|
| /openbmc/libmctp/docs/bindings/ |
| H A D | vendor-ibm-astlpc.md | 101 - A window of the LPC FW address space, where reads and writes are forwarded to
107 - The BMC will perform writes by writing to the memory backing the LPC window
108 - The host will perform writes by writing to the LPC bus, at predefined
148 writes to the KCS status register but hardware implementations are not required
149 to do so. Comparatively, writes to the data registers must set the corresponding
316 | 1 | The host writes a command value to IDR |
329 | 1 | The BMC writes a command value to ODR |
342 | 1 | The BMC writes the status value to the status register |
343 | 2 | The BMC writes the dummy command to ODR |
364 1. The Tx side writes the packet to its Tx buffer
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-spirit/ |
| H A D | json-spirit_4.08.bb | 2 DESCRIPTION = "JSON Spirit, a C++ library that reads and writes JSON files or streams. \
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/netcat/ |
| H A D | netcat.inc | 3 DESCRIPTION = "A simple Unix utility which reads and writes data across network \
|
| /openbmc/qemu/tests/tcg/plugins/ |
| H A D | mem.c | 54 uint64_t writes; member
111 ri->writes, in plugin_exit()
150 ri->writes++; in update_region_info()
|
| /openbmc/qemu/docs/ |
| H A D | nvdimm.txt | 39 "share=on/off" controls the visibility of guest writes. If
40 "share=on", then guest writes will be applied to the backend
42 "share=on", then above writes will be visible to it as well. If
43 "share=off", then guest writes won't be applied to the backend
55 persistent writes. Linux guest drivers set the device to read-only when this
191 accept persistent writes. In result, for example, the guest Linux
247 will take necessary operations to guarantee the persistence of its own writes
|
| /openbmc/qemu/docs/interop/ |
| H A D | bitmaps.rst | 12 Dirty Bitmaps are in-memory objects that track writes to block devices. They
48 explicitly added in order to begin tracking writes.
54 That is to say: It's likely most useful to track the guest's writes to disk,
72 writes bitmap data to disk upon close. If persistence is not required for a
120 - ``recording``: This bitmap is recording writes.
142 #. ``Disabled``: This bitmap is not recording new writes.
146 #. ``Active``: This bitmap is recording new writes.
195 Creates a new bitmap that tracks writes to the specified node. granularity,
300 "Enables" a bitmap, setting the ``recording`` bit to true, causing writes to
330 writes to begin being ignored. ``+busy`` bitmaps cannot be disabled.
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 138.out | 11 Data may be corrupted, or further writes to the image may corrupt it.
|
| H A D | 236.out | 11 --- Emulating writes ---
150 --- Emulating further writes ---
|
| /openbmc/phosphor-mboxd/vpnor/ |
| H A D | README.md | 16 behaviour around writes from the host. It is likely the scheme will prevent
57 future writes are expected to succeed, but in both cases we define them as
|
| /openbmc/u-boot/drivers/mtd/ |
| H A D | Kconfig | 47 bool "Enable buffered writes to flash"
50 Use buffered writes to flash.
|
| /openbmc/hiomapd/vpnor/ |
| H A D | README.md | 14 behaviour around writes from the host. It is likely the scheme will prevent
53 future writes are expected to succeed, but in both cases we define them as
|
| /openbmc/openbmc/poky/meta/recipes-bsp/grub/files/ |
| H A D | CVE-2024-45774.patch | 8 allowing future OOB writes.
|
| /openbmc/u-boot/board/synopsys/emsdp/ |
| H A D | README | 46 might be unlocked for writes its initial content will be restored
78 need to enable writes into "ROM" by writing 1 to 0xf0001000.
|