Searched full:concept (Results 1 – 25 of 222) sorted by relevance
123456789
/linux-6.14.4/Documentation/ABI/testing/ |
D | configfs-tsm | 82 supports the concept of attestation reports for TVMs running at 102 supports the concept of attestation reports from a service 119 supports the concept of attestation reports from a service 137 supports the concept of attestation reports from a service
|
/linux-6.14.4/Documentation/bpf/ |
D | ringbuf.rst | 46 Another approach could introduce a new concept, alongside BPF map, to represent 50 would also add another concept that BPF developers would have to familiarize 58 familiar concept (no need to teach users a new type of object in BPF program),
|
/linux-6.14.4/drivers/net/can/mscan/ |
D | Kconfig | 8 implementation of the Motorola Scalable CAN concept targeted for
|
/linux-6.14.4/arch/xtensa/include/asm/ |
D | bootparam.h | 12 * (Concept borrowed from the 68K port)
|
/linux-6.14.4/Documentation/arch/x86/x86_64/ |
D | cpu-hotplug-spec.rst | 13 ACPI 3.0 specification). ACPI already has the concept of disabled LAPIC
|
/linux-6.14.4/Documentation/devicetree/bindings/media/xilinx/ |
D | xlnx,video.txt | 4 General concept
|
/linux-6.14.4/Documentation/timers/ |
D | hrtimers.rst | 24 the wheel concept, leading to even worse compromises. The timer wheel 33 wheel concept, it cannot be 'designed out' without inevitably
|
/linux-6.14.4/Documentation/arch/x86/ |
D | topology.rst | 26 The kernel does not care about the concept of physical sockets because a 77 packages in a consistent way, we introduced the concept of logical package
|
/linux-6.14.4/Documentation/crypto/ |
D | architecture.rst | 269 with the kernel crypto API. In this case, the concept described by the 366 Generic block ciphers follow the same concept as depicted with the ASCII 376 Keyed message digest implementations again follow the same concept as
|
/linux-6.14.4/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,rpm-master-stats.yaml | 13 The Qualcomm RPM (Resource Power Manager) architecture includes a concept
|
/linux-6.14.4/drivers/staging/media/atomisp/ |
D | TODO | 23 means that at least proof-of-concept libcamera integration needs to be
|
/linux-6.14.4/Documentation/netlabel/ |
D | lsm_interface.rst | 22 it uses the concept of security attributes to refer to the packet's security
|
/linux-6.14.4/kernel/ |
D | async.c | 18 More specifically, the asynchronous function call concept allows 24 Key to the asynchronous function call implementation is the concept of
|
/linux-6.14.4/arch/x86/entry/vsyscall/ |
D | vsyscall_64.c | 13 * addresses. This concept is problematic: 18 * - The whole concept is impossible for 32-bit compat userspace.
|
/linux-6.14.4/Documentation/driver-api/ |
D | edac.rst | 57 memories. FB-DIMM and RAMBUS use a different concept for channel, so 58 this concept doesn't apply there.
|
D | scsi.rst | 269 purely a software concept, the underlying hardware for a PHY and a 272 There is no concept of a SAS port in this code, users can see what PHYs
|
/linux-6.14.4/Documentation/scheduler/ |
D | sched-design-CFS.rst | 27 introduce the concept of "virtual runtime." The virtual runtime of a task 51 Most of the rest of CFS's design just falls out of this really simple concept,
|
/linux-6.14.4/include/linux/ |
D | tsm.h | 13 * Privilege level is a nested permission concept to allow confidential
|
/linux-6.14.4/Documentation/virt/kvm/s390/ |
D | s390-pv-boot.rst | 39 For PVMs this concept has been extended with new subcodes:
|
/linux-6.14.4/Documentation/driver-api/nvdimm/ |
D | firmware-activate.rst | 35 If the platform has a concept of incremental work needed to perform
|
/linux-6.14.4/Documentation/bpf/libbpf/ |
D | libbpf_overview.rst | 140 libbpf steps up the BPF program portability by supporting the BPF CO-RE concept. 166 specific kernel on the host. BPF CO-RE concept thus eliminates overhead
|
/linux-6.14.4/include/dt-bindings/mux/ |
D | ti-serdes.h | 11 * concept of bindings but rather contain pure constants values used only
|
/linux-6.14.4/drivers/thermal/mediatek/ |
D | auxadc_thermal.c | 479 * the bank concept wouldn't be necessary here. However, the SVS (Smart 520 * so the bank concept wouldn't be necessary here. However, the SVS (Smart 551 * so the bank concept wouldn't be necessary here. However, the SVS (Smart 585 * so the bank concept wouldn't be necessary here. However, the SVS (Smart 644 * the bank concept wouldn't be necessary here. However, the SVS (Smart
|
/linux-6.14.4/Documentation/gpu/ |
D | msm-preemption.rst | 13 priority levels. Having multiple rings is purely a software concept as the GPU
|
/linux-6.14.4/Documentation/networking/ |
D | representors.rst | 73 connecting the representor to the representee, similar in concept to a veth 130 .. [#] The concept here is that a hardware IP stack in the device performs the
|
123456789