/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."
|
/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."
|
/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 …
|
/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
|
/linux/arch/arm64/boot/dts/qcom/ |
H A D | msm8916-samsung-j3-common.dtsi | 44 /* GPIO pins vary depending on model variant */ 48 /* GPIO pins vary depending on model variant */
|
/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
|
/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()
|
/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
|
/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
|
/linux/arch/m68k/hp300/ |
H A D | README.hp300 | 10 combination seems to work for me. Your mileage may vary.
|
/linux/Documentation/devicetree/bindings/input/ |
H A D | e3x0-button.txt | 15 Note: Interrupt numbers might vary depending on the FPGA configuration.
|
/linux/include/linux/spi/ |
H A D | ad7877.h | 4 /* Touchscreen characteristics vary between boards and models. The
|
/linux/drivers/gpu/drm/amd/display/dc/ |
H A D | dm_pp_smu.h | 128 * FCLK will vary with DPM, but never below requested hard min 188 * UCLK will vary with DPM, but never below requested hard min
|
/linux/arch/powerpc/tools/ |
H A D | gcc-check-fpatchable-function-entry.sh | 10 # Output from -fpatchable-function-entry can only vary on ppc64 elfv2, so this
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | arm,nvic.txt | 5 vary in the number of interrupts and priority bits per interrupt.
|
/linux/usr/ |
H A D | initramfs_data.S | 17 The above example is for i386 - the parameters vary from architectures.
|
/linux/Documentation/scsi/ |
H A D | sym53c500_cs.rst | 27 for Tom Corner, and it works for me. Your mileage will probably vary.
|
/linux/Documentation/devicetree/bindings/mtd/partitions/ |
H A D | redboot-fis.yaml | 13 This block size will vary depending on flash but is typically
|
/linux/Documentation/devicetree/bindings/hwmon/ |
H A D | amd,sbrmi.yaml | 31 socket 0 and 70h for socket 1, but it could vary based on hardware
|
H A D | amd,sbtsi.yaml | 32 0 and 90h for socket 1, but it could vary based on hardware address
|
/linux/drivers/net/phy/ |
H A D | open_alliance_helpers.h | 31 * bits may vary, but generally:
|
/linux/Documentation/devicetree/bindings/net/wireless/ |
H A D | qcom,ath10k.yaml | 99 can vary between hardware versions. 110 Pre-calibration data as a byte array. The length can vary between
|