| /openbmc/hiomapd/test/ |
| H A D | flash_erase.c | 38 struct erase_info_user *recorded; variable 72 alloced = realloc(recorded, n_ioctls * sizeof(*recorded)); in ioctl() 75 recorded = alloced; in ioctl() 77 memcpy(&recorded[n_ioctls - 1], provided, sizeof(*provided)); in ioctl() 96 i, recorded[i].start, recorded[i].length); in dump_ioctls() 115 recorded = NULL; in main() 124 assert(recorded[0].start == 0); in main() 125 assert(recorded[0].length == sizeof(data)); in main() 127 free(recorded); in main() 128 recorded = NULL; in main() [all …]
|
| /openbmc/phosphor-mboxd/test/ |
| H A D | erase_flash.c | 36 struct erase_info_user *recorded; variable 70 alloced = realloc(recorded, n_ioctls * sizeof(*recorded)); in ioctl() 73 recorded = alloced; in ioctl() 75 memcpy(&recorded[n_ioctls - 1], provided, sizeof(*provided)); in ioctl() 94 i, recorded[i].start, recorded[i].length); in dump_ioctls() 110 recorded = NULL; in main() 119 assert(recorded[0].start == 0); in main() 120 assert(recorded[0].length == sizeof(data)); in main() 122 free(recorded); in main() 123 recorded = NULL; in main() [all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/postgresql/files/ |
| H A D | 0004-config_info.c-not-expose-build-info.patch | 54 - configdata[i].setting = pstrdup(_("not recorded")); 62 - configdata[i].setting = pstrdup(_("not recorded")); 70 - configdata[i].setting = pstrdup(_("not recorded")); 78 - configdata[i].setting = pstrdup(_("not recorded")); 86 - configdata[i].setting = pstrdup(_("not recorded")); 94 - configdata[i].setting = pstrdup(_("not recorded")); 102 - configdata[i].setting = pstrdup(_("not recorded")); 110 - configdata[i].setting = pstrdup(_("not recorded"));
|
| H A D | 0002-Improve-reproducibility.patch | 10 not recorded 13 not recorded
|
| /openbmc/u-boot/doc/ |
| H A D | bounces | 3 # information recorded in git.
|
| H A D | README.trace | 17 function entry/exit points. These are then recorded in a memory buffer. 326 stack depth goes above this then no tracing information is recorded. 327 The maximum depth reached is recorded and displayed by the 'trace stats' 339 - Trace filter to select which functions are recorded
|
| H A D | README.log | 234 buffer - recorded in a memory buffer
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/liberror/ |
| H A D | liberror-perl_0.17030.bb | 5 either be thrown, for subsequent catch, or can simply be recorded."
|
| /openbmc/qemu/docs/system/ |
| H A D | replay.rst | 66 * Interaction with audio devices and serial ports are recorded and replayed 111 controller. Therefore all disk requests may be recorded and replayed. 180 Audio data is recorded and replay automatically. The command line for recording 189 Serial ports input is recorded and replay automatically. The command lines
|
| /openbmc/u-boot/common/ |
| H A D | Kconfig | 8 bootstage.h. Only a single entry is recorded for each ID. You can 63 number of bootstage records that can be recorded. 70 number of bootstage records that can be recorded. 266 Console output is recorded even when the console is silent. 276 more data will be recorded until some is removed. The buffer is 474 can be displayed on the console, recorded in a memory buffer, or 483 can be displayed on the console, recorded in a memory buffer, or 492 can be displayed on the console, recorded in a memory buffer, or 501 This selects the maximum log level that will be recorded. Any value 521 This selects the maximum log level that will be recorded. Any value [all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/go/go/ |
| H A D | 0010-cmd-go-clear-GOROOT-for-func-ldShared-when-trimpath-.patch | 34 // the output file path is recorded in the .gnu.version_d section.
|
| /openbmc/qemu/qapi/ |
| H A D | replay.json | 39 # in record or replay modes, when the log is recorded or replayed.
|
| /openbmc/qemu/docs/devel/ |
| H A D | tcg.rst | 25 CPU cannot change in it. The state is recorded in the Translation 28 matches the state recorded in the previous TB. The same idea can be applied
|
| H A D | replay.rst | 137 That is why it is completely deterministic and does not have to be recorded. 166 is recorded to the log. In replay phase the queue is matched with
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | README.md | 141 detected via CRC or security verification failure. An event may be recorded 150 has failed. An event may be recorded with additional details.
|
| /openbmc/qemu/hw/arm/ |
| H A D | smmuv3-internal.h | 441 bool recorded; member
|
| /openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
| H A D | tripwire.txt | 31 The Integrity Check mode compares the current file system objects with their properties recorded in…
|
| /openbmc/docs/designs/ |
| H A D | event-logging.md | 67 device and system. When this event occurs, there might be a `LogEntry` recorded 159 1. Search back through the journal for recorded metadata associated with the 368 previously recorded error, for marking as resolved. These strings need to be 371 A `Logging.SearchHint` interface will be created, which will be recorded at the
|
| /openbmc/docs/ |
| H A D | IPMITOOL-cheatsheet.md | 119 event : Event information recorded by the sensor
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | maint-appx.rst | 205 recorded in the series of directories in their compilation order. The
|
| /openbmc/openbmc/poky/meta/recipes-extended/shadow/files/ |
| H A D | login.defs_shadow-sysroot | 21 # Enable display of unknown usernames when login failures are recorded.
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | reference.rst | 536 The ``buildslist`` command lists all builds that Toaster has recorded. 544 identifications, of the builds that Toaster has recorded in the current
|
| /openbmc/qemu/docs/interop/ |
| H A D | bitmaps.rst | 301 begin being recorded. ``+busy`` bitmaps cannot be enabled. 565 destination. These writes will be recorded in the bitmap 790 the backup starts, not when it ends. These writes are recorded in a
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-2.3.rst | 437 If you need the build date recorded in ``/etc/issue*`` or anywhere
|
| /openbmc/u-boot/tools/binman/ |
| H A D | README.entries | 369 place then the offset and size of the microcode is recorded by this entry,
|