| /linux/include/linux/ |
| H A D | tracefs.h | 28 * @name: The name of the file that is to be created
30 * @data: data to pass to the created file ops
31 * @fops: the file operations of the created file
33 * The evetnfs files are dynamically created. The struct eventfs_entry array
43 * created.
45 * If a file is to be created, then @mode should be populated with the file
46 * mode (permissions) for which the file is created for. This would be
47 * used to set the created inode i_mode field.
68 * struct eventfs_entry - dynamically created eventfs file call back handler
70 * @callback: The callback to get the fops of the file when it is created
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | overview.rst | 29 * Soft-Reserved IO Resource created for CFMWS entry
33 * Nodes created from ACPI CEDT CFMWS and SRAT Proximity domains (PXM)
37 * A default memory_tier is created with all nodes.
53 * root, port, and memdev devices created
58 * root, switch, and endpoint decoders created
62 * memory_region and endpoint devices created
74 * dax_region created
76 * DAX device created via DAX driver
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/steering/hws/ |
| H A D | mlx5hws.h | 126 /* Define whether the created matcher supports resizing into a bigger matcher */
331 * @ctx: The context in which the new template will be created.
423 * Both matchers must be in the same table type, must be created with the
462 * @matcher: The matcher in which the new rule will be created.
528 * @ctx: The context in which the new action will be created.
541 * @ctx: The context in which the new action will be created.
553 * @ctx: The context in which the new action will be created.
567 * @ctx: The context in which the new action will be created.
580 * @ctx: The context in which the new action will be created.
600 * @ctx: The context in which the new action will be created.
[all …]
|
| /linux/include/kunit/ |
| H A D | device.h | 24 * @name: The name to give the created driver.
36 * @name: The name to give the created device.
52 * @name: The name to give the created device.
69 * @test: The test context object which created the device
72 * Unregisters and destroys a struct device which was created with
73 * kunit_device_register or kunit_device_register_with_driver. If KUnit created
|
| /linux/Documentation/userspace-api/ |
| H A D | iommufd.rst | 24 small letter (iommufd) refers to the file descriptors created via /dev/iommu for
61 feature.) As such, it must be created with a given nesting parent stage-2
69 to those events. A FAULT object must be created first to get a fault_id that
87 must be created given a nesting parent HWPT_PAGING object, and then it would
97 vIOMMU objects created for individual slices of different physical IOMMUs.
123 vIOMMU object must be created first to get its viommu_id, which could be then
198 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can
203 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI
210 3. IOMMUFD_OBJ_HWPT_PAGING can be created in two ways:
212 * IOMMUFD_OBJ_HWPT_PAGING is automatically created when an external driver
[all …]
|
| /linux/Documentation/ABI/testing/ |
| 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",
|
| 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.
|
| /linux/include/sound/ |
| H A D | seq_virmidi.h | 16 * This instance is created at each time the midi device file is
46 int client; /* created/attached client */
47 int port; /* created/attached port */
56 * attached sequencer port. sequencer port is not created
61 * sequencer port is created in virmidi.
|
| /linux/drivers/extcon/ |
| H A D | devres.c | 54 * @dev: the device owning the extcon device being created
91 * @dev: the device owning the extcon device being created
106 * @dev: the device owning the extcon device being created
142 * @dev: the device owning the extcon device being created
157 * @dev: the device owning the extcon device being created
201 * @dev: the device owning the extcon device being created
218 * @dev: the device owning the extcon device being created
256 * @dev: the device owning the extcon device being created
|
| /linux/Documentation/filesystems/ |
| H A D | configfs.rst | 21 With sysfs, an object is created in kernel (for example, when a device
25 write(2). The important point is that the object is created and
29 A configfs config_item is created via an explicit userspace operation:
54 An item is created via mkdir(2). The item's attributes will also
98 A fakenbd connection can be created with mkdir(2). The name is
127 Items are created and destroyed inside a config_group. A group is a
129 Items are created by mkdir(2) and removed by rmdir(2), but configfs
166 Whether statically defined in a source file or created by a parent
263 A config_item cannot live in a vacuum. The only way one can be created
356 The group is where child config_items are created. For a subsystem,
[all …]
|
| H 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.
224 Symbolic links can be created with debugfs_create_symlink().
227 there is no automatic cleanup of any directories created in debugfs. If a
|
| /linux/drivers/greybus/ |
| H A D | greybus_trace.h | 127 * Occurs after a new operation is created for an outgoing request
128 * has been successfully created.
133 * Occurs after a new core operation has been created.
138 * Occurs after a new operation has been created for an incoming
139 * request has been successfully created and initialized.
199 * Occurs after a new connection is successfully created.
268 * Occurs after a new bundle is successfully created.
332 * Occurs after a new interface is successfully created.
405 * Occurs after a new module is successfully created, before
416 * Occurs after a module is successfully created, before registering
[all …]
|
| /linux/drivers/hv/ |
| H A D | hv_debugfs.c | 67 pr_debug("debugfs_hyperv: file %s not created\n", buffer); in hv_debug_delay_files()
75 pr_debug("debugfs_hyperv: file %s not created\n", message); in hv_debug_delay_files()
94 pr_debug("debugfs_hyperv: file %s not created\n", status); in hv_debug_set_test_state()
119 pr_debug("debugfs_hyperv: hyperv/%s/ not created\n", in hv_debug_add_dev_dir()
128 pr_debug("debugfs_hyperv: hyperv/%s/%s/ not created\n", in hv_debug_add_dev_dir()
174 pr_debug("debugfs_hyperv: hyperv/ not created\n"); in hv_debug_init()
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | task_local_data.h | 35 * TLD_DYN_DATA_SIZE - The maximum size of memory allocated for TLDs created dynamically
38 * A TLD can be defined statically using TLD_DEFINE_KEY() or created on the fly using
39 * tld_create_key(). As the total size of TLDs created with tld_create_key() cannot be
44 * will be allocated for TLDs created with it.
287 * The total size of TLDs created using TLD_DEFINE_KEY() cannot exceed a page. Just
309 * Use tld_create_key() only when a TLD needs to be created dynamically (e.g., @name is
310 * not known statically or a TLD needs to be created conditionally)
313 * created dynamically with tld_create_key(). Since only a user page is pinned to the
314 * kernel, when TLDs created with TLD_DEFINE_KEY() uses more than TLD_PAGE_SIZE -
341 * @key: A key object created by TLD_DEFINE_KEY() or tld_create_key().
|
| /linux/include/uapi/linux/ |
| H A D | amt.h | 29 * AMT interface is created as Gateway mode, this attribute is used
31 * AMT interface is created as Relay mode, this attribute is used
36 * AMT interface is created as Gateway mode, this attribute is used
38 * AMT interface is created as Relay mode, this attribute is not used.
|
| /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()
248 bool created; in clsact_init() local
257 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init()
262 if (created) in clsact_init()
276 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init()
281 if (created) in clsact_init()
|
| /linux/Documentation/usb/ |
| H 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
93 Further custom string descriptors can be created as directories within the
107 directories must be created::
120 Each configuration also needs its strings, so a subdirectory must be created
137 directory must be created::
158 At this moment a number of gadgets is created, each of which has a number of
364 a number of its default sub-groups created automatically.
|
| /linux/Documentation/driver-api/ |
| H A D | vfio-mediated-device.rst | 93 * @probe: called when new device created
127 used to trigger the creation of a mdev_device. The created mdev_device will be
134 Which will unbind and destroy all the created mdevs and remove the sysfs files.
192 The [<type-id>] name is created by adding the device driver string as a prefix
200 This attribute shows which device API is being created, for example,
206 created.
211 created.
246 Mediated devices can be created and assigned at runtime. The procedure to hot
|
| /linux/tools/testing/selftests/net/ |
| H A D | reuseport_dualstack.c | 163 fprintf(stderr, "---- UDP IPv4 created before IPv6 ----\n"); in main()
170 fprintf(stderr, "---- UDP IPv6 created before IPv4 ----\n"); in main()
180 fprintf(stderr, "---- UDP IPv4 created before IPv6 (large) ----\n"); in main()
187 fprintf(stderr, "---- UDP IPv6 created before IPv4 (large) ----\n"); in main()
194 fprintf(stderr, "---- TCP IPv4 created before IPv6 ----\n"); in main()
201 fprintf(stderr, "---- TCP IPv6 created before IPv4 ----\n"); in main()
|
| /linux/Documentation/nvme/ |
| H A D | nvme-pci-endpoint-target.rst | 17 regular M.2 SSD. The target controller is created in the same manner as when
182 be setup and bound to the subsystem and port created.
196 memory backing). The block device created will be /dev/nullb0 by default::
212 example, the port is created with a maximum of 4 I/O queue pairs::
241 device can now be created and enabled. The NVMe PCI endpoint target driver
242 should already be loaded (that is done automatically when the port is created)::
272 created::
285 target device and endpoint device are created and connected.
289 null_blk: disk nullb0 created
293 …nvmet: Created nvm controller 1 for subsystem nvmepf.0.nqn for NQN nqn.2014-08.org.nvmexpress:uuid…
|
| /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
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zoned_loop.rst | 24 number of conventional zones can be created. The storage for each zone of the
33 zone size. With this, the maximum capacity of a zloop zoned block device created
124 the zoned device will not be created.
139 For the device created (/dev/zloop0), the zone backing files are all created
156 The zoned device created (/dev/zloop0) can then be used normally::
179 the device was first created. To fully delete a zoned device, its backing files
|
| /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.
|
| /linux/include/linux/rpmsg/ |
| H A D | ns.h | 15 * @flags: indicates whether service is created or destroyed
19 * rpmsg channel (i.e device) is created/destroyed. In turn, the ->probe()
32 * @RPMSG_NS_CREATE: a new remote service was just created
|