Home
last modified time | relevance | path

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

12345678910>>...28

/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-bus-vfio-mdev9 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.
Dsysfs-class-vduse15 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.
Dconfigfs-rdma_cm12 for this HCA has to be created:
28 will be created with this TOS as default.
Dsysfs-class-rtrs-server6 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
/linux-6.1.9/Documentation/PCI/endpoint/
Dpci-endpoint-cfs.rst39 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-6.1.9/Documentation/userspace-api/media/dvb/
Dnet-add-if.rst36 ULE) and the interface number for the new interface to be created. When
38 created.
41 filled with the number of the created interface.
Dnet-get-if.rst13 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-6.1.9/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-6.1.9/Documentation/networking/devlink/
Ddevlink-port.rst115 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-6.1.9/Documentation/leds/
Duleds.rst12 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-6.1.9/Documentation/driver-api/driver-model/
Dbinding.rst63 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-6.1.9/Documentation/filesystems/
Defivarfs.rst7 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
Ddebugfs.rst39 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
/linux-6.1.9/arch/arm/boot/dts/
Dfacebook-bmc-flash-layout.dtsi34 * Although the master partition can be created by enabling
36 * explicitly created to avoid breaking legacy applications.
Dfacebook-bmc-flash-layout-128.dtsi52 * Although the master partition can be created by enabling
54 * explicitly created to avoid breaking legacy applications.
/linux-6.1.9/arch/x86/kvm/mmu/
Dmmutrace.h159 TP_PROTO(struct kvm_mmu_page *sp, bool created),
160 TP_ARGS(sp, created),
164 __field(bool, created)
169 __entry->created = created;
173 __entry->created ? "new" : "existing")
/linux-6.1.9/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-6.1.9/Documentation/driver-api/
Dvfio-mediated-device.rst99 * @probe: called when new device created
133 used to trigger the creation of a mdev_device. The created mdev_device will be
140 Which will unbind and destroy all the created mdevs and remove the sysfs files.
198 The [<type-id>] name is created by adding the device driver string as a prefix
206 This attribute shows which device API is being created, for example,
212 created.
217 created.
252 Mediated devices can be created and assigned at runtime. The procedure to hot
314 2. Create a mediated device by using the dummy device that you created in the
369 8. Destroy the mediated device that you created::
/linux-6.1.9/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-6.1.9/Documentation/admin-guide/sysctl/
Duser.rst25 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-6.1.9/Documentation/usb/
Dgadget_configfs.rst62 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-6.1.9/Documentation/virt/kvm/devices/
Dvfio.rst11 Only one VFIO instance may be created per VM. The created device
/linux-6.1.9/tools/perf/Documentation/
Dintel-hybrid.txt14 The 'cpus' files are created under the directories. For example,
52 two events are created automatically. One is for atom, the other is for
85 are created automatically.
137 As previous, two events are created.
179 besides of software events, following events are created and
/linux-6.1.9/Documentation/devicetree/bindings/arm/
Darm,realview.yaml22 - description: ARM RealView Emulation Baseboard (HBI-0140) was created
28 (HBI-0147) was created as a development board to test ARM TrustZone,
33 (HBI-0159, HBI-0175 and HBI-0176) was created to showcase
/linux-6.1.9/Documentation/devicetree/bindings/clock/st/
Dst,quadfs.txt30 an empty string then no clock will be created for the
32 4 strings are provided then no clocks will be created

12345678910>>...28