/openbmc/qemu/tests/qemu-iotests/ |
H A D | 146 | 140 echo === Read created image, default opts ==== 148 echo === Read created image, force_size_calc=chs ==== 156 echo === Read created image, force_size_calc=current_size ==== 170 echo === Read created image, default opts ==== 178 echo === Read created image, force_size_calc=chs ==== 186 echo === Read created image, force_size_calc=current_size ====
|
H A D | 157.out | 1 QA output created by 157 4 === Setting WCE with qdev and with manually created BB ===
|
/openbmc/sdbusplus/include/sdbusplus/server/ |
H A D | README.md | 5 **What is _transaction id_** - A unique identifier created by hashing the bus 11 created, and whenever the id is requested and has not been initialized yet. 19 - When a journal entry is created, the _transaction id_ is added as metadata. 20 Therefore all journal entries created within a message have the same 23 - When an error/event log is created, the _transaction id_ of that message will
|
/openbmc/linux/net/sched/ |
H A D | sch_ingress.c | 83 bool created; in ingress_init() local 91 entry = tcx_entry_fetch_or_create(dev, true, &created); in ingress_init() 96 if (created) in ingress_init() 247 bool created; in clsact_init() local 256 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init() 261 if (created) in clsact_init() 275 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init() 280 if (created) in clsact_init()
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Ipmi/ |
H A D | SESSION_README.md | 5 IPMI RMCP+ sessions are created and maintained by phosphor-ipmi-net daemon, 15 - Channel - Session created channel. 20 - UserID - Session created by given user id.
|
/openbmc/phosphor-fan-presence/docs/monitor/ |
H A D | num_nonfunc_rotors_before_error.md | 6 deemed nonfunctional for an error event log to be created. When the number of 8 created against those nonfunctional fan rotors. This attribute is optional and 9 defaults to 1, meaning an error event log should be created when any one of the
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-vfio-mdev | 9 Each supported type is a directory whose name is created 41 devices sysfs entries which are created of this <type-id>. 48 devices of type <type-id> that can be created. This is a 53 the number of available instances could be created before 69 mediated device that will get created of type <type-id>. 81 mediated device that will get created of type <type-id>. 102 directory of which this mediated device is created.
|
H A D | sysfs-class-vduse | 15 This directory entry is created for the control device 23 This directory entry is created when a VDUSE device is 24 created via the control device.
|
H A D | sysfs-bus-event_source-devices-hv_gpci | 92 * This sysfs file will be created only for power10 and above platforms. 96 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS", 124 * This sysfs file will be created only for power10 and above platforms. 128 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS", 156 * This sysfs file will be created only for power10 and above platforms. 160 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS", 188 * This sysfs file will be created only for power10 and above platforms. 192 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS", 220 * This sysfs file will be created only for power10 and above platforms. 224 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
|
/openbmc/linux/Documentation/PCI/endpoint/ |
H A D | pci-endpoint-cfs.rst | 39 entries corresponding to EPF driver will be created by the EPF core. 56 (These entries are created by the framework when any new <EPF Device> is 57 created) 86 be created by the user to represent the virtual functions that are bound to 95 entries corresponding to EPC device will be created by the EPC core. 109 <EPF Device>. These symbolic links should be created by the user to 116 all the EPF devices are created and linked with the EPC device.
|
/openbmc/phosphor-fan-presence/docs/sensor-monitor/ |
H A D | README.md | 14 time. Event logs will also be created. 28 When the alarm properties are asserted, event logs are created. When they are 29 deasserted, informational event logs are created.
|
/openbmc/openbmc/poky/meta/recipes-core/initscripts/initscripts-1.0/ |
H A D | volatiles | 2 # during startup and be created if missing. 21 # Thus, if a link is in the place to be verified, the object will be created 24 # a link will be created at /var/test pointing to /tmp/testfile and due to this 25 # link the file defined as /var/test will actually be created as /tmp/testfile.
|
/openbmc/openbmc/poky/meta/lib/bblayers/templates/ |
H A D | example.bb | 2 DESCRIPTION = "Recipe created by bitbake-layers" 8 bb.plain("* Example recipe created by bitbake-layers *");
|
/openbmc/linux/Documentation/userspace-api/media/dvb/ |
H A D | net-add-if.rst | 36 ULE) and the interface number for the new interface to be created. When 38 created. 41 filled with the number of the created interface.
|
/openbmc/openbmc-test-automation/redfish/account_service/ |
H A D | test_user_account.robot | 237 # Delete created users. 552 # username The username to be created. 577 # Verify login with created user. 582 # Validate Role ID of created user. 593 # username The username to be created. 633 # username The username to be created. 666 # username The username to be created. 684 # Delete newly created user. 702 # Delete newly created user. 730 # Login with created user. [all …]
|
/openbmc/linux/net/ceph/ |
H A D | crypto.c | 79 if (*p + sizeof(u16) + sizeof(key->created) + in ceph_crypto_key_encode() 83 ceph_encode_copy(p, &key->created, sizeof(key->created)); in ceph_crypto_key_encode() 93 ceph_decode_need(p, end, 2*sizeof(u16) + sizeof(key->created), bad); in ceph_crypto_key_decode() 95 ceph_decode_copy(p, &key->created, sizeof(key->created)); in ceph_crypto_key_decode()
|
/openbmc/openbmc/poky/bitbake/lib/toaster/orm/management/commands/ |
H A D | lsupdates.py | 136 l, created = Layer.objects.get_or_create(name=index.layerItems[id].name) 141 if created: 171 lv, created = Layer_Version.objects.get_or_create( 182 if created: 230 distro, created = Distro.objects.get_or_create( 245 mo, created = Machine.objects.get_or_create( 264 ro, created = Recipe.objects.get_or_create(
|
/openbmc/linux/Documentation/leds/ |
H A D | uleds.rst | 12 When the driver is loaded, a character device is created at /dev/uleds. To 22 A new LED class device will be created with the name given. The name can be 34 Multiple LED class devices are created by opening additional file handles to
|
/openbmc/phosphor-dbus-monitor/src/test/yaml/interfaceaddtest/ |
H A D | one.yaml | 1 # Validate number of watches created for the object path 3 # Expecting one watch created for the object path
|
/openbmc/qemu/tests/qemu-iotests/sample_images/ |
H A D | README | 5 For instance, a VHDX image in this directory would be an image created not by 6 QEMU itself, but rather created by Hyper-V.
|
/openbmc/linux/Documentation/driver-api/driver-model/ |
H A D | binding.rst | 63 A symlink is created in the bus's 'devices' directory that points to 66 A symlink is created in the driver's 'devices' directory that points 69 A directory for the device is created in the class's directory. A 70 symlink is created in that directory that points to the device's 73 A symlink can be created (though this isn't done yet) in the device's 75 top-level directory. One can also be created to point to its driver's
|
/openbmc/linux/kernel/bpf/ |
H A D | tcx.c | 12 bool created, ingress = attr->attach_type == BPF_TCX_INGRESS; in tcx_prog_attach() local 34 entry = tcx_entry_fetch_or_create(dev, ingress, &created); in tcx_prog_attach() 49 } else if (created) { in tcx_prog_attach() 145 bool created, ingress = tcx->location == BPF_TCX_INGRESS; in tcx_link_prog_attach() local 151 entry = tcx_entry_fetch_or_create(dev, ingress, &created); in tcx_link_prog_attach() 163 } else if (created) { in tcx_link_prog_attach()
|
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/ |
H A D | Notify.interface.yaml | 3 dump is already created and ready to be offloaded. This interface will 11 used for all communication with the host), and the size of the newly created 42 Sometimes the dump is created in the host based on the request 61 Resource Dump: A dump of host resources, created for various
|
/openbmc/linux/Documentation/filesystems/ |
H A D | efivarfs.rst | 7 The efivarfs filesystem was created to address the shortcomings of 14 Variables can be created, deleted and modified with the efivarfs 23 files that are not well-known standardized variables are created
|
/openbmc/linux/arch/arm/boot/dts/aspeed/ |
H A D | facebook-bmc-flash-layout.dtsi | 34 * Although the master partition can be created by enabling 36 * explicitly created to avoid breaking legacy applications.
|