/openbmc/linux/scripts/coccinelle/api/ |
H A D | kvmalloc.cocci | 12 virtual report 234 @script: python depends on report@ 238 coccilib.report.print_report(p[0], "WARNING opportunity for kvmalloc") 246 @script: python depends on report@ 250 coccilib.report.print_report(p[0], "WARNING opportunity for kvfree")
|
/openbmc/openbmc-test-automation/lib/ |
H A D | gen_arg.py | 390 report = "\n" 395 report += gp.sprint_issuing(cmd_buf) 397 report += outbuf + "\n" 399 return report
|
H A D | gen_call_robot.py | 69 report = "NONE" 73 report = file_prefix + "report.html" 82 gm.set_mod_global(report) 91 report,
|
/openbmc/linux/tools/memory-model/scripts/ |
H A D | README | 100 The checkghlitmus.sh should not report errors in cases where the 101 checklitmushist.sh script did not also report a change. However, 108 new version. In this case, checklitmushist.sh will report a mismatch 109 and checkghlitmus.sh will report success. This happens when the change
|
/openbmc/docs/ |
H A D | SECURITY.md | 3 ## How to report a security vulnerability 5 This describes how you can report an OpenBMC security vulnerability privately to 50 version of OpenBMC), please report it and we will help you route it to the
|
/openbmc/linux/arch/s390/pci/ |
H A D | pci_sysfs.c | 140 struct zpci_report_error_header *report = (void *) buf; in report_error_write() local 146 if (off || (count < sizeof(*report))) in report_error_write() 149 ret = sclp_pci_report(report, zdev->fh, zdev->fid); in report_error_write()
|
/openbmc/openbmc/poky/ |
H A D | SECURITY.md | 4 If you would like to report a public issue (for example, one with a released 5 CVE number), please report it using the
|
/openbmc/linux/tools/testing/selftests/kvm/x86_64/ |
H A D | vmx_tsc_adjust_test.c | 114 static void report(int64_t val) in report() function 144 report(uc.args[1]); in main()
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | perf-report.txt | 1 perf-report(1) 6 perf-report - Read perf.data (created by perf record) and display the profile 11 'perf report' [-i <file> | --input=file] 205 field(s) to the default field order. For example: perf report -F +period,sample. 346 --cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can 348 CPUs are specified with -: 0-2. Default is to report samples on all 375 perf report is able to auto-detect whether a perf.data file contains 458 perf report --time 10%/2 462 perf report --time 0%-10% 466 perf report --time 10%/1,10%/2 [all …]
|
H A D | perf-lock.txt | 11 'perf lock' {record|report|script|info|contention} 23 'perf lock report' reports statistical data. 40 Output file name for perf lock contention and report. 87 $ perf lock report -t -F acquired,contended,avg_wait
|
/openbmc/linux/drivers/net/wireless/realtek/rtlwifi/rtl8192de/ |
H A D | trx.c | 64 u8 report, cck_highpwr; in _rtl92de_query_rxphystatus() local 74 report = cck_buf->cck_agc_rpt & 0xc0; in _rtl92de_query_rxphystatus() 75 report = report >> 6; in _rtl92de_query_rxphystatus() 76 switch (report) { in _rtl92de_query_rxphystatus() 92 report = p_drvinfo->cfosho[0] & 0x60; in _rtl92de_query_rxphystatus() 93 report = report >> 5; in _rtl92de_query_rxphystatus() 94 switch (report) { in _rtl92de_query_rxphystatus()
|
/openbmc/linux/tools/testing/selftests/powerpc/pmu/ |
H A D | count_instructions.c | 30 u64 overhead, bool report) in do_count_loop() argument 49 if (report) { in do_count_loop()
|
/openbmc/openbmc/poky/bitbake/ |
H A D | SECURITY.md | 4 If you would like to report a public issue (for example, one with a released 5 CVE number), please report it using the
|
/openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-security/bastille/files/ |
H A D | edit_usage_message.patch | 30 "$spc --assess : check status of system and report in browser\n". 31 "$spc --assessnobrowser : check status of system and list report locations\n".
|
/openbmc/linux/Documentation/input/ |
H A D | event-codes.rst | 270 Upon binding to a device or resuming from suspend, a driver must report 288 - Used to report the number of microseconds since the last reset. This event 397 accelerometer data. Some devices also report gyroscope data, which devices 398 can report through the rotational axes (absolute and/or relative rx, ry, rz). 413 REL_{X,Y} must be reported when the mouse moves. BTN_LEFT must be used to report 414 the primary button press. BTN_{MIDDLE,RIGHT,4,5,etc.} should be used to report 415 further buttons of the device. REL_WHEEL and REL_HWHEEL should be used to report 422 used to report when a touch is active on the screen. 431 Legacy trackpads that only provide relative position information must report 434 Trackpads that provide absolute touch position must report ABS_{X,Y} for the [all …]
|
/openbmc/openpower-pnor-code-mgmt/ |
H A D | activation.cpp | 228 report<InternalFailure>(); in rebootHost() 254 report<InternalFailure>(); in validateSignature() 265 report<InternalFailure>(); in validateSignature()
|
/openbmc/linux/drivers/hid/ |
H A D | hid-elo.c | 80 static int elo_raw_event(struct hid_device *hdev, struct hid_report *report, in elo_raw_event() argument 90 switch (report->id) { in elo_raw_event() 99 hid_info(hdev, "unknown report type %d\n", report->id); in elo_raw_event()
|
/openbmc/linux/tools/perf/ |
H A D | builtin-kwork.c | 166 if (kwork->report == KWORK_REPORT_LATENCY) in sort_dimension__add() 1108 if (kwork->report == KWORK_REPORT_RUNTIME) { in report_print_work() 1112 } else if (kwork->report == KWORK_REPORT_LATENCY) { // avg delay in report_print_work() 1127 if (kwork->report == KWORK_REPORT_RUNTIME) { in report_print_work() 1143 else if (kwork->report == KWORK_REPORT_LATENCY) { in report_print_work() 1170 if (kwork->report == KWORK_REPORT_RUNTIME) { in report_print_header() 1173 } else if (kwork->report == KWORK_REPORT_LATENCY) { in report_print_header() 1180 if (kwork->report == KWORK_REPORT_RUNTIME) { in report_print_header() 1185 } else if (kwork->report == KWORK_REPORT_LATENCY) { in report_print_header() 1344 switch (kwork->report) { in perf_kwork__check_config() [all …]
|
/openbmc/linux/Documentation/trace/ |
H A D | tracepoint-analysis.rst | 109 Similarly, one could execute a shell and exit it as desired to get a report 202 on-line, it can be interrupted once to generate a report without exiting 240 perf report. 243 $ perf report 260 # (For more details, try: perf report --sort comm,dso,symbol) 278 $ perf report 289 # (For more details, try: perf report --sort comm,dso,symbol) 296 $ perf report --sort comm,dso,symbol
|
/openbmc/linux/mm/kmsan/ |
H A D | core.c | 424 goto report; in kmsan_metadata_is_contiguous() 433 goto report; in kmsan_metadata_is_contiguous() 440 goto report; in kmsan_metadata_is_contiguous() 444 report: in kmsan_metadata_is_contiguous()
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | iosm.rst | 108 * - ``report.json`` 128 $ devlink region new pci/0000:02:00.0/report.json 130 $ devlink region dump pci/0000:02:00.0/report.json snapshot 0 132 $ devlink region del pci/0000:02:00.0/report.json snapshot 0
|
/openbmc/phosphor-dbus-monitor/src/ |
H A D | elog.hpp | 78 phosphor::logging::report<T>(std::forward<Args>(args)...); in op() 168 phosphor::logging::report<errorType>(metadataType(data.c_str())); in operator ()()
|
/openbmc/linux/drivers/vfio/ |
H A D | vfio_main.c | 1109 struct vfio_device_feature_dma_logging_report report; in vfio_ioctl_device_feature_logging_report() local 1119 sizeof(report)); in vfio_ioctl_device_feature_logging_report() 1123 if (copy_from_user(&report, arg, minsz)) in vfio_ioctl_device_feature_logging_report() 1126 if (report.page_size < SZ_4K || !is_power_of_2(report.page_size)) in vfio_ioctl_device_feature_logging_report() 1129 if (check_add_overflow(report.iova, report.length, &iova_end) || in vfio_ioctl_device_feature_logging_report() 1133 iter = iova_bitmap_alloc(report.iova, report.length, in vfio_ioctl_device_feature_logging_report() 1134 report.page_size, in vfio_ioctl_device_feature_logging_report() 1135 u64_to_user_ptr(report.bitmap)); in vfio_ioctl_device_feature_logging_report()
|
/openbmc/linux/Documentation/dev-tools/ |
H A D | kasan.rst | 101 When it is enabled, KASAN panics the kernel after printing a bug report. 103 By default, KASAN prints a bug report only for the first invalid memory access. 104 With ``kasan_multi_shot``, KASAN prints a report on every invalid access. This 110 - ``kasan.fault=report``, ``=panic``, or ``=panic_on_write`` controls whether 111 to only print a KASAN report, panic the kernel, or panic the kernel on 112 invalid writes only (default: ``report``). The panic happens even if 166 A typical KASAN report looks like this:: 239 The report header summarizes what kind of bug happened and what kind of access 243 bug report). Next comes a description of the accessed slab object and the 246 In the end, the report shows the memory state around the accessed address. [all …]
|
/openbmc/witherspoon-pfault-analysis/power-supply/ |
H A D | power_supply.cpp | 343 report<PowerSupplyInputFault>( in checkInputFault() 391 report<PowerSupplyShouldBeOn>( in checkPGOrUnitOffFault() 430 report<PowerSupplyOutputOvercurrent>( in checkCurrentOutOverCurrentFault() 471 report<PowerSupplyOutputOvervoltage>( in checkOutputOvervoltageFault() 510 report<PowerSupplyFanFault>( in checkFanFault() 565 report<PowerSupplyTemperatureFault>( in checkTemperatureFault()
|