| /kernel/linux/linux-4.19/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_ih.c | 211 * If there are too many pending page faults, this will fail. Retry
216 * -ENOSPC if there are too many pending faults.
223 if (WARN_ON_ONCE(!adev->irq.ih.faults)) in amdgpu_ih_add_fault()
225 * support retry faults and require retry filtering. in amdgpu_ih_add_fault()
229 spin_lock_irqsave(&adev->irq.ih.faults->lock, flags); in amdgpu_ih_add_fault()
232 if (adev->irq.ih.faults->count >= (1 << (AMDGPU_PAGEFAULT_HASH_BITS-1))) in amdgpu_ih_add_fault()
235 r = chash_table_copy_in(&adev->irq.ih.faults->hash, key, NULL); in amdgpu_ih_add_fault()
237 adev->irq.ih.faults->count++; in amdgpu_ih_add_fault()
243 spin_unlock_irqrestore(&adev->irq.ih.faults->lock, flags); in amdgpu_ih_add_fault()
262 if (!adev->irq.ih.faults) in amdgpu_ih_clear_fault()
[all …]
|
| D | vega10_ih.c | 243 /* Filter retry page faults, let only the first one pass. If in vega10_ih_prescreen_iv()
244 * there are too many outstanding faults, ignore them until in vega10_ih_prescreen_iv()
245 * some faults get cleared. in vega10_ih_prescreen_iv()
273 * ignore further page faults in vega10_ih_prescreen_iv()
278 /* Track retry faults in per-VM fault FIFO. */ in vega10_ih_prescreen_iv()
288 r = kfifo_put(&vm->faults, key); in vega10_ih_prescreen_iv()
389 adev->irq.ih.faults = kmalloc(sizeof(*adev->irq.ih.faults), GFP_KERNEL); in vega10_ih_sw_init()
390 if (!adev->irq.ih.faults) in vega10_ih_sw_init()
392 INIT_CHASH_TABLE(adev->irq.ih.faults->hash, in vega10_ih_sw_init()
394 spin_lock_init(&adev->irq.ih.faults->lock); in vega10_ih_sw_init()
[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-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-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-4.19/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-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-4.19/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
122 Guest async page faults, FOLL_NOWAIT and all other GUP features work
124 page faults in the guest scheduler so those guest processes that
219 not get further userland page faults from the removed area. Still, the
223 Unlike userland page faults which have to be synchronous and require
|
| /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-4.19/include/uapi/linux/ |
| D | virtio_balloon.h | 50 #define VIRTIO_BALLOON_S_MAJFLT 2 /* Number of major faults */
51 #define VIRTIO_BALLOON_S_MINFLT 3 /* Number of minor faults */
63 VIRTIO_BALLOON_S_NAMES_prefix "major-faults", \
64 VIRTIO_BALLOON_S_NAMES_prefix "minor-faults", \
|
| /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-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()
|
| D | ltc4222.c | 112 if (fault) /* Clear reported faults in chip register */ in ltc4222_bool_show()
126 * UV/OV faults are associated with the input voltage, and power bad and fet
127 * faults are associated with the output voltage.
192 /* Clear faults */ in ltc4222_probe()
|
| /kernel/linux/linux-4.19/Documentation/virtual/kvm/devices/ |
| D | s390_flic.txt | 15 - enable/disable for the guest transparent async page faults
53 Enables async page faults for the guest. So in case of a major page fault
57 Disables async page faults for the guest and waits until already pending
58 async page faults are done. This is necessary to trigger a completion interrupt
|
| /kernel/linux/linux-4.19/drivers/hwmon/ |
| D | ltc4260.c | 107 if (fault) /* Clear reported faults in chip register */ in ltc4260_show_bool()
121 * UV/OV faults are associated with the input voltage, and the POWER BAD and
122 * FET SHORT faults are associated with the output voltage.
172 /* Clear faults */ in ltc4260_probe()
|
| D | ltc4222.c | 121 if (fault) /* Clear reported faults in chip register */ in ltc4222_show_bool()
139 * UV/OV faults are associated with the input voltage, and power bad and fet
140 * faults are associated with the output voltage.
208 /* Clear faults */ in ltc4222_probe()
|
| /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/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:
|
| /kernel/linux/linux-4.19/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:
|
| /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-5.10/Documentation/virt/kvm/devices/ |
| D | s390_flic.rst | 18 - enable/disable for the guest transparent async page faults
58 Enables async page faults for the guest. So in case of a major page fault
62 Disables async page faults for the guest and waits until already pending
63 async page faults are done. This is necessary to trigger a completion interrupt
|
| /kernel/linux/linux-4.19/drivers/md/ |
| D | md-faulty.c | 41 * All current faults can be clear using a layout of "0".
88 sector_t faults[MaxFault]; member
114 if (conf->faults[i] >= start && in check_sector()
115 conf->faults[i] < end) { in check_sector()
138 if (conf->faults[i] == start) { in add_sector()
167 conf->faults[n] = start; in add_sector()
|
| /kernel/linux/linux-4.19/arch/x86/mm/ |
| D | fault.c | 170 * 3. T1 : faults...
596 * Note we only handle faults in kernel here.
732 * the below recursive fault logic only apply to a faults from in no_context()
749 /* XXX: hwpoison faults will set the wrong code. */ in no_context()
885 * Instruction fetch faults in the vsyscall page might need in __bad_area_nosemaphore()
898 * are always protection faults. in __bad_area_nosemaphore()
1078 * Spurious faults may only occur if the TLB contains an entry with
1080 * and reserved bit (R = 1) faults are never spurious.
1102 * spurious faults. in spurious_fault()
1107 * faults. in spurious_fault()
[all …]
|