/openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen1/ |
H A D | floating-point.json | 81 …floating-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8.", 88 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Divide… 95 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Multip… 102 …ng-point Ops that have retired. The number of events logged per cycle can vary from 0 to 8. Add/su… 109 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 116 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 123 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 130 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 137 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 144 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … [all …]
|
H A D | core.json | 11 … interrupts, microcode assists, etc.). The number of events logged per cycle can vary from 0 to 4." 123 …branch instructions retired per cycle. The number of events logged per cycle can vary from 0 to 3."
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen2/ |
H A D | floating-point.json | 40 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 46 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 53 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 59 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 65 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This …
|
H A D | core.json | 11 … interrupts, microcode assists, etc.). The number of events logged per cycle can vary from 0 to 8." 128 …se-branch instructions retired per cycle. The number of events logged per cycle can vary from 0-8."
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
H A D | floating-point.json | 40 …umber of retired SSE/AVX FLOPS. The number of events logged per cycle can vary from 0 to 64. This … 46 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This … 52 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This … 58 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This … 64 …umber of retired SSE/AVX FLOPs. The number of events logged per cycle can vary from 0 to 64. This …
|
/openbmc/linux/Documentation/devicetree/bindings/phy/ |
H A D | qcom,qusb2-phy.yaml | 90 tuning parameter that may vary for different boards of same SOC. 99 tuning parameter that may vary for different boards of same SOC. 108 tuning parameter that may vary for different boards of same SOC. 149 threshold and may vary for different boards of same SOC.
|
/openbmc/linux/Documentation/driver-api/firmware/ |
H A D | introduction.rst | 6 for functionality from userspace, the uses vary: 22 Which one you use vary depending on your requirements, the rule of thumb
|
/openbmc/linux/drivers/usb/misc/ |
H A D | usbtest.c | 33 __u32 vary; member 50 __u32 vary; member 458 int vary, in simple_io() argument 493 if (vary) { in simple_io() 496 len += vary; in simple_io() 499 len = (vary < max) ? vary : max; in simple_io() 536 alloc_sglist(int nents, int max, int vary, struct usbtest_dev *dev, int pipe) in alloc_sglist() argument 577 if (vary) { in alloc_sglist() 578 size += vary; in alloc_sglist() 581 size = (vary < max) ? vary : max; in alloc_sglist() [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Manifest.v1_1_2.json | 96 …describe the request details of a stanza within a manifest. Its contents vary depending on the va… 117 …escribe the response details of a stanza within a manifest. Its contents vary depending on the va… 173 …operty shall contain the request details for the stanza, and the contents vary depending on the va… 185 …perty shall contain the response details for the stanza, and the contents vary depending on the va…
|
/openbmc/linux/drivers/i3c/master/mipi-i3c-hci/ |
H A D | xfer_mode_rate.h | 20 * Presence and definitions for indexes beyond these ones may vary. 45 * rates may vary slightly and are also specified in the Data Transfer
|
/openbmc/qemu/include/hw/intc/ |
H A D | arm_gic.h | 35 * + sysbus IRQs: (in order; number will vary depending on number of cores) 50 * + sysbus MMIO regions: (in order; numbers will vary depending on
|
/openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
H A D | firmware_state_notyetstarted_unittest.cpp | 26 * There are the following calls (parameters may vary): 28 * session parameter are valid. Once you open() from this state, we will vary
|
/openbmc/linux/tools/usb/ |
H A D | testusb.c | 47 unsigned vary; member 395 param.vary = 1024; in main() 436 case 'v': /* vary packet size by ... */ in main() 437 if (parse_num(¶m.vary, optarg)) in main() 457 "\t-v vary default 1024\n", in main()
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Manifest_v1.xml | 96 …operty shall contain the request details for the stanza, and the contents vary depending on the va… 100 …perty shall contain the response details for the stanza, and the contents vary depending on the va… 142 …describe the request details of a stanza within a manifest. Its contents vary depending on the va… 148 …escribe the response details of a stanza within a manifest. Its contents vary depending on the va…
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-platform-dell-smbios | 19 Tokens will vary from machine to machine, and
|
H A D | sysfs-bus-iio-magnetometer-hmc5843 | 18 The effect of this configuration may vary
|
/openbmc/linux/arch/m68k/hp300/ |
H A D | README.hp300 | 10 combination seems to work for me. Your mileage may vary.
|
/openbmc/openbmc/poky/bitbake/lib/toaster/tests/builds/ |
H A D | README | 9 $ cd bitbake/lib/toaster/ # path my vary but this is into toaster's directory
|
/openbmc/linux/drivers/net/wireless/ath/ath9k/ |
H A D | common-spectral.h | 59 /* WARNING: don't actually use this struct! MAC may vary the amount of 88 /* WARNING: don't actually use this struct! MAC may vary the amount of
|
/openbmc/linux/Documentation/devicetree/bindings/input/ |
H A D | e3x0-button.txt | 15 Note: Interrupt numbers might vary depending on the FPGA configuration.
|
/openbmc/qemu/target/alpha/ |
H A D | cpu-param.h | 18 * Allow user-only to vary page size. Real hardware allows only 8k and 64k,
|
/openbmc/qemu/target/arm/ |
H A D | cpu-param.h | 27 /* Allow user-only to vary page size from 4k */
|
/openbmc/qemu/target/ppc/ |
H A D | cpu-param.h | 36 /* Allow user-only to vary page size from 4k */
|
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/xtrans/ |
H A D | multilibfix.patch | 2 which can vary depending on which multilib is configured. The .pc file does
|
/openbmc/linux/include/linux/spi/ |
H A D | ad7877.h | 4 /* Touchscreen characteristics vary between boards and models. The
|