Home
last modified time | relevance | path

Searched full:themselves (Results 1 – 25 of 894) sorted by relevance

12345678910>>...36

/kernel/linux/linux-4.19/include/xen/interface/
Dxenpmu.h45 * - XENPMU_MODE_SELF: Guests can profile themselves
46 * - XENPMU_MODE_HV: Guests can profile themselves, dom0 profiles
/kernel/linux/linux-5.10/include/xen/interface/
Dxenpmu.h45 * - XENPMU_MODE_SELF: Guests can profile themselves
46 * - XENPMU_MODE_HV: Guests can profile themselves, dom0 profiles
/kernel/linux/linux-4.19/Documentation/trace/
Dstm.rst11 trace sources are usually free to pick for themselves any
56 trace data into its file descriptor. In order to identify themselves
66 need to allocate that many channels to themselves (via the
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-devlink17 supplier devices themselves are still present.
32 when as long as the supplier and consumer devices themselves
/kernel/linux/linux-4.19/drivers/misc/ti-st/
DKconfig14 to register themselves with core and send data, the responses
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-bindings.txt24 Note that pin controllers themselves may also be client devices of themselves.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/arc/
Dpct.txt9 counted, the HW events themselves cannot serve as a trigger for a sample.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arc/
Dpct.txt9 counted, the HW events themselves cannot serve as a trigger for a sample.
/kernel/linux/linux-5.10/drivers/misc/ti-st/
DKconfig15 to register themselves with core and send data, the responses
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/can/
Dcan-transceiver.txt5 modes. Typically these limitations are static and the transceivers themselves
/kernel/linux/linux-5.10/drivers/net/ethernet/chelsio/cxgb3/
Dcxgb3_offload.h57 * Client registration. Users of T3 driver must register themselves.
155 * The tables themselves are allocated dynamically.
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dexception-64e.h14 * critical exceptions which can themselves be interrupted by machine
15 * checks, and since the two later can themselves cause a TLB miss when
/kernel/linux/linux-4.19/drivers/net/ethernet/chelsio/cxgb3/
Dcxgb3_offload.h57 * Client registration. Users of T3 driver must register themselves.
155 * The tables themselves are allocated dynamically.
/kernel/linux/linux-5.10/Documentation/trace/
Dstm.rst13 trace sources are usually free to pick for themselves any
86 need to allocate that many channels to themselves (via the
/kernel/linux/linux-5.10/fs/jffs2/
DLICENCE23 files, these files do not by themselves cause the resulting work to be
/kernel/linux/linux-4.19/fs/jffs2/
DLICENCE23 files, these files do not by themselves cause the resulting work to be
/kernel/linux/linux-5.10/arch/sh/kernel/
Dtime.c26 * Make sure all compiled-in early timers register themselves. in sh_late_time_init()
/kernel/linux/linux-4.19/arch/powerpc/include/asm/
Dexception-64e.h18 * critical exceptions which can themselves be interrupted by machine
19 * checks, and since the two later can themselves cause a TLB miss when
/kernel/linux/linux-4.19/Documentation/parisc/
Ddebugging38 at all. Usually Q bit problems will show themselves in unexplainable
/kernel/linux/linux-4.19/include/uapi/asm-generic/
Dstatfs.h11 * Special cases can override it for themselves -- except for S390x, which
/kernel/linux/linux-5.10/drivers/usb/common/
DKconfig29 attached to them. The ULPI PHY drivers themselves are normal PHY
/kernel/linux/linux-5.10/include/uapi/asm-generic/
Dstatfs.h11 * Special cases can override it for themselves -- except for S390x, which
/kernel/linux/linux-4.19/Documentation/driver-api/
Ddevice_connection.rst21 devices requests a reference to the other. The descriptions themselves can be
/kernel/linux/linux-5.10/tools/perf/Documentation/
Ddb-export.txt33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
/kernel/linux/linux-4.19/drivers/gpu/drm/
Ddrm_simple_kms_helper.c245 * handle connectors themselves (see drm_simple_display_pipe_attach_bridge()).
249 * release the memory for the structure themselves.

12345678910>>...36