| /linux/Documentation/PCI/endpoint/ |
| 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.
|
| /linux/Documentation/ABI/testing/ |
| 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.
|
| A D | sysfs-class-rtrs-server | 6 directory entry with the name of that session is created in here. 12 Description: When new path is created by writing to "add_path" entry on client side, 13 a directory entry named as <source address>@<destination address> is created
|
| A D | configfs-rdma_cm | 12 for this HCA has to be created: 28 will be created with this TOS as default.
|
| /linux/Documentation/networking/devlink/ |
| A D | devlink-port.rst | 115 before a bus specific device for the function is created. However, when 116 SRIOV is enabled, virtual function devices are created on the PCI bus. 129 it is deployed. Subfunction is created and deployed in unit of 1. Unlike 143 A subfunction is created using a devlink port interface. A user adds the 152 A subfunction devlink port is created but it is not active yet. That means the 153 entities are created on devlink side, the e-switch port representor is created, 154 but the subfunction device itself is not created. A user might use e-switch port 164 A subfunction device is created on the :ref:`Documentation/driver-api/auxiliary_bus.rst <auxiliary_… 174 Represents a single devlink port; created/destroyed by the driver. Since leaf 179 Represents a group of rate objects (leafs and/or nodes); created/deleted by
|
| /linux/net/ceph/ |
| 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()
|
| /linux/Documentation/userspace-api/media/dvb/ |
| 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.
|
| A D | net-get-if.rst | 13 NET_GET_IF - Read the configuration data of an interface created via - :ref:`NET_ADD_IF <net>`. 38 created yet with :ref:`NET_ADD_IF <net>`, it will return -1 and fill
|
| /linux/Documentation/driver-api/driver-model/ |
| 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
|
| /linux/Documentation/leds/ |
| 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
|
| /linux/arch/x86/kvm/mmu/ |
| A D | mmutrace.h | 158 TP_PROTO(struct kvm_mmu_page *sp, bool created), 159 TP_ARGS(sp, created), 163 __field(bool, created) 168 __entry->created = created; 172 __entry->created ? "new" : "existing")
|
| /linux/Documentation/filesystems/ |
| 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
|
| A D | debugfs.rst | 39 created in the debugfs root. On success, the return value is a struct 58 the return value will be a dentry pointer to the created file, 76 created with any of:: 154 any code which does so in the mainline. Note that all files created with 198 of its elements. Note: Once array is created its size can not be changed. 226 Symbolic links can be created with debugfs_create_symlink(). 229 there is no automatic cleanup of any directories created in debugfs. If a 242 pointer for every debugfs file they created so that all files could be
|
| A D | hpfs.rst | 71 well. If you create 'a. ...', the file 'a' will be created, but you can still 84 attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only 86 options are created. Once created, the extended attributes are never deleted, 93 special 4-byte extended attribute "DEV" will be created containing the device 118 file has a pointer to codepage its name is in. However OS/2 was created in 121 Once I booted English OS/2 working in cp 850 and I created a file on my 852 126 really what IBM developers wanted? But problems continued. When I created in 193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2 198 probably because of directories created with old version of this driver. 201 whole created by this driver, it is BUG - let me know about it. [all …]
|
| A D | sharedsubtree.rst | 385 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is 387 are created and mounted at the dentry 'b' on all mounts where 'B' 394 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is 396 are created and mounted at the dentry 'b' on all mounts where 'B' 419 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is 424 new mount 'C' which is a clone of 'A' is created. Its root dentry is 502 are created and mounted at dentry 'b' on all mounts that receive 511 are created and mounted at dentry 'b' on all mounts that receive 513 propagation tree is created which is identical to that of 694 the number of mounts created is an exponential function of 'n'. [all …]
|
| /linux/Documentation/driver-api/ |
| A D | vfio-mediated-device.rst | 101 * @probe: called when new device created 151 used to trigger the creation of a mdev_device. The created mdev_device will be 158 Which will unbind and destroy all the created mdevs and remove the sysfs files. 216 The [<type-id>] name is created by adding the device driver string as a prefix 227 This attribute should show which device API is being created, for example, 233 created. 238 created. 273 Mediated devices can be created and assigned at runtime. The procedure to hot 335 2. Create a mediated device by using the dummy device that you created in the 390 8. Destroy the mediated device that you created::
|
| /linux/drivers/infiniband/ulp/ipoib/ |
| A D | ipoib_fs.c | 102 unsigned long created; in ipoib_mcg_seq_show() local 108 ipoib_mcast_iter_read(iter, &mgid, &created, &queuelen, in ipoib_mcg_seq_show() 120 gid_buf, created, queuelen, in ipoib_mcg_seq_show()
|
| /linux/arch/arm/boot/dts/ |
| 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.
|
| A D | facebook-bmc-flash-layout-128.dtsi | 52 * Although the master partition can be created by enabling 54 * explicitly created to avoid breaking legacy applications.
|
| /linux/Documentation/devicetree/ |
| A D | overlay-notes.rst | 18 in an active device should have it created while if the device node is either 81 As a result of the overlay, a new device node (bar) has been created 83 is loaded the device will be created as expected. 115 previously created via the call to of_overlay_fdt_apply(). Removal of an
|
| /linux/Documentation/usb/ |
| A D | gadget_configfs.rst | 62 For each gadget to be created its corresponding directory must be created:: 82 In order to have a place to store them, a strings subdirectory must be created 97 directories must be created: 110 Each configuration also needs its strings, so a subdirectory must be created 127 directory must be created:: 148 At this moment a number of gadgets is created, each of which has a number of 354 a number of its default sub-groups created automatically.
|
| /linux/Documentation/security/tpm/ |
| A D | tpm_vtpm_proxy.rst | 36 as well as the major and minor numbers of the character device that was created. 38 example ``/dev/tpm10`` was created, the number (``dev_num``) 10 is returned. 40 Once the device has been created, the driver will immediately try to talk
|
| /linux/Documentation/admin-guide/sysctl/ |
| A D | user.rst | 25 the user in the user namespace who created the object and 29 who created user namespaces the creation of the object happens 33 This recursive counting of created objects ensures that creating a
|
| /linux/tools/perf/Documentation/ |
| A D | intel-hybrid.txt | 14 The 'cpus' files are created under the directories. For example, 59 two events are created automatically. One is for atom, the other is for 92 are created automatically. 145 As previous, two events are created. 189 besides of software events, following events are created and
|
| /linux/drivers/mtd/ubi/ |
| A D | attach.c | 105 bool *created) in find_or_add_av() argument 116 *created = false; in find_or_add_av() 146 *created = true; in find_or_add_av() 162 int vol_id, bool *created) in ubi_find_or_add_av() argument 401 bool created; in add_volume() local 405 av = ubi_find_or_add_av(ai, vol_id, &created); in add_volume() 406 if (IS_ERR(av) || !created) in add_volume() 719 bool created; in ubi_add_av() local 721 return find_or_add_av(ai, vol_id, AV_ADD, &created); in ubi_add_av() 735 bool created; in ubi_find_av() local [all …]
|