Generally (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:generally (Results 1 – 25 of 1610) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...65

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivytown/
D	uncore-interconnect.json	25 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 34 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 622 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 764 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 772 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 781 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 790 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 799 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 808 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 817 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/kernel/linux/linux-5.10/Documentation/driver-api/media/
D	camera-sensor.rst	`15 divisors. The clock tree is generally configured by the driver based on a few 17 and the link frequency. The two parameters generally are obtained from system 45 Register list based drivers generally, instead of able to configure the device 95 level interface natively, generally use the concept of frame interval (or frame`
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/haswellx/
D	uncore-interconnect.json	615 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 757 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 765 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 774 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 783 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 792 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 801 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 810 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 819 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 828 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/broadwellx/
D	uncore-interconnect.json	615 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 756 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 764 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 773 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 782 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 791 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 800 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 809 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 818 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 827 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/
D	uncore-other.json	578 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 590 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 602 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 614 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 626 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 638 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 650 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 662 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… 866 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… 878 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… [all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/
D	uncore-other.json	557 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 569 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 581 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 593 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 605 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 617 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 629 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 641 …de to the MMIO space of a card on IIO Part3 by a unit on the main die (generally a core) or by an… 845 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… 857 …for up to a 64 byte transaction of data made by a unit on the main die (generally a core) or by an… [all …]
/kernel/linux/linux-5.10/Documentation/power/
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`
D	freezing-of-tasks.rst	`36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally 104 Generally speaking, there is a couple of reasons to use the freezing of tasks: 123 devices are deactivated, because we generally need them for swapping out. 206 tasks, since it generally exists anyway.`
/kernel/linux/linux-6.6/Documentation/driver-api/media/
D	camera-sensor.rst	`15 divisors. The clock tree is generally configured by the driver based on a few 17 and the link frequency. The two parameters generally are obtained from system 64 Register list based drivers generally, instead of able to configure the device 115 level interface natively, generally use the concept of frame interval (or frame`
/kernel/linux/linux-6.6/Documentation/power/
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`
D	freezing-of-tasks.rst	`36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally 104 Generally speaking, there is a couple of reasons to use the freezing of tasks: 123 devices are deactivated, because we generally need them for swapping out. 206 tasks, since it generally exists anyway.`
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/memory-controllers/ddr/
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`
/kernel/linux/linux-5.10/Documentation/core-api/
D	bus-virt-phys-mapping.rst	`48 not generally necessarily true on other PCI/ISA setups. 125 And you generally never want to use the physical address, because you can't 143 memory" on the PCI or ISA bus. That's generally not RAM (although in the case 213 It's generally not hard to fix drivers, and in many cases the code`
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-interconnect.json	25 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 34 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 379 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 467 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 619 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 627 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 635 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 643 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 651 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 659 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	uncore-interconnect.json	2181 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2208 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2235 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2244 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2271 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2298 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2379 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2406 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2433 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 2442 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
/kernel/linux/linux-5.10/Documentation/vm/
D	active_mm.rst	`76 should generally just do 81 we have a user context", and is generally done by the page fault handler`
/kernel/linux/linux-5.10/Documentation/i2c/busses/
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`
/kernel/linux/linux-6.6/Documentation/mm/
D	active_mm.rst	`80 should generally just do 85 we have a user context", and is generally done by the page fault handler`
/kernel/linux/linux-6.6/Documentation/i2c/busses/
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`
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
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 388 generally is regarded as a part of the CPU scheduler, so it can access the 430 This governor generally is regarded as a replacement for the older `ondemand`_ 460 It generally selects CPU frequencies proportional to the estimated load, so that 644 The frequency boost mechanism is generally intended to help to achieve optimum 655 conditions. Generally, the processor's energy consumption increases
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 449 and it generally depends on the driver's `operation mode <Operation Modes_>`_. 700 diagnostics. One of them is the ``cpu_frequency`` trace event generally used 706 their output (if the kernel is generally configured to support event tracing)::
/kernel/linux/linux-6.6/Documentation/admin-guide/pm/
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 388 generally is regarded as a part of the CPU scheduler, so it can access the 430 This governor generally is regarded as a replacement for the older `ondemand`_ 460 It generally selects CPU frequencies proportional to the estimated load, so that 644 The frequency boost mechanism is generally intended to help to achieve optimum 655 conditions. Generally, the processor's energy consumption increases
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)::
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/cascadelakex/
D	uncore-io.json	12 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 27 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 446 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 457 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 468 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 479 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 512 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 523 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 534 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 545 …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 …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/skylakex/
D	uncore-io.json	12 …equest for 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 27 …request of 4 bytes of data made by IIO Part0 to a unit on the main die (generally memory). In the … 446 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 457 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 468 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 479 … every read request for 4 bytes of data made by a unit on the main die (generally a core) or by an… 512 …ade to the MMIO space of a card on IIO Part0 by a unit on the main die (generally a core) or by an… 523 …ade to the MMIO space of a card on IIO Part1 by a unit on the main die (generally a core) or by an… 534 …de to the MMIO space of a card on IIO Part2 by a unit on the main die (generally a core) or by an… 545 …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 …]

12 3 4 5 6 7 8 9 10 >>...65