Home
last modified time | relevance | path

Searched refs:attaching (Results 26 – 50 of 57) sorted by relevance

123

/openbmc/linux/Documentation/networking/device_drivers/hamradio/
H A Dbaycom.rst95 me for WAMPES which allows attaching a kernel network interface directly.
/openbmc/openbmc-tools/ipkdbg/
H A DREADME.md62 Interactive debugging is handled by attaching `gdbserver` on the BMC to the
/openbmc/linux/Documentation/filesystems/
H A Djournalling.rst115 ``transaction->t_private_list`` for attaching entries to a transaction
/openbmc/linux/Documentation/trace/
H A Duser_events.rst92 or perf record -e user_events:[name] when attaching/recording.
/openbmc/linux/Documentation/networking/
H A Dkcm.rst79 Filter (BPF) is used for this. When attaching a TCP socket to a multiplexor a
H A Dfilter.rst395 attaching to a live system. For that purpose, there's a small tool called
/openbmc/linux/drivers/infiniband/ulp/rtrs/
H A DREADME67 by one via attaching RTRS_MSG_CON_REQ messages to the rdma_connect requests.
/openbmc/openbmc/poky/meta/recipes-multimedia/pulseaudio/
H A Dpulseaudio.inc222 # It's primarily useful for attaching an information dump when reporting bugs.
/openbmc/linux/Documentation/bpf/libbpf/
H A Dlibbpf_overview.rst9 heavy lifting of loading, verifying, and attaching BPF programs to various
/openbmc/linux/Documentation/process/
H A D3.Early-stage.rst143 patches, and who, if anybody, is attaching Signed-off-by lines to those
/openbmc/linux/drivers/media/rc/
H A DKconfig25 Allow attaching eBPF programs to a lirc device using the bpf(2)
/openbmc/linux/Documentation/i2c/
H A Dwriting-clients.rst124 Probing and attaching
/openbmc/linux/Documentation/bpf/
H A Dbpf_design_QA.rst295 The kernel function prototypes will change, and BPF programs attaching to
/openbmc/linux/Documentation/input/joydev/
H A Djoystick.rst437 Linux runs on, and usually require a special connector for attaching
/openbmc/linux/Documentation/filesystems/caching/
H A Dnetfs-api.rst256 The *begin* function sets up an operation, attaching the resources required to
/openbmc/linux/Documentation/hid/
H A Dhid-bpf.rst228 Unless ``HID_BPF_FLAG_INSERT_HEAD`` is added to the flags while attaching the
/openbmc/qemu/docs/system/devices/
H A Dcxl.rst58 **Type 3 Memory devices:** These devices act as a means of attaching
/openbmc/linux/Documentation/arch/s390/
H A Dvfio-ap.rst1011 2. A vfio_ap mediated device can be hot unplugged by attaching the qemu monitor
1058 2. A vfio_ap mediated device can be hot plugged by attaching the qemu monitor
/openbmc/linux/Documentation/admin-guide/mm/
H A Dnuma_memory_policy.rst513 be attaching to the shared region. Furthermore, if the cpusets' allowed
/openbmc/linux/Documentation/driver-api/
H A Dvfio.rst330 then the device is fully accessible including attaching it to an
/openbmc/linux/init/
H A DKconfig1063 It should be noted that organisational operations (such as attaching
1149 Allow attaching eBPF programs to a cgroup using the bpf(2)
/openbmc/qemu/docs/interop/
H A Dbitmaps.rst56 attaching the bitmap elsewhere in the storage graph. This is beyond the scope
/openbmc/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst2115 setting the limit to be smaller than pids.current, or attaching enough
2663 No implicit cgroup changes happen with attaching to another cgroup
2664 namespace. It is expected that the someone moves the attaching
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dcpusets.rst673 on task attaching. In this failing case, those tasks will stay
/openbmc/u-boot/doc/driver-model/
H A DREADME.txt597 that the flash device is connetced to. The act of attaching a device to a

123