| /openbmc/linux/drivers/iommu/ |
| H A 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 …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | phase_fault_detection.hpp | 40 * Detects and logs redundant phase faults in a voltage regulator.
58 * Phase faults are detected by executing actions.
74 * @param actions Actions that detect phase faults in the regulator.
76 * faults. If not specified, the regulator will be used.
100 * Executes the actions that detect phase faults in the regulator.
102 * If the required number of consecutive phase faults are detected, an error
114 * Returns the actions that detect phase faults in the regulator.
125 * faults.
141 * consecutive faults. If the required number of consecutive faults have
167 * Actions that detect phase faults in the regulator.
[all …]
|
| H A D | phase_fault_detection.cpp | 40 * Number of consecutive phase faults required to log an error. This provides
59 // Execute the actions to detect phase faults in execute()
62 // Check for any N or N+1 phase faults that were detected in execute()
75 "Unable to detect phase faults in regulator " + in execute()
116 // If the required number of consecutive faults have been detected in checkForPhaseFault()
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A 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 …]
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 17 various faults, and report vital product data (VPD). Some of the function will
39 input power and power FRU faults, during boot and at runtime only.
98 any faults are occurring, logging errors as appropriate.
137 - Application detects and logs faults for power supply faults including input
138 faults, output faults, shorts, current share faults, communication failures,
143 - System operates through power supply faults and power line disturbances as
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| /openbmc/linux/arch/powerpc/platforms/powernv/ |
| H A 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.
|
| /openbmc/linux/arch/ia64/include/asm/ |
| H A 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 */
|
| /openbmc/linux/Documentation/driver-api/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A 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
|
| /openbmc/linux/Documentation/gpu/rfc/ |
| H A 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.
|
| /openbmc/linux/tools/testing/selftests/powerpc/mm/ |
| H A 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"
|
| /openbmc/witherspoon-pfault-analysis/power-sequencer/ |
| H A D | ucd90160.hpp | 61 * Clears faults in the device
101 * Checks for VOUT faults on the device.
104 * devices, and VOUT faults are voltage faults
112 * Checks for PGOOD faults on the device.
115 * devices, and this check will look for faults of
|
| H A D | runtime_monitor.hpp | 18 * Monitors the power sequencer for faults at runtime
27 * 2) Polls for faults, as some won't always drop PGOOD.
61 * Clears faults and then runs DeviceMonitor::run to
|
| /openbmc/phosphor-power/power-sequencer/ |
| H A D | ucd90160.hpp | 61 * Clears faults in the device
101 * Checks for VOUT faults on the device.
104 * devices, and VOUT faults are voltage faults
112 * Checks for PGOOD faults on the device.
115 * devices, and this check will look for faults of
|
| /openbmc/qemu/docs/interop/ |
| H A D | virtio-balloon-stats.rst | 33 - stat-major-faults
34 - stat-minor-faults
96 "stat-minor-faults": 219028,
97 "stat-major-faults": 235,
|
| /openbmc/openpower-hw-diags/analyzer/plugins/ |
| H A D | p10-tod-plugins.cpp | 47 /** All chips with internal path faults. */
50 /** The chips sourcing the clocks to non-MDMT chips with faults. */
87 * @return The list of all chips with internal faults.
115 * with step check faults.
326 // likely that any downstream step check faults are due to the fault in in tod_step_check_fault()
333 // check faults. in tod_step_check_fault()
360 else if (!networkFaults.empty()) // network path faults in tod_step_check_fault()
372 else if (!internalFaults.empty()) // interal path faults in tod_step_check_fault()
|
| /openbmc/phosphor-power/phosphor-regulators/src/actions/ |
| H A D | action_environment.hpp | 47 * - faults detected by actions (if any)
95 * Adds the specified phase fault to the set of faults that have been
152 * Returns the set of phase faults that have been detected (if any).
154 * @return phase faults detected
274 * Redundant phase faults that have been detected.
|
| /openbmc/linux/include/uapi/linux/ |
| H A 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", \
|
| /openbmc/qemu/include/standard-headers/linux/ |
| H A 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 */
85 VIRTIO_BALLOON_S_NAMES_prefix "major-faults", \
86 VIRTIO_BALLOON_S_NAMES_prefix "minor-faults", \
|
| /openbmc/linux/drivers/hwmon/ |
| H A 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()
|
| /openbmc/linux/lib/ |
| H A D | test_hmm_uapi.h | 21 * @faults: (out) number of device page faults seen
28 __u64 faults; member
|
| /openbmc/phosphor-power/phosphor-power-supply/test/ |
| H A D | power_supply_tests.cpp | 115 // The call for clearing faults includes clearing VIN_UV fault. in setMissingToPresentExpects()
255 // In order to get the various faults tested, the power supply needs to in TEST_F()
274 // Start with STATUS_WORD 0x0000. Powered on, no faults. in TEST_F()
378 // Turning VIN_UV fault off causes clearing of faults, causing read of in TEST_F()
727 // STATUS_WORD 0x0000 is powered on, no faults. in TEST_F()
761 // STATUS_WORD 0x0000 is powered on, no faults. in TEST_F()
816 // pgoodFault at PGOOD_DEGLITCH_LIMIT, all other faults are deglitched in TEST_F()
857 // Faults clear on READ_VIN 0 -> !0 in TEST_F()
875 // All faults deglitched now. Check for false before limit above. in TEST_F()
922 // We only cleared the VIN_UV and OFF faults. in TEST_F()
[all …]
|
| /openbmc/linux/drivers/md/ |
| H A 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()
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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:
|