| /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
|
| /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 …]
|
| /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
|
| /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 */
|
| /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
|
| /linux-5.10/lib/ |
| D | test_hmm_uapi.h | 21 * @faults: (out) number of device page faults seen
28 __u64 faults; member
|
| /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", \
|
| /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()
|
| /linux-5.10/arch/x86/mm/ |
| D | fault.c | 419 * Note we only handle faults in kernel here.
557 * ones are faults accessing the GDT, or LDT. Perhaps in show_fault_oops()
613 * kernel addresses are always protection faults. in set_signal_archinfo()
648 * the below recursive fault logic only apply to a faults from in no_context()
663 /* XXX: hwpoison faults will set the wrong code. */ in no_context()
723 * recover from such faults. in no_context()
812 * are always protection faults. in __bad_area_nosemaphore()
906 * 3. T1 : faults... in bad_area_access_error()
1009 * Spurious faults may only occur if the TLB contains an entry with
1011 * and reserved bit (R = 1) faults are never spurious.
[all …]
|
| /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()
|
| /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:
|
| /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
|
| /linux-5.10/tools/perf/util/ |
| D | parse-events.l | 340 page-faults|faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS); }
341 minor-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS_MIN); }
342 major-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS_MAJ); }
345 alignment-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_ALIGNMENT_FAULTS); }
346 emulation-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_EMULATION_FAULTS); }
|
| /linux-5.10/tools/perf/pmu-events/arch/x86/amdzen2/ |
| D | floating-point.json | 119 "BriefDescription": "Floating Point Dispatch Faults. YMM spill fault.",
125 "BriefDescription": "Floating Point Dispatch Faults. YMM fill fault.",
131 "BriefDescription": "Floating Point Dispatch Faults. XMM fill fault.",
137 "BriefDescription": "Floating Point Dispatch Faults. x87 fill fault.",
|
| /linux-5.10/arch/powerpc/lib/ |
| D | vmx-helper.c | 21 * We need to disable page faults as they can call schedule and in enter_vmx_usercopy()
22 * thus make us lose the VMX context. So on page faults, we just in enter_vmx_usercopy()
|
| /linux-5.10/drivers/gpu/drm/msm/ |
| D | msm_submitqueue.c | 126 size_t size = min_t(size_t, args->len, sizeof(queue->faults)); in msm_submitqueue_query_faults()
131 args->len = sizeof(queue->faults); in msm_submitqueue_query_faults()
138 ret = copy_to_user(u64_to_user_ptr(args->data), &queue->faults, size); in msm_submitqueue_query_faults()
|
| /linux-5.10/drivers/gpu/drm/nouveau/ |
| D | nouveau_svm.c | 334 * client, with replayable faults enabled). in nouveau_svmm_init()
647 /* Sort parsed faults by instance pointer to prevent unnecessary in nouveau_svm_fault()
649 * type to reduce the amount of work when handling the faults. in nouveau_svm_fault()
668 /* Process list of faults. */ in nouveau_svm_fault()
679 /* Cancel any faults from non-SVM channels. */ in nouveau_svm_fault()
686 /* We try and group handling of faults within a small in nouveau_svm_fault()
697 * permissions based on pending faults. in nouveau_svm_fault()
739 * same SVMM as faults are ordered by access type such in nouveau_svm_fault()
742 * ie. WRITE faults appear first, thus any handling of in nouveau_svm_fault()
743 * pending READ faults will already be satisfied. in nouveau_svm_fault()
[all …]
|
| /linux-5.10/tools/testing/selftests/powerpc/mm/ |
| D | pkey_exec_prot.c | 52 /* Check if too many faults have occurred for a single test case */ in segv_handler()
54 sigsafe_err("got too many faults for the same address\n"); in segv_handler()
228 * This should generate two faults. First, a pkey fault in test()
256 * This should generate pkey faults based on IAMR bits which in test()
|
| /linux-5.10/Documentation/i2c/ |
| D | fault-codes.rst | 11 Not all fault reports imply errors; "page faults" should be a familiar
13 faults. There may be fancier recovery schemes that are appropriate in
82 about probe faults other than ENXIO and ENODEV.)
|
| /linux-5.10/tools/testing/selftests/vm/ |
| D | hmm-tests.c | 42 uint64_t faults; member
142 buffer->faults = cmd.faults; in hmm_dmirror_cmd()
268 ASSERT_EQ(buffer->faults, 1); in TEST_F()
378 ASSERT_EQ(buffer->faults, 1); in TEST_F()
422 ASSERT_EQ(buffer->faults, 1); in TEST_F()
444 ASSERT_EQ(buffer->faults, 1); in TEST_F()
521 ASSERT_EQ(buffer->faults, 1); in TEST_F()
599 ASSERT_EQ(buffer->faults, 1); in TEST_F()
655 ASSERT_EQ(buffer->faults, 1); in TEST_F()
713 ASSERT_EQ(buffer->faults, 1); in TEST_F()
[all …]
|
| /linux-5.10/arch/powerpc/mm/ |
| D | fault.c | 107 * 3. T1 : faults... in bad_access_pkey()
201 /* NX faults set DSISR_PROTFAULT on the 8xx, DSISR_NOEXEC_OR_G on others */ in bad_kernel_fault()
244 * faults just to hit a pkey fault as soon as we fill in a in access_pkey_error()
458 /* When running in the kernel we expect faults to occur only to in __do_page_fault()
459 * addresses in user space. All other faults represent errors in the in __do_page_fault()
467 * As the vast majority of faults will be valid we will only perform in __do_page_fault()
|
| /linux-5.10/arch/powerpc/kvm/ |
| D | book3s_segment.S | 77 /* Activate guest mode, so faults get handled by KVM */
204 /* Restore R1/R2 so we can handle faults */
284 /* In case lwz faults */
289 /* Set guest mode to 'jump over instruction' so if lwz faults
|
| /linux-5.10/Documentation/arm64/ |
| D | memory-tagging-extension.rst | 58 Tag Check Faults
75 thread, asynchronously following one or multiple tag check faults,
84 - ``PR_MTE_TCF_NONE`` - *Ignore* tag check faults
254 * Enable the tagged address ABI, synchronous MTE tag check faults and
|
| /linux-5.10/Documentation/fault-injection/ |
| D | fault-injection.rst | 179 In order to inject faults while debugfs is not available (early boot time),
199 Note that this file enables all types of faults (slab, futex, etc).
204 This feature is intended for systematic testing of faults in a single
391 Systematic faults using fail-nth
394 The following code systematically faults 0-th, 1-st, 2-nd and so on
|