Home
last modified time | relevance | path

Searched full:faults (Results 1 – 25 of 385) sorted by relevance

12345678910>>...16

/linux/tools/perf/pmu-events/arch/common/common/
H A Dsoftware.json18 "EventName": "faults",
19 "BriefDescription": "Number of page faults [This event is an alias of page-faults]",
24 "EventName": "page-faults",
25 "BriefDescription": "Number of page faults [This event is an alias of faults]",
54 "EventName": "minor-faults",
55 "BriefDescription": "Number of minor page faults. Minor faults don't require I/O to handle",
60 "EventName": "major-faults",
61 "BriefDescription": "Number of major page faults. Major faults require I/O to handle",
66 "EventName": "alignment-faults",
67 "BriefDescription": "Number of kernel handled memory alignment faults",
[all …]
H A Dmetrics.json30 "BriefDescription": "Page faults per CPU second",
31 "MetricExpr": "(software@page\\-faults\\,name\\=page\\-faults@ * 1e9) / (software@cpu\\-clock\\,name\\=cpu\\-clock@ if #target_cpu else software@task\\-clock\\,name\\=task\\-clock@)",
34 "ScaleUnit": "1faults/sec",
/linux/drivers/iommu/
H A Dio-pgfault.c3 * Handle device page faults
46 list_for_each_entry_safe(iopf, next, &group->faults, list) { in __iopf_free_group()
99 INIT_LIST_HEAD(&group->faults); in iopf_group_alloc()
101 list_add(&group->last_fault.list, &group->faults); in iopf_group_alloc()
103 /* See if we have partial faults for this group */ in iopf_group_alloc()
108 list_move(&iopf->list, &group->faults); in iopf_group_alloc()
110 list_add(&group->pending_node, &iopf_param->faults); in iopf_group_alloc()
113 group->fault_count = list_count_nodes(&group->faults); in iopf_group_alloc()
134 * managed PASID table. Therefore page faults for in find_fault_handler()
181 * them before reporting faults. A PASID Stop Marker (LRW = 0b100) doesn't
[all …]
/linux/arch/powerpc/platforms/powernv/
H A Dvas-fault.c24 * 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.
/linux/Documentation/gpu/rfc/
H A Di915_vm_bind.rst96 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.
H A Dgpusvm.rst94 * Concurrent GPU faults
95 * CPU faults are concurrent so makes sense to have concurrent GPU
96 faults.
/linux/tools/testing/selftests/powerpc/mm/
H A Dstress_code_patching.sh20 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"
/linux/drivers/gpu/drm/xe/
H A Dxe_pagefault.c24 * DOC: Xe page faults
26 * Xe page faults are handled in two layers. The producer layer interacts with
27 * hardware or firmware to receive and parse faults into struct xe_pagefault,
28 * then forwards them to the consumer. The consumer layer services the faults
31 * The consumer uses a page fault queue sized to absorb all potential faults and
354 * user can issue separate page faults per EU and per CS in xe_pagefault_queue_init()
428 /* Squash all pending faults on the GT */ in xe_pagefault_queue_reset()
446 * Reset the Xe page fault state for a GT; that is, squash any pending faults on
/linux/include/uapi/linux/
H A Dvirtio_balloon.h66 #define VIRTIO_BALLOON_S_MAJFLT 2 /* Number of major faults */
67 #define VIRTIO_BALLOON_S_MINFLT 3 /* Number of minor faults */
85 VIRTIO_BALLOON_S_NAMES_prefix "major-faults", \
86 VIRTIO_BALLOON_S_NAMES_prefix "minor-faults", \
H A Duserfaultfd.h219 * UFFD_FEATURE_MINOR_HUGETLBFS indicates that minor faults
227 * faults would be provided and the offset within the page would not be
249 * Pages are made inaccessible via UFFDIO_RWPROTECT and faults
253 * UFFDIO_REGISTER_MODE_RWP. When set, faults on read-write
346 * NOTE: Write protecting a region (WP=1) is unrelated to page faults,
428 * Create a userfaultfd that can handle page faults only in user mode.
/linux/lib/
H A Dtest_hmm_uapi.h21 * @faults: (out) number of device page faults seen
28 __u64 faults; member
/linux/Documentation/ABI/testing/
H A Dsysfs-class-led-flash54 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/Documentation/virt/kvm/devices/
H A Ds390_flic.rst18 - 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
64 Disables async page faults for the guest and waits until already pending
65 async page faults are done. This is necessary to trigger a completion interrupt
/linux/tools/perf/pmu-events/arch/x86/amdzen2/
H A Dfloating-point.json119 "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/tools/perf/pmu-events/arch/x86/amdzen3/
H A Dfloating-point.json118 "BriefDescription": "Floating Point Dispatch Faults. YMM spill fault.",
124 "BriefDescription": "Floating Point Dispatch Faults. YMM fill fault.",
130 "BriefDescription": "Floating Point Dispatch Faults. XMM fill fault.",
136 "BriefDescription": "Floating Point Dispatch Faults. x87 fill fault.",
/linux/Documentation/i2c/
H A Dfault-codes.rst11 Not all fault reports imply errors; "page faults" should be a familiar
13 faults. There may be fancier recovery schemes that are appropriate in
86 about probe faults other than ENXIO and ENODEV.)
/linux/arch/powerpc/lib/
H A Dvmx-helper.c20 * We need to disable page faults as they can call schedule and in enter_vmx_usercopy()
21 * thus make us lose the VMX context. So on page faults, we just in enter_vmx_usercopy()
/linux/kernel/trace/rv/monitors/pagefault/
H A Dpagefault.c68 .description = "Monitor that RT tasks do not raise page faults",
88 MODULE_DESCRIPTION("pagefault: Monitor that RT tasks do not raise page faults");
/linux/arch/x86/include/asm/
H A Dkfence.h75 * We need to avoid IPIs, as we may get KFENCE allocations or faults in kfence_protect_page()
78 * lazy fault handling takes care of faults after the page is PRESENT. in kfence_protect_page()
/linux/tools/testing/selftests/mm/
H A Duffd-common.c22 * to avoid non alignment faults on non-x86 archs.
406 /* Write protection page faults */ in wp_range()
469 /* Write protect page faults */ in uffd_handle_page_fault()
477 * Minor page faults in uffd_handle_page_fault()
498 * Missing page faults. in uffd_handle_page_fault()
501 * faults. It's guaranteed because the only threads that in uffd_handle_page_fault()
502 * will trigger uffd faults are the locking threads, and in uffd_handle_page_fault()
/linux/arch/powerpc/kvm/
H A Dbook3s_segment.S77 /* Activate guest mode, so faults get handled by KVM */
207 /* Restore R1/R2 so we can handle faults */
287 /* In case lwz faults */
292 /* Set guest mode to 'jump over instruction' so if lwz faults
/linux/tools/perf/pmu-events/arch/x86/amdzen4/
H A Dfloating-point.json785 "BriefDescription": "Floating-point dispatch faults for x87 fills.",
791 "BriefDescription": "Floating-point dispatch faults for XMM fills.",
797 "BriefDescription": "Floating-point dispatch faults for YMM fills.",
803 "BriefDescription": "Floating-point dispatch faults for YMM spills.",
809 "BriefDescription": "Floating-point dispatch faults of all types for SSE and AVX ops.",
815 "BriefDescription": "Floating-point dispatch faults of all types.",
/linux/tools/perf/tests/shell/
H A Dstat+std_output.sh14 event_name=(cpu-clock task-clock context-switches cpu-migrations page-faults stalled-cycles-fronten…
15 event_metric=("CPUs_utilized" "CPUs_utilized" "cs/sec" "migrations/sec" "faults/sec" "frontend_cycl…
/linux/Documentation/arch/x86/
H A Dpti.rst183 * Double faults: overflowing the kernel stack because of page
184 faults upon page faults. Caused by touching non-pti-mapped
/linux/arch/microblaze/mm/
H A Dfault.c127 /* When running in the kernel we expect faults to occur only to in do_page_fault()
128 * addresses in user space. All other faults represent errors in the in do_page_fault()
136 * As the vast majority of faults will be valid we will only perform in do_page_fault()

12345678910>>...16