| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | other.json | 11 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 24 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 37 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 50 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 63 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 76 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 89 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 102 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 115 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 128 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … [all …]
|
| D | memory.json | 11 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 24 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 37 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 51 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 65 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 79 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 84 …"BriefDescription": "Counts L1 data cache hardware prefetch requests and software prefetch request… 92 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 106 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 120 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … [all …]
|
| D | cache.json | 12 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 26 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 40 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 54 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 78 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 92 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 118 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 132 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 166 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 180 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … [all …]
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | Kconfig | 4 # Licensed and distributed under the GPL 13 tristate "EDAC (Error Detection And Correction) reporting" 40 levels are 0-4 (from low to high) and by default it is set to 2. 68 It should be noticed that keeping both GHES and a hardware-driven 81 Support for error detection and correction of DRAM ECC errors on 88 Recent Opterons (Family 10h and later) provide for Memory Error 90 allows the operator/user to inject Uncorrectable and Correctable 100 In addition, there are two control files, inject_read and inject_write, 101 which trigger the DRAM ECC Read and Write respectively. 107 Support for error detection and correction for Amazon's Annapurna [all …]
|
| /kernel/linux/linux-6.6/drivers/pinctrl/intel/ |
| D | Kconfig | 11 platforms. Supports 3 banks with 102, 28 and 44 gpios. 18 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver" 22 allows configuring of SoC pins and using them as GPIOs. 25 tristate "Intel Lynxpoint pinctrl and GPIO driver" 29 provides an interface that allows configuring of PCH pins and 41 tristate "Intel Alder Lake pinctrl and GPIO driver" 45 of Intel Alder Lake PCH pins and using them as GPIOs. 48 tristate "Intel Broxton pinctrl and GPIO driver" 52 configuring of SoC pins and using them as GPIOs. 55 tristate "Intel Cannon Lake PCH pinctrl and GPIO driver" [all …]
|
| /kernel/linux/linux-6.6/drivers/edac/ |
| D | Kconfig | 4 # Licensed and distributed under the GPL 13 tristate "EDAC (Error Detection And Correction) reporting" 40 levels are 0-4 (from low to high) and by default it is set to 2. 69 It should be noticed that keeping both GHES and a hardware-driven 82 Support for error detection and correction of DRAM ECC errors on 88 AMD CPUs up to and excluding family 0x17 provide for Memory 90 module allows the operator/user to inject Uncorrectable and 100 In addition, there are two control files, inject_read and inject_write, 101 which trigger the DRAM ECC Read and Write respectively. 107 Support for error detection and correction for Amazon's Annapurna [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | memory.json | 3 …"BriefDescription": "Counts all demand & prefetch RFOs that miss the L3 and the data is returned f… 11 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 24 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 39 …"BriefDescription": "Counts all prefetch (that bring data to L2) RFOs that miss the L3 and the dat… 47 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 60 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 65 …"BriefDescription": "Counts all demand data writes (RFOs) that miss the L3 and the modified data i… 73 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 87 …"BriefDescription": "Counts all prefetch data reads that miss the L3 and the data is returned from… 95 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … [all …]
|
| D | cache.json | 3 …"BriefDescription": "Counts all demand code reads that hit in the L3 and sibling core snoops are n… 11 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 34 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 67 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 104 …efetch requests and software prefetch requests that hit in the L3 and the snoop to one of the sibl… 112 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 117 …nts demand data reads that hit in the L3 and the snoop to one of the sibling cores hits the line i… 125 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 138 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … 194 …ogrammed only with a specific pair of event select and counter MSR, and with specific event codes … [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/westmereep-dp/ |
| D | memory.json | 10 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = ANY_DRAM AND REMOTE_FWD", 19 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = ANY_LLC_MISS", 28 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = OTHER_LOCAL_DRAM", 37 "BriefDescription": "REQUEST = ANY_DATA read and RESPONSE = REMOTE_DRAM", 46 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = ANY_DRAM AND REMOTE_FWD", 55 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = ANY_LLC_MISS", 64 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = OTHER_LOCAL_DRAM", 73 "BriefDescription": "REQUEST = ANY IFETCH and RESPONSE = REMOTE_DRAM", 82 "BriefDescription": "REQUEST = ANY_REQUEST and RESPONSE = ANY_DRAM AND REMOTE_FWD", 91 "BriefDescription": "REQUEST = ANY_REQUEST and RESPONSE = ANY_LLC_MISS", [all …]
|
| /kernel/linux/linux-5.10/drivers/pinctrl/intel/ |
| D | Kconfig | 12 platforms. Supports 3 banks with 102, 28 and 44 gpios. 19 tristate "Intel Cherryview/Braswell pinctrl and GPIO driver" 24 allows configuring of SoC pins and using them as GPIOs. 27 tristate "Intel Lynxpoint pinctrl and GPIO driver" 36 provides an interface that allows configuring of PCH pins and 47 interface that allows configuring of SoC pins and using them as 59 tristate "Intel Broxton pinctrl and GPIO driver" 64 configuring of SoC pins and using them as GPIOs. 67 tristate "Intel Cannon Lake PCH pinctrl and GPIO driver" 72 of Intel Cannon Lake PCH pins and using them as GPIOs. [all …]
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision 10 features into the existing timer framework, and after testing various 14 to solve this'), and spent a considerable effort trying to integrate 18 - the forced handling of low-resolution and high-resolution timers in 19 the same way leads to a lot of compromises, macro magic and #ifdef 20 mess. The timers.c code is very "tightly coded" around jiffies and 21 32-bitness assumptions, and has been honed and micro-optimized for a 23 for many years - and thus even small extensions to it easily break 25 code is very good and tight code, there's zero problems with it in its 45 error conditions in various I/O paths, such as networking and block [all …]
|
| /kernel/linux/linux-6.6/Documentation/timers/ |
| D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision 10 features into the existing timer framework, and after testing various 14 to solve this'), and spent a considerable effort trying to integrate 18 - the forced handling of low-resolution and high-resolution timers in 19 the same way leads to a lot of compromises, macro magic and #ifdef 20 mess. The timers.c code is very "tightly coded" around jiffies and 21 32-bitness assumptions, and has been honed and micro-optimized for a 23 for many years - and thus even small extensions to it easily break 25 code is very good and tight code, there's zero problems with it in its 45 error conditions in various I/O paths, such as networking and block [all …]
|
| /kernel/linux/linux-6.6/LICENSES/dual/ |
| D | CC-BY-4.0 | 19 Creative Commons Corporation ("Creative Commons") is not a law firm and 22 other relationship. Creative Commons makes its licenses and related 25 terms and conditions, or any related information. Creative Commons 31 Creative Commons public licenses provide a standard set of terms and 32 conditions that creators and other rights holders may use to share 33 original works of authorship and other material subject to copyright 34 and certain other rights specified in the public license below. The 36 exhaustive, and do not form part of our licenses. 41 copyright and certain other rights. Our licenses are 42 irrevocable. Licensors should read and understand the terms [all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | hist-v4l2.rst | 12 and began to work on documentation, example drivers and applications. 15 another four years and two stable kernel releases until the new API was 28 meaningless ``O_TRUNC`` :c:func:`open()` flag, and the 29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set 32 identifiers are now ordinals instead of flags, and the 33 ``video_std_construct()`` helper function takes id and 40 struct ``video_standard`` and the color subcarrier fields were 53 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio 55 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and 59 module. The ``YUV422`` and ``YUV411`` planar image formats were added. [all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | hist-v4l2.rst | 12 and began to work on documentation, example drivers and applications. 15 another four years and two stable kernel releases until the new API was 28 meaningless ``O_TRUNC`` :c:func:`open()` flag, and the 29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set 32 identifiers are now ordinals instead of flags, and the 33 ``video_std_construct()`` helper function takes id and 40 struct ``video_standard`` and the color subcarrier fields were 53 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio 55 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and 59 module. The ``YUV422`` and ``YUV411`` planar image formats were added. [all …]
|
| /kernel/linux/linux-6.6/drivers/hwmon/ |
| D | Kconfig | 14 sensors and various additional features such as the ability to 16 should say Y here and also to the specific driver(s) for your 36 a problem with I2C support and want to see more of what is going 46 and second revision of the Abit uGuru chip. The voltage and frequency 49 Abit motherboards from before end 2005). For more info and a list 62 and their settings is supported. The third revision of the Abit 64 2005). For more info and a list of which motherboards have which 75 current and power sensors of Ampere's Altra processor family SoC 79 tristate "Analog Devices AD7314 and compatibles" 83 AD7314, ADT7301 and ADT7302 temperature sensors. [all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | af_xdp.rst | 13 This document assumes that the reader is familiar with BPF and XDP. If 24 syscall. Associated with each XSK are two rings: the RX ring and the 25 TX ring. A socket can receive packets on the RX ring and it can send 26 packets on the TX ring. These rings are registered and sized with the 27 setsockopts XDP_RX_RING and XDP_TX_RING, respectively. It is mandatory 30 UMEM. RX and TX can share the same UMEM so that a packet does not have 31 to be copied between RX and TX. Moreover, if a packet needs to be kept 33 to that packet can be changed to point to another and reused right 42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The 47 kernel has transmitted completely and can now be used again by user [all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | workqueue.rst | 14 is needed and the workqueue (wq) API is the most commonly used 20 queue is called workqueue and the thread is called worker. 32 worker thread per CPU and a single threaded (ST) wq had one worker 35 wq users over the years and with the number of CPU cores continuously 40 provided was unsatisfactory. The limitation was common to both ST and 47 The tension between the provided level of concurrency and resource 49 choosing to use ST wq for polling PIOs and accepting an unnecessary 64 * Automatically regulate worker pool and level of concurrency so that 77 item pointing to that function and queue that work item on a 86 subsystems and drivers queue work items on and the backend mechanism [all …]
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | ChangeLog.lpfc | 12 for fabric and nport logins out of lpfc_cmpl_els_flogi. 18 PRLI...) are errored back and scan() terminates. 28 find command in both TX and TX completion queues. Return ERROR 62 - kill struct lpfc_scsi_dma_buf and embedded the two members 67 ever used by the driver, just reported to userspace (and that in 72 32bit and 64bit defines on some archs. 82 * Revise TRANSPORT_PATCHES_V2 so that lpfc_target is removed and 84 * Changed RW attributes of scan_down, max_luns and fcp_bind_method 88 list and marked for ADISC. 102 * Use DMA_64BIT_MASK and DMA_32BIT_MASK defines instead of [all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ChangeLog.lpfc | 12 for fabric and nport logins out of lpfc_cmpl_els_flogi. 18 PRLI...) are errored back and scan() terminates. 28 find command in both TX and TX completion queues. Return ERROR 62 - kill struct lpfc_scsi_dma_buf and embedded the two members 67 ever used by the driver, just reported to userspace (and that in 72 32bit and 64bit defines on some archs. 82 * Revise TRANSPORT_PATCHES_V2 so that lpfc_target is removed and 84 * Changed RW attributes of scan_down, max_luns and fcp_bind_method 88 list and marked for ADISC. 102 * Use DMA_64BIT_MASK and DMA_32BIT_MASK defines instead of [all …]
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame 16 behaviours differ in subtle (and not so subtle) ways. This document describes 24 Device and driver capabilities are reported in the fixed screen information 34 expect from the device and driver. 43 2. Types and visuals 50 Formats are described by frame buffer types and visuals. Some visuals require 52 bits_per_pixel, grayscale, red, green, blue and transp fields. 54 Visuals describe how color information is encoded and assembled to create 56 types and visuals are supported. 64 Padding at end of lines may be present and is then reported through the fixed [all …]
|
| /kernel/linux/linux-6.6/Documentation/fb/ |
| D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame 16 behaviours differ in subtle (and not so subtle) ways. This document describes 24 Device and driver capabilities are reported in the fixed screen information 34 expect from the device and driver. 43 2. Types and visuals 50 Formats are described by frame buffer types and visuals. Some visuals require 52 bits_per_pixel, grayscale, red, green, blue and transp fields. 54 Visuals describe how color information is encoded and assembled to create 56 types and visuals are supported. 64 Padding at end of lines may be present and is then reported through the fixed [all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | frontswap.rst | 11 (Note, frontswap -- and :ref:`cleancache` (merged at 3.0) -- are the "frontends" 12 and the only necessary changes to the core kernel for transcendent memory; 15 for a detailed overview of frontswap and related kernel parts) 25 kernel and is of unknown and possibly time-varying size. The driver 27 frontswap_ops funcs appropriately and the functions it provides must 32 copy the page to transcendent memory and associate it with the type and 36 from transcendent memory and an "invalidate_area" will remove ALL pages 37 associated with the swap type (e.g., like swapoff) and notify the "device" 43 success, the data has been successfully saved to transcendent memory and 44 a disk write and, if the data is later read back, a disk read are avoided. [all …]
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| D | Kconfig | 14 sensors and various additional features such as the ability to 16 should say Y here and also to the specific driver(s) for your 36 a problem with I2C support and want to see more of what is going 48 AB8500 die and two GPADC channels. The GPADC channel are preferably 59 and second revision of the Abit uGuru chip. The voltage and frequency 62 Abit motherboards from before end 2005). For more info and a list 75 and their settings is supported. The third revision of the Abit 77 2005). For more info and a list of which motherboards have which 84 tristate "Analog Devices AD7314 and compatibles" 88 AD7314, ADT7301 and ADT7302 temperature sensors. [all …]
|
| /kernel/linux/linux-6.6/LICENSES/deprecated/ |
| D | GPL-1.0 | 18 Everyone is permitted to copy and distribute verbatim copies 25 License is intended to guarantee your freedom to share and change free 28 software and to any other program whose authors commit to using it. 36 programs; and that you know you can do these things. 46 source code. And you must tell them their rights. 48 We protect your rights with two steps: (1) copyright the software, and 50 distribute and/or modify the software. 52 Also, for each author's protection and ours, we want to make certain 54 software. If the software is modified by someone else and passed on, we 59 The precise terms and conditions for copying, distribution and [all …]
|