Searched full:attach (Results 1 – 25 of 149) sorted by relevance
123456
| /Documentation/bpf/ |
| D | map_cgroup_storage.rst | 10 attach to cgroups; the programs are made available by the same Kconfig. The
34 ``attach_type`` is the program's attach type.
37 When this key type is used, then all attach types of the particular cgroup and
39 ``struct bpf_cgroup_storage_key``, then programs of different attach types
133 multiple attach types, and each attach creates a fresh zeroed storage. The
145 does not already contain an entry for the cgroup and attach type pair, or else
146 the old storage is reused for the new attachment. If the map is attach type
147 shared, then attach type is simply ignored during comparison. Storage is freed
158 In all versions, userspace may use the attach parameters of cgroup and
159 attach type pair in ``struct bpf_cgroup_storage_key`` as the key to the BPF map
[all …]
|
| D | prog_cgroup_sysctl.rst | 13 1. Attach type
16 ``BPF_CGROUP_SYSCTL`` attach type has to be used to attach
|
| D | prog_sk_lookup.rst | 14 Hooks for a common attach point (``BPF_SK_LOOKUP``) exist for both TCP and UDP.
37 ``bpf(BPF_LINK_CREATE, ...)`` syscall using the ``BPF_SK_LOOKUP`` attach type and a
|
| /Documentation/admin-guide/LSM/ |
| D | Yama.rst | 18 attach to other running processes (e.g. Firefox, SSH sessions, GPG agent,
47 may attach.
67 2 - admin-only attach:
71 3 - no attach:
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 44 int (*attach)(struct acpi_device *dev, const struct acpi_device_id *id);
50 maintained by the ACPI core and the .attach() and .detach() callbacks are
57 available scan handlers. If a matching scan handler is found, its .attach()
65 If the .attach() callback returns 0, it means that the device node is not
|
| /Documentation/devicetree/bindings/usb/ |
| D | qcom,pmic-typec.yaml | 45 - description: Type-C CC attach notification, VBUS error, tCCDebounce done
50 - description: Type-C Attach/detach notification
70 - const: attach-detach
165 "attach-detach",
|
| D | richtek,rt1719.yaml | 14 USB Type-C and PD standards. It does the USB Type-C detection including attach
|
| /Documentation/iio/ |
| D | iio_dmabuf_api.rst | 15 can attach DMABUF objects (externally created) to an IIO buffer, and
39 Attach the DMABUF object, identified by its file descriptor, to the
|
| /Documentation/trace/rv/ |
| D | da_monitor_instrumentation.rst | 123 They should be used to *attach* and *detach* the instrumentation to the running
125 *attach* and *detach* its monitor to the system.
132 But no change was required because: by default, these functions *attach* and
|
| /Documentation/i2c/ |
| D | old-module-parameters.rst | 12 control how the driver would probe I2C buses and attach to devices. These
14 address), ``force`` (to forcibly attach the driver to a given device) and
|
| D | i2c-address-translators.rst | 86 calling i2c_atr_new() passing attach/detach callbacks
87 2. When the attach callback is called pick an appropriate alias,
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 204 - in fork and exit, to attach and detach a task from its css_set.
323 6) Attach that task to the new cgroup by writing its PID to the
423 Now attach your shell to this cgroup::
447 Note that it is PID, not PIDs. You can only attach ONE task at a time.
448 If you have several tasks to attach, you have to do it one after another::
455 You can attach the current shell task by echoing 0::
598 subsystem returns an error, this will abort the attach operation.
613 attach() or cancel_attach() will be called in future.
632 Called when a task attach operation has failed after can_attach() has succeeded.
638 ``void attach(struct cgroup *cgrp, struct cgroup_taskset *tset)``
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | vfio.rst | 65 KVM_DEV_VFIO_PVIOMMU_ATTACH: Create and attach a pvIOMMU instance to the
87 the pviommufd returned from the attach operation:
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 17 variables may attach to the same parent object, but their numeric
132 /* Attach a corresponding shadow variable, then initialize it */
169 In these cases, the klp_shadow_get_or_alloc() call can be used to attach
|
| /Documentation/devicetree/bindings/ptp/ |
| D | timestamper.txt | 5 can simply attach their interface directly to the PHY instance), stand
|
| /Documentation/admin-guide/ |
| D | bcache.rst | 55 have to manually attach::
71 device, it'll be running in passthrough mode until you attach it to a cache.
106 echo <CSET-UUID> > /sys/block/bcache0/bcache/attach
173 host:/sys/block/md5/bcache# echo 0226553a-37cf-41d5-b3ce-8b1e944543a8 > attach
175 [ 1933.478179] bcache: __cached_dev_store() Can't attach 0226553a-37cf-41d5-b3ce-8b1e944543a8
218 After you boot back with bcache enabled, you recreate the cache and attach it::
237 attach new cache::
239 host:/sys/block/md5/bcache# echo 5bc072a8-ab17-446d-9744-e247949913c1 > attach
409 attach
|
| /Documentation/usb/ |
| D | functionfs.rst | 79 userspace can attach DMABUF objects (externally created) to an endpoint,
90 Attach the DMABUF object, identified by its file descriptor, to the
|
| /Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 13 constrains the amount of extended attributes one can attach to an inode.
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 129 Before executing OF unittest, it is required to attach the test data to
142 attach_node_and_children() uses of_attach_node() to attach the nodes into the
158 required to attach the root('/') node. All other nodes are attached by calling
|
| /Documentation/sound/designs/ |
| D | jack-controls.rst | 27 and attach it to the jack, at jack creation stage. We can also add a
|
| /Documentation/fb/ |
| D | fbcon.rst | 177 Before going on to how to attach, detach and unload the framebuffer console, an
210 echo 1 > /sys/class/vtconsole/vtcon1/bind - attach framebuffer console to
277 c. Attach fbcon::
294 c. Attach fbcon::
|
| /Documentation/bpf/libbpf/ |
| D | program_types.rst | 8 The table below lists the program types, their attach types where relevant and the ELF section
15 When ``extras`` are specified, they provide details of how to auto-attach the BPF program. The
22 | Program Type | Attach Type | ELF Section …
216 .. [#fentry] The ``fentry`` attach format is ``fentry[.s]/<function>``.
217 .. [#kprobe] The ``kprobe`` attach format is ``kprobe/<function>[+<offset>]``. Valid
220 .. [#ksyscall] The ``ksyscall`` attach format is ``ksyscall/<syscall>``.
221 .. [#uprobe] The ``uprobe`` attach format is ``uprobe[.s]/<path>:<function>[+<offset>]``.
222 .. [#usdt] The ``usdt`` attach format is ``usdt/<path>:<provider>:<name>``.
223 .. [#kpmulti] The ``kprobe.multi`` attach format is ``kprobe.multi/<pattern>`` where ``pattern``
227 .. [#rawtp] The ``raw_tp`` attach format is ``raw_tracepoint[.w]/<tracepoint>``.
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-ocores.rst | 25 There is also a possibility to attach a list of i2c_board_info which
|
| /Documentation/netlabel/ |
| D | introduction.rst | 12 NetLabel is a mechanism which can be used by kernel security modules to attach
|
| /Documentation/trace/coresight/ |
| D | coresight-ect.rst | 30 The CTI driver enables the programming of the CTI to attach triggers to
133 This provides an easy way to attach triggers to channels, without needing
164 * ``trigin_attach, trigout_attach``: Attach a channel to a trigger signal.
|
123456