/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
D | v4l2.rst | 39 Revision and Copyright 50 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter. 54 - Original author of the V4L2 API and documentation. 63 - Original author of the V4L2 API and documentation. 76 - Designed and documented the multi-planar API. 84 - Introduce HSV formats and other minor changes. 88 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls. 96 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl… 101 part can be used and distributed without restrictions. 115 ctrl_class and which. Which is used to select the current value of the [all …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
/Linux-v5.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 …]
|
D | cleancache.rst | 19 that is not directly accessible or addressable by the kernel and is 20 of unknown and possibly time-varying size. 25 and a disk access is avoided. 28 in Xen (using hypervisor memory) and zcache (using in-kernel compressed 29 memory) and other implementations are in development. 43 by the kernel and so may or may not still be in cleancache at any later time. 45 Cleancache has complete discretion over what pages to preserve and what 46 pages to discard and when. 51 (presumably about-to-be-evicted) page into cleancache and associate it with 52 the pool id, a file key, and a page index into the file. (The combination [all …]
|
/Linux-v5.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 …]
|
/Linux-v5.10/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 …]
|
/Linux-v5.10/tools/memory-model/Documentation/ |
D | explanation.txt | 13 5. ORDERING AND CYCLES 15 7. THE PROGRAM ORDER RELATION: po AND po-loc 17 9. DEPENDENCY RELATIONS: data, addr, and ctrl 18 10. THE READS-FROM RELATION: rf, rfi, and rfe 19 11. CACHE COHERENCE AND THE COHERENCE ORDER RELATION: co, coi, and coe 20 12. THE FROM-READS RELATION: fr, fri, and fre 27 19. AND THEN THERE WAS ALPHA 30 22. RCU RELATIONS: rcu-link, rcu-gp, rcu-rscsi, rcu-order, rcu-fence, and rb 32 24. PLAIN ACCESSES AND DATA RACES 33 25. ODDS AND ENDS [all …]
|
/Linux-v5.10/Documentation/admin-guide/ |
D | cgroup-v2.rst | 8 This is the authoritative documentation on the design, interface and 10 of cgroup including core and specific controller behaviors. All 21 2-2. Organizing Processes and Threads 26 2-4-1. Enabling and Disabling 33 2-6-1. Organize Once and Control 73 6-2. The Root and Views 74 6-3. Migration and setns(2) 79 R. Issues with v1 and Rationales for v2 82 R-3. Competition Between Inner Nodes and Threads 84 R-5. Controller Issues and Remedies [all …]
|
D | perf-security.rst | 3 Perf events and tool security 12 direct usage of perf_events system call API [2]_ and over data files 15 units (PMU) [2]_ and Perf collect and expose for performance analysis. 16 Collected system and performance data may be split into several 19 1. System hardware and software configuration data, for example: a CPU 20 model and its cache configuration, an amount of available memory and 21 its topology, used kernel and Perf versions, performance monitoring 25 2. User and kernel module paths and their load addresses with sizes, 26 process and thread names with their PIDs and TIDs, timestamps for 27 captured hardware and software events. [all …]
|
/Linux-v5.10/Documentation/usb/ |
D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver. 35 and offering suggestions and sharing implementation experiences. 37 Additional thanks to the following companies and people for donations 38 of hardware, support, time and development (this is from the original 44 - 3Com GmbH for donating a ISDN Pro TA and supporting me 45 in technical questions and with test equipment. I'd never 52 Operating System and supports this project with 74 protocol. They've also donated a F-23 digital joystick and a 79 leading manufacturer for active and passive ISDN Controllers 80 and CAPI 2.0-based software. The active design of the AVM B1 [all …]
|
/Linux-v5.10/Documentation/x86/ |
D | intel_txt.rst | 15 - Measurement and verification of launched environment 17 Intel TXT is part of the vPro(TM) brand and is also available some 19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell 20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45, 21 PM45, and GS45 Express chipsets. 47 uses Intel TXT to perform a measured and verified launch of an OS 55 w/ TXT support since v3.2), and now Linux kernels. 61 While there are many products and technologies that attempt to 64 Measurement Architecture (IMA) and Linux Integrity Module interface 69 starting at system reset and requires measurement of all code [all …]
|
/Linux-v5.10/LICENSES/dual/ |
D | Apache-2.0 | 20 TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 24 "License" shall mean the terms and conditions for use, reproduction, and 30 "Legal Entity" shall mean the union of the acting entity and all other 43 and configuration files. 47 object code, generated documentation, and conversions to other media types. 55 that is based on (or derived from) the Work and for which the editorial 59 merely link (or bind by name) to the interfaces of, the Work and Derivative 63 version of the Work and any modifications or additions to that Work or 70 mailing lists, source code control systems, and issue tracking systems that 72 and improving the Work, but excluding communication that is conspicuously [all …]
|
/Linux-v5.10/Documentation/admin-guide/cifs/ |
D | todo.rst | 12 is a partial list of the known problems and missing features: 14 a) SMB3 (and SMB3.1.1) missing optional features: 18 - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl 21 b) improved sparse file support (fiemap and SEEK_HOLE are implemented 31 open/query/close and open/setinfo/close) to reduce the number of 32 roundtrips to the server and improve performance. Various cases 36 handle caching leases) and better using reference counters on file 39 f) Finish inotify support so kde and gnome file list windows 43 g) Add GUI tool to configure /proc/fs/cifs settings and for display of 46 h) implement support for security and trusted categories of xattrs [all …]
|