| /linux/Documentation/dev-tools/ |
| H A D | kasan.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 --------
11 designed to find out-of-bounds and use-after-free bugs.
16 2. Software Tag-Based KASAN
17 3. Hardware Tag-Based KASAN
23 Software Tag-Based KASAN or SW_TAGS KASAN, enabled with CONFIG_KASAN_SW_TAGS,
26 using it for testing on memory-restricted devices with real workloads.
28 Hardware Tag-Based KASAN or HW_TAGS KASAN, enabled with CONFIG_KASAN_HW_TAGS,
29 is the mode intended to be used as an in-field memory bug detector or as a
37 The Generic and the Software Tag-Based modes are commonly referred to as the
[all …]
|
| /linux/drivers/pci/controller/dwc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 menu "DesignWare-based PCIe controllers"
38 core plus Annapurna Labs proprietary hardware wrappers. This is
39 required only for DT-based platforms. ACPI platforms with the
49 Versal2 SoCs. The AMD MDB Versal2 PCIe controller is based on
50 DesignWare IP and therefore the driver re-uses the DesignWare
60 SoCs. The PCI controller on Amlogic is based on DesignWare hardware
61 and therefore the driver re-uses the DesignWare core functions to
68 bool "Axis ARTPEC-6 PCIe controller (host mode)"
74 Enables support for the PCIe controller in the ARTPEC-6 SoC to work in
[all …]
|
| /linux/lib/ |
| H A D | Kconfig.kasan | 1 # SPDX-License-Identifier: GPL-2.0-only
32 compile-time constants for better performance.
35 def_bool $(cc-option, -fsanitize=kernel-address)
38 def_bool $(cc-option, -fsanitize=kernel-hwaddress)
55 Enables KASAN (Kernel Address Sanitizer) - a dynamic memory safety
56 error detector designed to find out-of-bounds and use-after-free bugs.
58 See Documentation/dev-tools/kasan.rst for details.
65 …def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=kernel-address -mllvm -asan-kernel-mem-intrinsic-p…
66 (CC_IS_GCC && $(cc-option,-fsanitize=kernel-address --param asan-kernel-mem-intrinsic-prefix=1))
81 2. Software Tag-Based KASAN (arm64 only, based on software memory
[all …]
|
| /linux/drivers/hid/intel-thc-hid/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
13 is comprised of 3 key functional blocks: A natively half-duplex
15 HIDI2C compliant devices; a hardware sequencer with Read/Write DMA
21 tristate "Intel QuickSPI driver based on Intel Touch Host Controller"
24 Intel QuickSPI, based on Touch Host Controller (THC), implements
26 mode, and controls THC hardware sequencer to accelerate HIDSPI
32 tristate "Intel QuickI2C driver based on Intel Touch Host Controller"
35 Intel QuickI2C, uses Touch Host Controller (THC) hardware, implements
37 mode, and controls THC hardware sequencer to accelerate HIDI2C
|
| /linux/drivers/media/usb/cx231xx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
12 This is a video4linux driver for Conexant 231xx USB based TV cards.
24 cx231xx hardware has a builtin RX/TX support. However, a few
25 designs opted to not use it, but, instead, some other hardware.
26 This module enables the usage of those other hardware, like the
27 ones used with ISDB-T boards.
37 This is an ALSA driver for Cx231xx USB based TV cards.
40 module will be called cx231xx-alsa
43 tristate "DVB/ATSC Support for Cx231xx based TV cards"
58 This adds support for DVB cards based on the
|
| /linux/Documentation/arch/arm/ |
| H A D | interrupts.rst | 5 2.5.2-rmk5:
7 major architecture-specific subsystems.
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
33 exclusive of each other - if you're processing one interrupt from the
36 IDE PIO-based interrupt on the SA1111 excludes all other SA1111 and
37 SMC9196 interrupts until it has finished transferring its multi-sector
51 GPIO0-10, and another for all the rest. It is just a container for
[all …]
|
| /linux/Documentation/networking/ |
| H A D | multiqueue.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 ---------------------------------------------------------
22 netdev->queue_lock today. Therefore base drivers should use the
24 device is still operational. netdev->queue_lock is still used when the device
32 default pfifo_fast qdisc. This qdisc supports one qdisc per hardware queue.
33 A new round-robin qdisc, sch_multiq also supports multiple hardware queues. The
35 bands and queues based on the value in skb->queue_mapping. Use this field in
38 sch_multiq has been added for hardware that wishes to avoid head-of-line
39 blocking. It will cycle though the bands and verify that the hardware queue
42 On qdisc load, the number of bands is based on the number of queues on the
[all …]
|
| H A D | tc-queue-filters.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 TC queue based filtering
15 the queue-sets are configured using mqprio.
27 hw_tc $TCID - Specify a hardware traffic class to pass matching
32 is supported only in hardware. Multiple filters may compete in
33 the hardware for queue selection. In such case, the hardware
34 pipeline resolves conflicts based on priority. On Intel E810
|
| H A D | scaling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
|
| /linux/mm/kasan/ |
| H A D | hw_tags.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * This file contains core hardware tag-based KASAN code.
88 return -EINVAL; in early_kasan_flag()
95 return -EINVAL; in early_kasan_flag()
105 return -EINVAL; in early_kasan_mode()
114 return -EINVAL; in early_kasan_mode()
124 return -EINVAL; in early_kasan_flag_vmalloc()
134 return -EINVAL; in early_kasan_flag_vmalloc()
144 return -EINVAL; in early_kasan_flag_write_only()
151 return -EINVAL; in early_kasan_flag_write_only()
[all …]
|
| H A D | report_hw_tags.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * This file contains hardware tag-based KASAN specific error reporting code.
21 * Hardware Tag-Based KASAN only calls this function for normal memory in kasan_find_first_bad_addr()
43 * calculate the allocation size based on the metadata. in kasan_get_alloc_size()
45 while (size < cache->object_size) { in kasan_get_alloc_size()
54 return cache->object_size; in kasan_get_alloc_size()
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | cpufreq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
36 cases, there are hardware interfaces allowing CPUs to be switched between
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
63 Scaling drivers talk to the hardware. They provide scaling governors with
64 information on the available P-states (or P-state ranges in some cases) and
[all …]
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-eswitch-attr.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Devlink E-Switch Attribute
7 Devlink E-Switch supports two modes of operation: legacy and switchdev.
8 Legacy mode operates based on traditional MAC/VLAN steering rules. Switching
9 decisions are made based on MAC addresses, VLANs, etc. There is limited ability
10 to offload switching rules to hardware.
13 capabilities of the E-Switch to hardware. In switchdev mode, more switching
14 rules and logic can be offloaded to the hardware switch ASIC. It enables
16 or scalable-functions (SFs) of the device. See more information about
20 In addition, the devlink E-Switch also comes with other attributes listed
[all …]
|
| H A D | devlink-dpipe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 While performing the hardware offloading process, much of the hardware
12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
16 Linux kernel may differ from the hardware implementation. The pipeline debug
20 The hardware offload process is expected to be done in a way that the user
21 should not be able to distinguish between the hardware vs. software
22 implementation. In this process, hardware specifics are neglected. In
28 differences in the hardware and software models some processes cannot be
32 greatly to the hardware implementation. The configuration API is the same,
34 Level Path Compression trie (LPC-trie) in hardware.
[all …]
|
| /linux/block/ |
| H A D | blk-mq-cpumap.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * CPU <-> hardware queue mapping helpers
5 * Copyright (C) 2013-2014 Jens Axboe
18 #include "blk-mq.h"
30 * blk_mq_num_possible_queues - Calc nr of queues for multiqueue devices
31 * @max_queues: The maximum number of queues the hardware/driver
36 * device based on the number of possible CPUs.
45 * blk_mq_num_online_queues - Calc nr of queues for multiqueue devices
46 * @max_queues: The maximum number of queues the hardware/driver
51 * device based on the number of online CPUs.
[all …]
|
| /linux/Documentation/edac/ |
| H A D | scrub.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.2-no-invariants-or-later
7 Copyright (c) 2024-2025 HiSilicon Limited.
11 Invariant Sections, Front-Cover Texts nor Back-Cover Texts.
14 - Written for: 6.15
17 ------------
22 hardware failures that cause server and workload crashes.
24 Memory scrubbing is a feature where an ECC (Error-Correcting Code) engine
38 3. This reduces the likelihood of software or hardware products encountering
49 2. On-demand scrubbing for a specific address range or region of memory.
51 Several types of interfaces to hardware memory scrubbers have been
[all …]
|
| /linux/Documentation/timers/ |
| H A D | highres.rst | 8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
41 - independent of ticks (the processing is based on nanoseconds)
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | mtdnand.rst | 10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
40 not replaceable and provide functionality which is complete hardware
43 - [NAND Interface]
48 - [GENERIC]
51 is complete hardware independent.
53 - [DEFAULT]
55 Default functions provide hardware related functionality which is
65 -------------------------------
[all …]
|
| H A D | libata.rst | 12 transports for ATA and ATAPI devices, and SCSI<->ATA translation for ATA
16 internals, and a couple sample ATA low-level drivers.
22 is defined for every low-level libata
23 hardware driver, and it controls how the low-level driver interfaces
26 FIS-based drivers will hook into the system with ``->qc_prep()`` and
27 ``->qc_issue()`` high-level hooks. Hardware which behaves in a manner
28 similar to PCI IDE hardware may utilize several generic helpers,
33 ----------------------------------------------------------
35 Post-IDENTIFY device configuration
44 Typically used to apply device-specific fixups prior to issue of SET
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-ptp | 7 features of PTP hardware clocks.
14 hardware clock registered into the PTP class driver
21 This file contains the name of the PTP hardware clock
24 name" and to help distinguish PHY based devices from
25 MAC based ones. The string does not necessarily have
32 This file contains the PTP hardware clock's maximum
41 Write integer to re-configure it.
48 alarms offer by the PTP hardware clock.
55 channels offered by the PTP hardware clock.
62 output channels offered by the PTP hardware clock.
[all …]
|
| /linux/sound/pci/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 device found in particular on the Hewlett-Packard [BCJ]-xxx0
19 class PA-RISC workstations, using the AD1819 codec.
22 will be called snd-ad1889.
34 will be called snd-als300
45 Say Y here to include support for soundcards based on Avance Logic
49 will be called snd-als4000.
63 will be called snd-ali5451.
75 will be called snd-asihpi.
86 will be called snd-atiixp.
[all …]
|
| /linux/Documentation/fb/ |
| H A D | api.rst | 9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
36 - FB_CAP_FOURCC
38 The driver supports the four character code (FOURCC) based format setting API.
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
48 frame buffer memory in the format expected by the hardware.
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
[all …]
|
| /linux/Documentation/block/ |
| H A D | inline-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 Inline encryption hardware sits logically between memory and disk, and can
14 can control exactly how the inline encryption hardware will en/decrypt the data
18 Some inline encryption hardware accepts all encryption parameters including raw
19 keys directly in low-level I/O requests. However, most inline encryption
20 hardware instead has a fixed number of "keyslots" and requires that the key,
22 low-level I/O request then just contains a keyslot index and data unit number.
24 Note that inline encryption hardware is very different from traditional crypto
27 hardware operates on I/O requests. Thus, inline encryption hardware needs to be
30 Inline encryption hardware is also very different from "self-encrypting drives",
[all …]
|
| /linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 - the NVMe Base specification
21 - various Command Set specifications (e.g. NVM Command Set)
22 - various Transport specifications (e.g. PCIe, Fibre Channel, RDMA, TCP)
23 - the NVMe Management Interface specification
32 useful or suitable for specific use-cases. It is important to note that Linux
44 on-wire protocol, does not contradict any of the NVMe specifications.
47 3. Has a clear, indisputable value-proposition and a wide consensus across
63 of the standards. Linux uses identifier-based quirks to work around such
65 hardware, usually consumer, which Linux users can't use without these quirks.
[all …]
|
| /linux/Documentation/networking/device_drivers/ethernet/cirrus/ |
| H A D | cs89x0.rst | 1 .. SPDX-License-Identifier: GPL-2.0
33 2.1 CS8900-based Adapter Configuration
34 2.2 CS8920-based Adapter Configuration
46 5.2.1 Diagnostic Self-Test
66 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
67 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
69 in 16-bit ISA or EISA bus expansion slots and are available in
70 10BaseT-only or 3-media configurations (10BaseT, 10Base2, and AUI for 10Base-5
73 CS8920-based adapters are similar to the CS8900-based adapter with additional
85 or loaded at run-time as a device driver module.
[all …]
|