| /openbmc/linux/Documentation/mm/ |
| H A D | free_page_reporting.rst | 2 Free Page Reporting
5 Free page reporting is an API by which a device can register to receive
16 page reporting interface with the reporting framework assuming no other
17 page reporting devices are already registered.
19 Once registered the page reporting API will begin reporting batches of
20 pages to the driver. The API will start reporting pages 2 seconds after
24 Pages reported will be stored in the scatterlist passed to the reporting
30 Prior to removing a driver that is making use of free page reporting it
33 reporting removed. Doing this will prevent further reports from being
36 left off in terms of reporting free pages.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | error-reporting-tool.rst | 3 Using the Error Reporting Tool
6 The error reporting tool allows you to submit errors encountered during
15 There is a live instance of the error reporting server at
29 By default, the error reporting tool is disabled. You can enable it by
36 By default, the error reporting feature stores information in
44 reporting causes the build process to collect the errors and store them
72 To disable the error reporting feature, simply remove or comment out the
78 Setting Up Your Own Error Reporting Server
81 If you want to set up your own error reporting server, you can obtain
|
| /openbmc/linux/Documentation/PCI/ |
| H A D | pcieaer-howto.rst | 5 The PCI Express Advanced Error Reporting Driver Guide HOWTO
20 Reporting (AER) driver and provides information on how to use it, as
30 defines two error reporting paradigms: the baseline capability and
31 the Advanced Error Reporting capability. The baseline capability is
33 set of error reporting requirements. Advanced Error Reporting
34 capability is implemented with a PCIe Advanced Error Reporting
35 extended capability structure providing more robust error reporting.
38 Error Reporting capability. The PCIe AER driver provides three basic
121 When PCIe error reporting is enabled, a device will automatically send an
123 an error. The Root Port, upon receiving an error reporting message,
[all …]
|
| /openbmc/linux/mm/ |
| H A D | page_reporting.c | 38 MODULE_PARM_DESC(page_reporting_order, "Set page reporting order");
59 /* request page reporting */
71 * If reporting is already active there is nothing we need to do. in __page_reporting_request()
86 /* notify prdev of free page reporting request */
141 * The page reporting cycle consists of 4 stages, fill, report, drain, and
167 * Limit how many calls we will be making to the page reporting in page_reporting_cycle()
174 * list processed. This should result in us reporting all pages on in page_reporting_cycle()
273 * to allocate page reporting statistics for the zone. in page_reporting_process_zone()
318 * anyone requests page reporting after we complete our pass. If in page_reporting_process()
320 * to idle and quit scheduling reporting runs. in page_reporting_process()
[all …]
|
| /openbmc/linux/drivers/rapidio/switches/ |
| H A D | idt_gen2.c | 229 * Configure LT LAYER error reporting. in idtg2_em_init()
232 /* Enable standard (RIO.p8) error reporting */ in idtg2_em_init()
237 /* Use Port-Writes for LT layer error reporting. in idtg2_em_init()
245 * Configure PORT error reporting. in idtg2_em_init()
251 /* Configure reporting of implementation specific errors/events */ in idtg2_em_init()
255 /* Use Port-Writes for port error reporting and enable error logging */ in idtg2_em_init()
269 * Configure LANE error reporting. in idtg2_em_init()
272 /* Disable line error reporting */ in idtg2_em_init()
275 /* Use Port-Writes for lane error reporting (when enabled) in idtg2_em_init()
286 * Configure AUX error reporting. in idtg2_em_init()
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | iommu.rst | 23 - RMRR - Intel Reserved Memory Region Reporting Structure
24 - IVRS - AMD I/O Virtualization Reporting Structure
42 Virtualization Reporting Structure (IVRS) that is used to convey information
69 If this fixes anything, please ensure you file a bug reporting the problem.
86 this fixes anything, please ensure you file a bug reporting the problem.
88 Fault reporting
125 Intel Fault reporting
145 AMD Fault reporting
|
| /openbmc/linux/drivers/input/misc/ |
| H A D | Kconfig | 21 reporting power button status.
31 reporting power button status.
81 Say Y to enable support for reporting power button status on
101 Support the ONKEY of ATC260x PMICs as an input device reporting
241 reporting power button status.
263 reporting power button status.
336 Say Y here if you want to enable power key reporting via the
466 Say Y here if you want to enable power key reporting via the
476 Say Y here if you want to enable power button reporting for
486 Say Y here if you want to enable power button reporting for
[all …]
|
| /openbmc/linux/drivers/pci/pcie/ |
| H A D | Kconfig | 10 support for Native Hot-Plug, Advanced Error Reporting, Power
29 bool "PCI Express Advanced Error Reporting support"
33 This enables PCI Express Root Port Advanced Error Reporting
34 (AER) driver support. Error reporting messages sent to Root
42 This enables PCI Express Root Port Advanced Error Reporting
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_fifo_underrun.c | 53 * reporting on all pipes.
306 * intel_set_cpu_fifo_underrun_reporting - set cpu fifo underrrun reporting state
316 * disables for all due to shared interrupts. Actual reporting is still per-pipe
319 * Returns the previous state of underrun reporting.
336 * intel_set_pch_fifo_underrun_reporting - set PCH fifo underrun reporting state
343 * underrun reporting for one transcoder may also disable all the other PCH
347 * Returns the previous state of underrun reporting.
391 * into dmesg if underrun reporting is enabled and then disables the underrun
449 * into dmesg if underrun reporting is enabled and then disables the underrun
523 * We track the PCH trancoder underrun reporting state in intel_init_fifo_underrun_reporting()
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | page_reporting.h | 19 /* Current state of page reporting */
22 /* Minimal order of page reporting */
26 /* Tear-down and bring-up for page reporting devices */
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-siox | 56 Read-only value reporting the inbytes value provided to siox-X/device_add
69 Read-only value reporting the type value provided to siox-X/device_add.
75 Read-only value reporting if the watchdog of the siox device is
83 Read-only value reporting the number to time intervals when the
90 Read-only value reporting the outbytes value provided to siox-X/device_add.
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | atarikbd.rst | 66 Relative Position Reporting
96 Absolute Position reporting
119 Joystick Event Reporting
150 time to reporting the state of the joystick ports at a user specifiable rate.
201 The ikbd defaults to a mouse position reporting with threshold of 1 unit in
203 reporting mode for joystick 1, with both buttons being logically assigned to
259 SET RELATIVE MOUSE POSITION REPORTING
266 Set relative mouse position reporting. (DEFAULT) Mouse position packets are
417 All mouse event reporting is disabled (and scanning may be internally
419 valid mouse mode commands are SET RELATIVE MOUSE POSITION REPORTING, SET
[all …]
|
| /openbmc/linux/arch/x86/kernel/cpu/mce/ |
| H A D | winchip.c | 3 * IDT Winchip specific Machine Check Exception Reporting
28 /* Set up machine check reporting on the Winchip C6 series */
40 pr_info("Winchip machine check reporting enabled on CPU#0.\n"); in winchip_mcheck_init()
|
| H A D | p5.c | 3 * P5 specific Machine Check Exception Reporting
44 /* Set up machine check reporting for processors with Intel style MCE: */
64 pr_info("Intel old style machine check reporting enabled on CPU#%d.\n", in intel_p5_mcheck_init()
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | input.yaml | 19 Specifies an array of numeric keycode values to be used for reporting
28 Specifies a single numeric keycode value to be used for reporting
30 reporting.
|
| /openbmc/openpower-hw-diags/analyzer/plugins/ |
| H A D | p10-tod-plugins.cpp | 57 * @param i_chipAtFault The chip reporting step check fault.
77 * @param i_chipAtFault The chip reporting a step check fault.
100 * @param i_chipAtFault The chip reporting the fault.
158 // Given the chip reporting the error and the IOHS position within that in getChipSourcingClock()
325 // - First, check if the MDMT chip is reporting a fault. If so, it is in tod_step_check_fault()
328 // - If MDMT is not reporting a fault, look for any network path errors in tod_step_check_fault()
330 // of the chips sourcing those step check errors (not the chips reporting in tod_step_check_fault()
332 // - If no other errors found, callout any chips reporting internal step in tod_step_check_fault()
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 7 File system Error Reporting
11 reporting. It is meant to be used by file system health monitoring
20 early file system problem detection and reporting recovery tools.
|
| H A D | reporting-issues.rst | 4 Reporting issues
56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For
70 document and reporting the issue to your vendor instead, unless you are
117 go and install it for the reporting process. Testing and reporting with
168 Reporting regressions within a stable and longterm kernel line
203 Reporting issues only occurring in older kernel version lines
234 Reference section: Reporting issues to the kernel maintainers
280 document and reporting the issue to your vendor instead, unless you are
294 Most of these vendor kernels are quite unsuitable for reporting issues to the
324 better than not reporting the issue at all: sometimes such reports directly or
[all …]
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | jack.rst | 21 code providing jack reporting mechanisms.
23 For example, a system may have a stereo headset jack with two reporting
63 Each jack may have multiple reporting mechanisms, though it will need at
|
| /openbmc/linux/drivers/thermal/intel/ |
| H A D | Kconfig | 86 tristate "Intel PCH Thermal Reporting Driver"
90 Enable this to support thermal reporting on certain intel PCHs.
91 Thermal reporting device will provide temperature reading,
|
| /openbmc/linux/drivers/hid/amd-sfh-hid/hid_descriptor/ |
| H A D | amd_sfh_hid_report_desc.h | 33 0x0A, 0x16, 0x03, /* HID usage sensor property reporting state */
200 0x0A, 0x16, 0x03, /* HID usage sensor property reporting state */
206 0x0A, 0x40, 0x08, /* Sensor reporting state no events sel */
207 0x0A, 0x41, 0x08, /* Sensor reporting state all events sel */
208 0x0A, 0x42, 0x08, /* Sensor reporting state threshold events sel */
209 0x0A, 0x43, 0x08, /* Sensor reporting state no events wake sel */
210 0x0A, 0x44, 0x08, /* Sensor reporting state all events wake sel */
211 0x0A, 0x45, 0x08, /* Sensor reporting state threshold events wake sel */
361 0x0A, 0x16, 0x03, /* HID usage sensor property reporting state */
367 0x0A, 0x40, 0x08, /* Sensor reporting state no events sel */
[all …]
|
| /openbmc/linux/arch/x86/events/ |
| H A D | Kconfig | 30 tristate "AMD Processor Power Reporting Mechanism"
32 Provide power reporting mechanism support for AMD processors.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeontx2.rst | 168 The NPA reporters are responsible for reporting and recovering the following group of errors:
182 - RAS Error Reporting for NPA_AQ_INST_S/NPA_AQ_RES_S.
225 The NIX reporters are responsible for reporting and recovering the following group of errors:
242 - RAS Error Reporting for NIX Receive Multicast/Mirror Entry Structure.
243 - RAS Error Reporting for WQE/Packet Data read from Multicast/Mirror Buffer..
244 - RAS Error Reporting for NIX_AQ_INST_S/NIX_AQ_RES_S.
|
| /openbmc/docs/designs/ |
| H A D | event-logging.md | 13 There is currently not a consistent end-to-end error and event reporting design
139 Application code reporting an error:
172 likely to become outdated over time as internal OpenBMC error reporting
185 Message Registry and the reporting application. It also requires every
187 and external management interfaces. This also leaves gaps for reporting errors
197 - The `sdbusplus` bindings for error reporting do not currently handle lossless
203 `phosphor-health-monitor`. One cause of this is two different error reporting
223 mechanics for push-reporting.
254 - APIs to implement error and event reporting should have good ergonomics. These
271 reporting; expand it to cover tracing events; improve the ergonomics of the
[all …]
|
| /openbmc/linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | index.rst | 39 reporting-issues
48 reporting-bugs
|