Searched full:solve (Results 1 – 25 of 205) sorted by relevance
123456789
| /linux-6.14.4/Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 181 Open cross-HT issues that core scheduling does not solve
206 parallelism of the untrusted tasks, it would still solve the above issues while
213 to LKML to solve this, but it is debatable whether such windows are practically
|
| /linux-6.14.4/arch/powerpc/kernel/ |
| D | setup.h | 53 * tricky to solve for setup-common.c so have it here.
|
| /linux-6.14.4/Documentation/maintainer/ |
| D | modifying-patches.rst | 12 one submitters code and make him endorse your bugs. To solve this problem, it
|
| /linux-6.14.4/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 33 user space to solve the problem. In future, we may
|
| /linux-6.14.4/arch/riscv/lib/ |
| D | memmove.S | 49 * Solve for some register values now.
65 * Now solve for t5 and t6.
|
| /linux-6.14.4/Documentation/locking/ |
| D | robust-futexes.rst | 37 To solve such types of problems, "robust mutex" userspace APIs were
54 To solve this problem, the traditional approach was to extend the vma
|
| /linux-6.14.4/Documentation/core-api/ |
| D | idr.rst | 12 A common problem to solve is allocating identifiers (IDs); generally
|
| D | union_find.rst | 27 utilized to solve problems related to offline queries, dynamic connectivity,
|
| D | cachetlb.rst | 244 one way to solve this (in particular SPARC_FLAG_MMAPSHARED).
246 Next, you have to solve the D-cache aliasing issue for all
|
| /linux-6.14.4/Documentation/filesystems/ |
| D | virtiofs.rst | 25 solve these problems by providing file system access without networking.
|
| /linux-6.14.4/Documentation/networking/ |
| D | vxlan.rst | 7 The VXLAN protocol is a tunnelling protocol designed to solve the
|
| /linux-6.14.4/Documentation/arch/riscv/ |
| D | cmodx.rst | 21 There are two ways to solve this problem: use the riscv_flush_icache() syscall,
|
| /linux-6.14.4/drivers/gpu/drm/i915/gt/uc/ |
| D | intel_uc.h | 63 * To solve both these requirements, we commit to using the microcontrollers if
|
| /linux-6.14.4/drivers/net/ethernet/realtek/ |
| D | Kconfig | 64 of PCI shared memory (MMIO). This can possibly solve some problems
|
| /linux-6.14.4/sound/pci/cs46xx/ |
| D | cs46xx.c | 10 reloading the module may solve this.
|
| /linux-6.14.4/drivers/pinctrl/nomadik/ |
| D | pinctrl-abx500.h | 115 * intervals. To solve this quandary, we will place the
|
| /linux-6.14.4/drivers/hid/bpf/progs/ |
| D | Wacom__ArtPen.bpf.c | 22 * - to solve that, given that we know that the next event will be the same as
|
| /linux-6.14.4/drivers/staging/media/atomisp/pci/ |
| D | gdc_v2_defs.h | 23 /* -s is inserted to solve this issue, and */
|
| /linux-6.14.4/include/uapi/linux/ |
| D | libc-compat.h | 9 * This header is intended to solve the problem of UAPI definitions that
|
| /linux-6.14.4/include/linux/can/ |
| D | bittiming.h | 27 * To solve this issue, ISO 11898-1 introduces in section 11.3.3
|
| /linux-6.14.4/Documentation/arch/arm/ |
| D | interrupts.rst | 166 Please note that this will not solve all problems - some of them are
|
| /linux-6.14.4/drivers/clk/mediatek/ |
| D | clk-mtk.h | 28 * Only a few platforms are affected, so we solve issues given by the
|
| /linux-6.14.4/samples/bpf/ |
| D | cpustat_user.c | 149 * To solve this issue, below code forces to set 'scaling_max_freq' to 208MHz
|
| /linux-6.14.4/arch/arm/kernel/ |
| D | entry-ftrace.S | 14 * Newer GCCs (4.4+) solve this problem by using a version of mcount with call
|
| /linux-6.14.4/Documentation/trace/ |
| D | stm.rst | 26 To solve this mapping problem, stm class provides a policy management
|
123456789