/openbmc/linux/drivers/iommu/ |
H A D | io-pgfault.c | 50 struct list_head faults; member 85 list_for_each_entry_safe(iopf, next, &group->faults, list) { in iopf_handler() 193 INIT_LIST_HEAD(&group->faults); in iommu_queue_iopf() 194 list_add(&group->last_fault.list, &group->faults); in iommu_queue_iopf() 201 list_move(&iopf->list, &group->faults); in iommu_queue_iopf()
|
/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/drivers/md/ |
H A D | md-faulty.c | 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/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 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/tools/perf/util/ |
H A D | parse-events.l | 314 page-faults|faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS); } 315 minor-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS_MIN); } 316 major-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_PAGE_FAULTS_MAJ); } 319 alignment-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_ALIGNMENT_FAULTS); } 320 emulation-faults { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_EMULATION_FAULTS); }
|
/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/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/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 63 - Any user can always create a userfaultfd which traps userspace 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. 160 - For ``UFFDIO_REGISTER_MODE_MISSING`` faults, the fault needs to be 275 page faults in the guest scheduler so those guest processes that 370 not get further userland page faults from the removed area. Still, the [all …]
|
/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/drivers/gpu/drm/msm/ |
H A D | msm_submitqueue.c | 240 size_t size = min_t(size_t, args->len, sizeof(queue->faults)); in msm_submitqueue_query_faults() 245 args->len = sizeof(queue->faults); in msm_submitqueue_query_faults() 252 ret = copy_to_user(u64_to_user_ptr(args->data), &queue->faults, size); in msm_submitqueue_query_faults()
|
/openbmc/linux/Documentation/driver-api/ |
H A D | dma-buf.rst | 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 358 in the kernel even for resolving hardware page faults, e.g. by using copy [all …]
|
/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:
|
H A D | sysfs-bus-iio-thermocouple | 16 Open-circuit fault. The detection of open-circuit faults,
|
/openbmc/qemu/hw/sensor/ |
H A D | tmp105.c | 159 s->faults = tmp105_faultq[(s->config >> 3) & 3]; /* F */ in tmp105_write() 218 s->faults = tmp105_faultq[(s->config >> 3) & 3]; /* F */ in tmp105_post_load() 276 s->faults = tmp105_faultq[(s->config >> 3) & 3]; in tmp105_reset()
|
/openbmc/qemu/include/hw/sensor/ |
H A D | tmp105.h | 44 int faults; member
|
/openbmc/linux/tools/testing/selftests/mm/ |
H A D | hmm-tests.c | 43 uint64_t faults; member 200 buffer->faults = cmd.faults; in hmm_dmirror_cmd() 340 ASSERT_EQ(buffer->faults, 1); in TEST_F() 450 ASSERT_EQ(buffer->faults, 1); in TEST_F() 494 ASSERT_EQ(buffer->faults, 1); in TEST_F() 516 ASSERT_EQ(buffer->faults, 1); in TEST_F() 593 ASSERT_EQ(buffer->faults, 1); in TEST_F() 671 ASSERT_EQ(buffer->faults, 1); in TEST_F() 727 ASSERT_EQ(buffer->faults, 1); in TEST_F() 831 ASSERT_EQ(buffer->faults, 1); in TEST_F() [all …]
|
/openbmc/witherspoon-pfault-analysis/ |
H A D | README.md | 3 Code for detecting and analyzing power faults on Witherspoon.
|
/openbmc/linux/lib/ |
H A D | test_hmm_uapi.h | 28 __u64 faults; member
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/uim/uim/ |
H A D | JMP_BUF_GC_jmp_buf.patch | 14 /* Set up a handler for address faults which will longjmp to */
|
/openbmc/linux/Documentation/virt/kvm/devices/ |
H A 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
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-debug.rst | 14 high then the rate the kernel samples for NUMA hinting faults may be 35 Higher scan rates incur higher system overhead as page faults must be
|
/openbmc/linux/kernel/sched/ |
H A D | fair.c | 1407 unsigned long faults[]; member 1586 unsigned long faults = 0; in group_faults_priv() local 1590 faults += ng->faults[task_faults_idx(NUMA_MEM, node, 1)]; in group_faults_priv() 1593 return faults; in group_faults_priv() 1602 faults += ng->faults[task_faults_idx(NUMA_MEM, node, 0)]; in group_faults_shared() 1605 return faults; in group_faults_shared() 1641 unsigned long faults; in score_nearby_nodes() local 1680 score += faults; in score_nearby_nodes() 2592 max_faults = faults; in numa_group_count_active_nodes() 2794 max_faults = faults; in preferred_group_nid() [all …]
|
/openbmc/linux/tools/perf/tests/shell/ |
H A D | stat+std_output.sh | 13 event_name=(cpu-clock task-clock context-switches cpu-migrations page-faults stalled-cycles-fronten…
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | phase_fault_detection.md | 5 Specifies how to detect and log redundant phase faults in a voltage regulator. 22 Phase faults are detected and logged by executing actions:
|
/openbmc/linux/Documentation/i2c/ |
H A 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.)
|