| /kernel/linux/linux-6.6/drivers/iommu/ |
| D | io-pgfault.c | 3 * Handle device page faults
33 * @partial: faults that are part of a Page Request Group for which the last
50 struct list_head faults; member
85 list_for_each_entry_safe(iopf, next, &group->faults, list) { in iopf_handler()
88 * faults in the group if there is an error. in iopf_handler()
111 * them before reporting faults. A PASID Stop Marker (LRW = 0b100) doesn't
131 * request completes, outstanding faults will have been dealt with by the time
137 * freed after the device has stopped generating page faults (or the iommu
138 * hardware has been set to block the page faults) and the pending page faults
184 * need to clean up before leaving, otherwise partial faults in iommu_queue_iopf()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 10 memory page faults, something otherwise only the kernel code could do.
19 regions of virtual memory with it. Then, any page faults which occur within the
26 1) ``read/POLLIN`` protocol to notify a userland thread of the faults
58 handle kernel page faults have been a useful tool for exploiting the kernel).
63 - Any user can always create a userfaultfd which traps userspace page faults
67 - In order to also trap kernel page faults for the address space, either the
80 to /dev/userfaultfd can always create userfaultfds that trap kernel page faults;
102 other than page faults are supported. These events are described in more
124 bitmask will specify to the kernel which kind of faults to track for
129 hugetlbfs), or all types of intercepted faults.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 63 presence of some faults. See V4L2_CID_FLASH_FAULT.
103 control may not be possible in presence of some faults. See
126 some faults. See V4L2_CID_FLASH_FAULT.
134 Faults related to the flash. The faults tell about specific problems
135 in the flash chip itself or the LEDs attached to it. Faults may
138 if the fault affects the flash LED. Exactly which faults have such
139 an effect is chip dependent. Reading the faults resets the control
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 63 presence of some faults. See V4L2_CID_FLASH_FAULT.
106 control may not be possible in presence of some faults. See
129 some faults. See V4L2_CID_FLASH_FAULT.
137 Faults related to the flash. The faults tell about specific problems
138 in the flash chip itself or the LEDs attached to it. Faults may
141 if the fault affects the flash LED. Exactly which faults have such
142 an effect is chip dependent. Reading the faults resets the control
|
| /kernel/linux/linux-6.6/arch/powerpc/platforms/powernv/ |
| D | vas-fault.c | 24 * 8MB FIFO can be used if expects more faults for each VAS
57 * It can raise a single interrupt for multiple faults. Expects OS to
58 * process all valid faults and return credit for each fault on user
78 * VAS can interrupt with multiple page faults. So process all in vas_fault_thread_fn()
92 * fifo_in_progress is set. Means these new faults will be in vas_fault_thread_fn()
153 * NX sees faults only with user space windows. in vas_fault_thread_fn()
176 * NX can generate an interrupt for multiple faults. So the in vas_fault_handler()
178 * entry. In case if NX sees continuous faults, it is possible in vas_fault_handler()
197 * FIFO upon page faults.
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/powernv/ |
| D | vas-fault.c | 24 * 8MB FIFO can be used if expects more faults for each VAS
74 * and faults will not be generated for kernel requests. in update_csb()
102 * threads later. We should handle faults if NX encounters in update_csb()
103 * pages faults on these requests. Update CSB with translation in update_csb()
201 * It can raise a single interrupt for multiple faults. Expects OS to
202 * process all valid faults and return credit for each fault on user
222 * VAS can interrupt with multiple page faults. So process all in vas_fault_thread_fn()
236 * fifo_in_progress is set. Means these new faults will be in vas_fault_thread_fn()
313 * NX can generate an interrupt for multiple faults. So the in vas_fault_handler()
315 * entry. In case if NX sees continuous faults, it is possible in vas_fault_handler()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 25 …rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve faults
26 …svd.usage_in_bytes # show current reservations and no-reserve faults for "hugepagesize"…
28 …tlb.<hugepagesize>.limit_in_bytes # set/show limit of "hugepagesize" hugetlb faults
108 For shared HugeTLB memory, both HugeTLB reservation and page faults are charged
119 When a HugeTLB cgroup goes offline with some reservations or faults still
130 complex compared to the tracking of HugeTLB faults, so it is significantly
|
| /kernel/linux/linux-5.10/arch/ia64/include/asm/ |
| D | kregs.h | 121 #define IA64_DCR_DM_BIT 8 /* defer TLB miss faults */
122 #define IA64_DCR_DP_BIT 9 /* defer page-not-present faults */
123 #define IA64_DCR_DK_BIT 10 /* defer key miss faults */
124 #define IA64_DCR_DX_BIT 11 /* defer key permission faults */
125 #define IA64_DCR_DR_BIT 12 /* defer access right faults */
126 #define IA64_DCR_DA_BIT 13 /* defer access bit faults */
127 #define IA64_DCR_DD_BIT 14 /* defer debug faults */
|
| /kernel/linux/linux-6.6/arch/ia64/include/asm/ |
| D | kregs.h | 121 #define IA64_DCR_DM_BIT 8 /* defer TLB miss faults */
122 #define IA64_DCR_DP_BIT 9 /* defer page-not-present faults */
123 #define IA64_DCR_DK_BIT 10 /* defer key miss faults */
124 #define IA64_DCR_DX_BIT 11 /* defer key permission faults */
125 #define IA64_DCR_DR_BIT 12 /* defer access right faults */
126 #define IA64_DCR_DA_BIT 13 /* defer access bit faults */
127 #define IA64_DCR_DD_BIT 14 /* defer debug faults */
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | dma-buf.rst | 292 Recoverable Hardware Page Faults Implications
295 Modern hardware supports recoverable page faults, which has a lot of
301 means any workload using recoverable page faults cannot use DMA fences for
308 faults. Specifically this means implicit synchronization will not be possible.
309 The exception is when page faults are only used as migration hints and never to
311 faults on GPUs are limited to pure compute workloads.
315 job with a DMA fence and a compute workload using recoverable page faults are
346 to guarantee all pending GPU page faults are flushed.
349 allocating memory to repair hardware page faults, either through separate
353 robust to limit the impact of handling hardware page faults to the specific
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | virtext.h | 36 * Disable VMX and clear CR4.VMXE (even if VMXOFF faults)
40 * Eat all faults as all other faults on VMXOFF faults are mode related, i.e.
41 * faults are guaranteed to be due to the !post-VMXON check unless the CPU is
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 25 …rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve faults
26 …svd.usage_in_bytes # show current reservations and no-reserve faults for "hugepagesize"…
28 …tlb.<hugepagesize>.limit_in_bytes # set/show limit of "hugepagesize" hugetlb faults
112 For shared HugeTLB memory, both HugeTLB reservation and page faults are charged
123 When a HugeTLB cgroup goes offline with some reservations or faults still
134 complex compared to the tracking of HugeTLB faults, so it is significantly
|
| /kernel/linux/linux-6.6/Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 96 newer VM_BIND mode, the VM_BIND mode with GPU page faults and possible future
98 The older execbuf mode and the newer VM_BIND mode without page faults manages
99 residency of backing storage using dma_fence. The VM_BIND mode with page faults
108 In future, when GPU page faults are supported, we can potentially use a
124 When GPU page faults are supported, the execbuf path do not take any of these
180 Where GPU page faults are not available, kernel driver upon buffer invalidation
210 GPU page faults
212 GPU page faults when supported (in future), will only be supported in the
214 binding will require using dma-fence to ensure residency, the GPU page faults
240 faults enabled.
|
| /kernel/linux/linux-6.6/tools/testing/selftests/powerpc/mm/ |
| D | stress_code_patching.sh | 20 echo "Testing for spurious faults when mapping kernel memory..."
44 echo "FAILED: Mapping kernel memory causes spurious faults" 1>&2
47 echo "OK: Mapping kernel memory does not cause spurious faults"
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 12 memory page faults, something otherwise only the kernel code could do.
25 1) ``read/POLLIN`` protocol to notify a userland thread of the faults
80 page faults, it has to verify that ``uffdio_api.features`` has appropriate
88 bitmask will specify to the kernel which kind of faults to track for
174 Guest async page faults, ``FOLL_NOWAIT`` and all other ``GUP*`` features work
176 page faults in the guest scheduler so those guest processes that
271 not get further userland page faults from the removed area. Still, the
275 Unlike userland page faults which have to be synchronous and require
|
| /kernel/linux/linux-5.10/lib/ |
| D | test_hmm_uapi.h | 21 * @faults: (out) number of device page faults seen
28 __u64 faults; member
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | virtio_balloon.h | 66 #define VIRTIO_BALLOON_S_MAJFLT 2 /* Number of major faults */
67 #define VIRTIO_BALLOON_S_MINFLT 3 /* Number of minor faults */
79 VIRTIO_BALLOON_S_NAMES_prefix "major-faults", \
80 VIRTIO_BALLOON_S_NAMES_prefix "minor-faults", \
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | virtio_balloon.h | 66 #define VIRTIO_BALLOON_S_MAJFLT 2 /* Number of major faults */
67 #define VIRTIO_BALLOON_S_MINFLT 3 /* Number of minor faults */
79 VIRTIO_BALLOON_S_NAMES_prefix "major-faults", \
80 VIRTIO_BALLOON_S_NAMES_prefix "minor-faults", \
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| D | ltc4260.c | 98 if (fault) /* Clear reported faults in chip register */ in ltc4260_bool_show()
110 * UV/OV faults are associated with the input voltage, and the POWER BAD and
111 * FET SHORT faults are associated with the output voltage.
156 /* Clear faults */ in ltc4260_probe()
|
| /kernel/linux/linux-6.6/drivers/hwmon/ |
| D | ltc4260.c | 98 if (fault) /* Clear reported faults in chip register */ in ltc4260_bool_show()
110 * UV/OV faults are associated with the input voltage, and the POWER BAD and
111 * FET SHORT faults are associated with the output voltage.
156 /* Clear faults */ in ltc4260_probe()
|
| /kernel/linux/linux-6.6/lib/ |
| D | test_hmm_uapi.h | 21 * @faults: (out) number of device page faults seen
28 __u64 faults; member
|
| /kernel/linux/linux-5.10/arch/x86/mm/ |
| D | fault.c | 426 * Note we only handle faults in kernel here.
564 * ones are faults accessing the GDT, or LDT. Perhaps in show_fault_oops()
620 * kernel addresses are always protection faults. in set_signal_archinfo()
655 * the below recursive fault logic only apply to a faults from in no_context()
670 /* XXX: hwpoison faults will set the wrong code. */ in no_context()
730 * recover from such faults. in no_context()
819 * are always protection faults. in __bad_area_nosemaphore()
913 * 3. T1 : faults... in bad_area_access_error()
1016 * Spurious faults may only occur if the TLB contains an entry with
1018 * and reserved bit (R = 1) faults are never spurious.
[all …]
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | md-faulty.c | 32 * All current faults can be clear using a layout of "0".
79 sector_t faults[MaxFault]; member
105 if (conf->faults[i] >= start && in check_sector()
106 conf->faults[i] < end) { in check_sector()
129 if (conf->faults[i] == start) { in add_sector()
158 conf->faults[n] = start; in add_sector()
|
| /kernel/linux/linux-6.6/drivers/md/ |
| D | md-faulty.c | 32 * All current faults can be clear using a layout of "0".
79 sector_t faults[MaxFault]; member
105 if (conf->faults[i] >= start && in check_sector()
106 conf->faults[i] < end) { in check_sector()
129 if (conf->faults[i] == start) { in add_sector()
158 conf->faults[n] = start; in add_sector()
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 54 Space separated list of flash faults that may have occurred.
55 Flash faults are re-read after strobing the flash. Possible
56 flash faults:
|