/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
H A D | uncore-interconnect.json | 28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 706 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 864 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 873 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 883 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 893 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 903 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 913 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 923 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
|
/linux/Documentation/rust/ |
H A D | quick-start.rst | 33 Arch Linux provides recent Rust releases and thus it should generally work out 43 recent Rust releases and thus they should generally work out of the box, e.g.:: 51 Fedora Linux provides recent Rust releases and thus it should generally work out 61 and thus it should generally work out of the box, e.g.:: 72 generally work out of the box, e.g.:: 85 they should generally work out of the box, e.g.::
|
/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
H A D | uncore-interconnect.json | 686 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 844 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 853 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 863 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 873 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 883 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 893 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 903 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 913 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 923 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
|
/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
H A D | uncore-interconnect.json | 686 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 843 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 852 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 862 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 872 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 882 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 892 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 902 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 912 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 922 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
|
/linux/Documentation/power/ |
H A D | suspend-and-interrupts.rst | 12 Device interrupt request lines (IRQs) are generally disabled during system 61 System wakeup interrupts generally need to be configured to wake up the system 72 After wakeup, it generally is better to disable that input to prevent the 128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally
|
H A D | freezing-of-tasks.rst | 38 tasks are generally frozen before kernel threads. 115 Generally speaking, there is a couple of reasons to use the freezing of tasks: 134 devices are deactivated, because we generally need them for swapping out. 217 tasks, since it generally exists anyway.
|
/linux/Documentation/devicetree/bindings/memory-controllers/ddr/ |
H A D | jedec,lpddr-props.yaml | 10 Different LPDDR types generally use the same properties and only differ in the 12 reused for each type. Nodes using this schema should generally be nested under
|
/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
H A D | uncore-interconnect.json | 28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 425 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 523 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 692 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 701 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 710 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 719 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 728 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 737 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … [all …]
|
/linux/Documentation/i2c/busses/ |
H A D | i2c-ali15x3.rst | 61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't 121 SMBus. Therefore the SMBus hangs can generally be avoided
|
/linux/Documentation/mm/ |
H A D | active_mm.rst | 80 should generally just do 85 we have a user context", and is generally done by the page fault handler
|
/linux/Documentation/admin-guide/pm/ |
H A D | intel_pstate.rst | 81 names of some of those governors. Moreover, confusingly enough, they generally 182 registers of the CPU. It generally selects P-states proportional to the 266 In turn, the P-states below the turbo threshold generally are sustainable. In 273 but the maximum P-state that can be set for them generally depends on the number 291 generally causes turbo P-states to be set more often when ``intel_pstate`` is 320 Generally, ways to obtain that information are specific to the processor model 455 as the current scaling driver and it generally depends on the driver's 707 diagnostics. One of them is the ``cpu_frequency`` trace event generally used 713 their output (if the kernel is generally configured to support event tracing)::
|
H A D | cpufreq.rst | 42 the utilization of the system generally changes over time, that has to be done 160 scheduler tick or generally whenever the CPU utilization may change (from the 215 and their behavior generally does not depend on what scaling driver is in use 392 generally is regarded as a part of the CPU scheduler, so it can access the 434 This governor generally is regarded as a replacement for the older `ondemand`_ 464 It generally selects CPU frequencies proportional to the estimated load, so that 648 The frequency boost mechanism is generally intended to help to achieve optimum 659 conditions. Generally, the processor's energy consumption increases
|
/linux/Documentation/userspace-api/media/drivers/ |
H A D | camera-sensor.rst | 32 Register list based drivers generally, instead of able to configure the device 83 level interface natively, generally use the concept of frame interval (or frame
|
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
H A D | uncore-interconnect.json | 2690 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2723 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2756 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2767 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2800 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2833 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2932 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2965 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2998 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 3009 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
|
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
H A D | uncore-interconnect.json | 2690 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2723 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2756 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2767 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2800 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2833 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2932 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2965 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2998 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 3009 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
|
/linux/tools/perf/pmu-events/arch/x86/skylakex/ |
H A D | uncore-io.json | 13 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 29 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 516 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 528 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 540 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 552 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 602 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 614 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 626 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… [all …]
|
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
H A D | uncore-io.json | 13 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 29 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 516 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 528 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 540 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 552 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 602 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 614 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 626 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… [all …]
|
/linux/Documentation/process/ |
H A D | volatile-considered-harmful.rst | 71 waiting is generally an anti-social act to begin with. 104 Patches to remove volatile variables are generally welcome - as long as
|
/linux/kernel/power/ |
H A D | Kconfig | 213 Hardware support is generally required for this functionality to work 318 Generally, if you don't have a battery in your machine, there isn't 336 Per-cpu workqueues are generally preferred because they show
|
/linux/drivers/thermal/ti-soc-thermal/ |
H A D | TODO | 9 generally:
|
/linux/Documentation/driver-api/pm/ |
H A D | devices.rst | 57 However, devices are not generally independent of each other (for 200 by the bus type (or generally subsystem) code using :c:func:`pm_runtime_allow()` 401 vectors, like PCI, generally need it; otherwise a driver might encounter 432 generally means undoing the actions of the ``suspend_noirq`` phase. If 445 of the resume methods. This generally involves undoing the actions of 449 state, so that it can perform normal I/O. This generally involves 654 been thawed. Generally speaking, the PM notifiers are suitable for performing 698 cases it generally is not possible to put devices into low-power states 820 the case generally depends on the state of the device before the given system 842 ``DPM_FLAG_MAY_SKIP_RESUME`` flag is necessary, but generally not sufficient,
|
/linux/arch/x86/include/uapi/asm/ |
H A D | posix_types_64.h | 6 * This file is generally used by user-level software, so you need to
|
/linux/arch/powerpc/include/uapi/asm/ |
H A D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
/linux/arch/alpha/include/uapi/asm/ |
H A D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|
/linux/arch/parisc/include/uapi/asm/ |
H A D | posix_types.h | 6 * This file is generally used by user-level software, so you need to
|