Home
last modified time | relevance | path

Searched refs:created (Results 1 – 25 of 597) sorted by relevance

12345678910>>...24

/Linux-v4.19/Documentation/PCI/endpoint/
Dpci-endpoint-cfs.txt30 entries corresponding to EPF driver will be created by the EPF core.
45 (These entries are created by the framework when any new <EPF Device> is
46 created)
64 entries corresponding to EPC device will be created by the EPC core.
77 <EPF Device>. These symbolic links should be created by the user to
83 all the EPF devices are created and linked with the EPC device.
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-bus-vfio-mdev9 Each supported type is a directory whose name is created
40 devices sysfs entries which are created of this <type-id>.
47 devices of type <type-id> that can be created. This is a
52 the number of available instances could be created before
68 mediated device that will get created of type <type-id>.
80 mediated device that will get created of type <type-id>.
101 directory of which this mediated device is created.
Dconfigfs-rdma_cm12 for this HCA has to be created:
28 will be created with this TOS as default.
/Linux-v4.19/arch/x86/kvm/
Dmmutrace.h152 TP_PROTO(struct kvm_mmu_page *sp, bool created),
153 TP_ARGS(sp, created),
157 __field(bool, created)
162 __entry->created = created;
166 __entry->created ? "new" : "existing")
/Linux-v4.19/Documentation/filesystems/
Defivarfs.txt4 The efivarfs filesystem was created to address the shortcomings of
11 Variables can be created, deleted and modified with the efivarfs
20 files that are not well-known standardized variables are created
Dexofs.txt64 performed and a clean file system will be created in the specified pid,
68 If pid already exists, it will be deleted and a new one will be created in
99 /dev/osdX: X is a decimal number. /dev/osdX was created after a successful
126 in-memory superblock structure at mount time. This object is created before
146 created in memory (read from disk or created). The credential works for all
160 - create/delete: delete should wait until the object is created
168 should wait until the object is created on the OSD.
171 created on the OSD.
173 object is created on the OSD.
Ddebugfs.txt32 created in the debugfs root. On success, the return value is a struct
51 the return value will be a dentry pointer to the created file, NULL for
68 created with any of:
138 any code which does so in the mainline. Note that all files created with
176 the number of elements in the array. Note: Once array is created its
205 Symbolic links can be created with debugfs_create_symlink().
208 there is no automatic cleanup of any directories created in debugfs. If a
220 pointer for every debugfs file they created so that all files could be
Dhpfs.txt62 well. If you create 'a. ...', the file 'a' will be created, but you can still
74 attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only
76 options are created. Once created, the extended attributes are never deleted,
83 special 4-byte extended attribute "DEV" will be created containing the device
106 file has a pointer to codepage its name is in. However OS/2 was created in
109 Once I booted English OS/2 working in cp 850 and I created a file on my 852
114 really what IBM developers wanted? But problems continued. When I created in
178 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
183 probably because of directories created with old version of this driver.
186 whole created by this driver, it is BUG - let me know about it.
[all …]
Dsharedsubtree.txt366 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is
368 are created and mounted at the dentry 'b' on all mounts where 'B'
370 created. This propagation tree is identical to the propagation tree of
375 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is
377 are created and mounted at the dentry 'b' on all mounts where 'B'
383 mount 'C' which is clone of 'A', is created. Its root dentry is 'a' .
385 'C3' ... are created and mounted at the dentry 'b' on all mounts where
387 'C','C1',.. 'Cn' is created. This propagation tree is identical to the
396 unbindable) mount. A new mount 'C' which is clone of 'A', is created.
400 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is
[all …]
/Linux-v4.19/Documentation/media/uapi/dvb/
Dnet-add-if.rst37 ULE) and the interface number for the new interface to be created. When
39 created.
42 filled with the number of the created interface.
Dnet-get-if.rst12 NET_GET_IF - Read the configuration data of an interface created via - :ref:`NET_ADD_IF <net>`.
39 created yet with :ref:`NET_ADD_IF <net>`, it will return -1 and fill
/Linux-v4.19/net/ceph/
Dcrypto.c79 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-v4.19/Documentation/leds/
Duleds.txt11 When the driver is loaded, a character device is created at /dev/uleds. To
21 A new LED class device will be created with the name given. The name can be
33 Multiple LED class devices are created by opening additional file handles to
/Linux-v4.19/Documentation/driver-model/
Dbinding.txt62 A symlink is created in the bus's 'devices' directory that points to
65 A symlink is created in the driver's 'devices' directory that points
68 A directory for the device is created in the class's directory. A
69 symlink is created in that directory that points to the device's
72 A symlink can be created (though this isn't done yet) in the device's
74 top-level directory. One can also be created to point to its driver's
/Linux-v4.19/Documentation/sysctl/
Duser.txt20 the user in the user namespace who created the object and
24 who created user namespaces the creation of the object happens
28 This recursive counting of created objects ensures that creating a
/Linux-v4.19/Documentation/security/tpm/
Dtpm_vtpm_proxy.rst36 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-v4.19/drivers/staging/iio/Documentation/
Dtrigger.txt18 triggers to keep track of what they have created.
31 consumer interface automatically created.
/Linux-v4.19/Documentation/virtual/kvm/devices/
Dvfio.txt7 Only one VFIO instance may be created per VM. The created device
/Linux-v4.19/drivers/infiniband/ulp/ipoib/
Dipoib_fs.c102 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-v4.19/Documentation/devicetree/
Doverlay-notes.txt15 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.
94 previously created via the call to of_overlay_fdt_apply(). Removal of an
/Linux-v4.19/Documentation/usb/
Dgadget_configfs.txt62 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
348 a number of its default sub-groups created automatically.
/Linux-v4.19/Documentation/devicetree/bindings/clock/st/
Dst,quadfs.txt27 an empty string then no clock will be created for the
29 4 strings are provided then no clocks will be created
/Linux-v4.19/drivers/mtd/ubi/
Dattach.c118 bool *created) in find_or_add_av() argument
129 *created = false; in find_or_add_av()
159 *created = true; in find_or_add_av()
175 int vol_id, bool *created) in ubi_find_or_add_av() argument
177 return find_or_add_av(ai, vol_id, AV_FIND_OR_ADD, created); in ubi_find_or_add_av()
414 bool created; in add_volume() local
418 av = ubi_find_or_add_av(ai, vol_id, &created); in add_volume()
419 if (IS_ERR(av) || !created) in add_volume()
732 bool created; in ubi_add_av() local
734 return find_or_add_av(ai, vol_id, AV_ADD, &created); in ubi_add_av()
[all …]
/Linux-v4.19/Documentation/
Dvfio-mediated-device.txt102 * @probe: called when new device created
230 The [<type-id>] name is created by adding the device driver string as a prefix
241 This attribute should show which device API is being created, for example,
247 created.
252 created.
287 Mediated devices can be created and assigned at runtime. The procedure to hot
349 2. Create a mediated device by using the dummy device that you created in the
404 8. Destroy the mediated device that you created::
/Linux-v4.19/Documentation/filesystems/configfs/
Dconfigfs.txt19 With sysfs, an object is created in kernel (for example, when a device
23 write(2). The important point is that the object is created and
27 A configfs config_item is created via an explicit userspace operation:
51 An item is created via mkdir(2). The item's attributes will also
94 A fakenbd connection can be created with mkdir(2). The name is
122 Items are created and destroyed inside a config_group. A group is a
124 Items are created by mkdir(2) and removed by rmdir(2), but configfs
158 Whether statically defined in a source file or created by a parent
245 A config_item cannot live in a vacuum. The only way one can be created
336 The group is where child config_items are created. For a subsystem,
[all …]

12345678910>>...24