| /linux-6.1.9/Documentation/translations/zh_CN/virt/acrn/ |
| D | io-request.rst | 16 I/O请求处理
19 客户虚拟机的I/O请求由超级管理器构建，由ACRN超级管理器服务模块分发到与I/O请求的地址范
20 围相对应的I/O客户端。I/O请求处理的细节将在以下章节描述。
22 1. I/O请求
26 I/O请求通信。一个I/O请求是一个256字节的结构体缓冲区，它是 "acrn_io_request" 结构
27 体，当客户虚拟机中发生被困的I/O访问时，由超级管理器的I/O处理器填充。服务虚拟机中的
29 台。缓冲区被用作16个I/O请求槽的数组，每个I/O请求槽为256字节。这个数组是按vCPU ID
32 2. I/O客户端
35 一个I/O客户端负责处理客户虚拟机的I/O请求，其访问的GPA在一定范围内。每个客户虚拟机
36 可以关联多个I/O客户端。每个客户虚拟机都有一个特殊的客户端，称为默认客户端，负责处理
[all …]
|
| /linux-6.1.9/drivers/comedi/drivers/tests/ |
| D | ni_routes_test.c | 27 #define O(x) ((x) + NI_NAMES_BASE) macro
47 static const int bad_dest = O(8), dest0 = O(0), desti = O(5);
49 static const int no_val_dest = O(7), no_val_index = 4;
52 #define rgout0_src0 (O(100))
53 #define rgout0_src1 (O(101))
54 #define brd0_src0 (O(110))
55 #define brd0_src1 (O(111))
56 #define brd1_src0 (O(120))
57 #define brd1_src1 (O(121))
58 #define brd2_src0 (O(130))
[all …]
|
| /linux-6.1.9/Documentation/virt/acrn/ |
| D | io-request.rst | 3 I/O request handling
6 An I/O request of a User VM, which is constructed by the hypervisor, is
7 distributed by the ACRN Hypervisor Service Module to an I/O client
8 corresponding to the address range of the I/O request. Details of I/O request
11 1. I/O request
14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
15 communication between the hypervisor and Service VM. An I/O request is a
17 an I/O handler of the hypervisor when a trapped I/O access happens in a User
20 used as an array of 16 I/O request slots with each I/O request slot being 256
23 2. I/O clients
[all …]
|
| /linux-6.1.9/Documentation/hwmon/ |
| D | it87.rst | 10 Addresses scanned: from Super I/O config space (8 I/O ports)
18 Addresses scanned: from Super I/O config space (8 I/O ports)
24 Addresses scanned: from Super I/O config space (8 I/O ports)
32 Addresses scanned: from Super I/O config space (8 I/O ports)
40 Addresses scanned: from Super I/O config space (8 I/O ports)
48 Addresses scanned: from Super I/O config space (8 I/O ports)
56 Addresses scanned: from Super I/O config space (8 I/O ports)
64 Addresses scanned: from Super I/O config space (8 I/O ports)
72 Addresses scanned: from Super I/O config space (8 I/O ports)
80 Addresses scanned: from Super I/O config space (8 I/O ports)
[all …]
|
| D | w83627hf.rst | 7 Addresses scanned: ISA address retrieved from Super I/O registers
10 Addresses scanned: ISA address retrieved from Super I/O registers
13 Addresses scanned: ISA address retrieved from Super I/O registers
16 Addresses scanned: ISA address retrieved from Super I/O registers
19 Addresses scanned: ISA address retrieved from Super I/O registers
42 the Winbond W83627HF, W83627THF, W83697HF and W83637HF Super I/O chips.
47 Super I/O chip and a second i2c-only Winbond chip (often a W83782D),
51 If you really want i2c accesses for these Super I/O chips,
72 be used to force the base I/O address of the hardware monitoring block.
78 # Enter the Super I/O config space::
[all …]
|
| D | f71882fg.rst | 10 Addresses scanned: none, address read from Super I/O config space
18 Addresses scanned: none, address read from Super I/O config space
26 Addresses scanned: none, address read from Super I/O config space
34 Addresses scanned: none, address read from Super I/O config space
42 Addresses scanned: none, address read from Super I/O config space
50 Addresses scanned: none, address read from Super I/O config space
58 Addresses scanned: none, address read from Super I/O config space
66 Addresses scanned: none, address read from Super I/O config space
74 Addresses scanned: none, address read from Super I/O config space
82 Addresses scanned: none, address read from Super I/O config space
[all …]
|
| /linux-6.1.9/Documentation/admin-guide/device-mapper/ |
| D | dm-io.rst | 5 Dm-io provides synchronous and asynchronous I/O services. There are three
6 types of I/O services available, and each type has a sync and an async
10 of the I/O. Each io_region indicates a block-device along with the starting
22 The first I/O service type takes a list of memory pages as the data buffer for
23 the I/O, along with an offset into the first page::
37 The second I/O service type takes an array of bio vectors as the data buffer
38 for the I/O. This service can be handy if the caller has a pre-assembled bio,
48 The third I/O service type takes a pointer to a vmalloc'd memory buffer as the
49 data buffer for the I/O. This service can be handy if the caller needs to do
50 I/O to a large region but doesn't want to allocate a large number of individual
[all …]
|
| /linux-6.1.9/Documentation/s390/ |
| D | cds.rst | 6 Device Driver I/O Support Routines
19 I/O access method. This gives relief to the device drivers as they don't
22 I/O (PIO), and other hardware features more. However, this implies that
23 either every single device driver needs to implement the hardware I/O
32 In order to build common device support for ESA/390 I/O interfaces, a
33 functional layer was introduced that provides generic I/O access methods to
36 The common device support layer comprises the I/O support routines defined
67 initiate an I/O request.
73 terminate the current I/O request processed on the device.
77 routine whenever an I/O interrupt is presented to the system. The do_IRQ()
[all …]
|
| D | vfio-ccw.rst | 8 Here we describe the vfio support for I/O subchannel devices for
13 I/O access method, which is so called Channel I/O. It has its own access
23 vfio framework. And we add read/write callbacks for special vfio I/O
25 (the real I/O subchannel device) to do further address translation and
26 to perform I/O instructions.
28 This document does not intend to explain the s390 I/O architecture in
31 - A good start to know Channel I/O in general:
32 https://en.wikipedia.org/wiki/Channel_I/O
47 paravirtualized virtio devices via the "Virtio Over Channel I/O
52 use the standard Channel I/O based mechanism, we also need to provide
[all …]
|
| /linux-6.1.9/Documentation/driver-api/ |
| D | s390-drivers.rst | 11 drive s390 based channel attached I/O devices. This includes interfaces
14 I/O layer.
17 with the s390 channel I/O architecture. For a description of this
21 While most I/O devices on a s390 system are typically driven through the
22 channel I/O mechanism described here, there are various other methods
25 The s390 common I/O layer also provides access to some devices that are
26 not strictly considered I/O devices. They are considered here as well,
38 * Standard I/O subchannels, for use by the system. They have a child
40 * I/O subchannels bound to the vfio-ccw driver. See
53 so-called channel attached devices. They are addressed via I/O
[all …]
|
| D | io_ordering.rst | 2 Ordering I/O writes to memory-mapped addresses
5 On some platforms, so-called memory-mapped I/O is weakly ordered. On such
6 platforms, driver writers are responsible for ensuring that I/O writes to
8 typically done by reading a 'safe' device or bridge register, causing the I/O
12 subsequent writes to I/O space arrived only after all prior writes (much like a
13 memory barrier op, mb(), only with respect to I/O).
49 Here, the reads from safe_register will cause the I/O chipset to flush any
|
| /linux-6.1.9/Documentation/block/ |
| D | stat.rst | 30 read merges requests number of read I/Os merged with in-queue I/O
34 write merges requests number of write I/Os merged with in-queue I/O
41 discard merges requests number of discard I/Os merged with in-queue I/O
51 These values increment when an I/O request completes.
56 These values increment when an flush I/O request completes.
64 These values increment when an I/O request is merged with an
65 already-queued I/O request.
73 block size. The counters are incremented when the I/O completes.
78 These values count the number of milliseconds that I/O requests have
79 waited on this block device. If there are multiple I/O requests waiting,
[all …]
|
| /linux-6.1.9/Documentation/translations/zh_CN/sound/hd-audio/ |
| D | controls.rst | 21 制多I/O插孔的插孔重分配。
53 输入“和”线路输入“以确定输入偏置,或者当引脚是环绕声道的多I/O插孔时，它
61 一个枚举控件，用于为环绕输出重新分配多个I/O插孔的任务。当它打开时，相应
98 被使用的通道数:”2ch“、”4ch“和”6ch“。根据配置，这还控制多I/O插孔的插孔重
|
| /linux-6.1.9/arch/powerpc/boot/ |
| D | README | 4 objcopy -j .kernel:vmlinux -O binary zImage vmlinux.gz
5 objcopy -j .kernel:System.map -O binary zImage System.map.gz
6 objcopy -j .kernel:.config -O binary zImage config.gz
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
|
| /linux-6.1.9/tools/scripts/ |
| D | Makefile.include | 2 ifneq ($(O),)
4 dummy := $(if $(shell cd $(PWD); test -d $(O) || echo $(O)),$(error O=$(O) does not exist),)
5 ABSOLUTE_O := $(shell cd $(PWD); cd $(O) ; pwd)
7 COMMAND_O := O=$(ABSOLUTE_O)
9 objtree := $(O)
|
| /linux-6.1.9/Documentation/features/scripts/ |
| D | features-refresh.sh | 13 O=""
16 O="not"
82 if [ "$O" = "" ] && [ ! -z "$K_GREP" ]; then
84 elif [ "$O" = "not" ] && [ -z "$K_GREP" ]; then
|
| /linux-6.1.9/Documentation/translations/zh_CN/mm/ |
| D | frontswap.rst | 105 忽略不计 - 因为每次frontswap失败都是在交换页写到磁盘之前，系统很可能是 I/O 绑定
150 结构，但这将需要相当大的改变。即使它被重写，现有的交换子系统也使用了块I/O层，它
152 及现有的交换子系统，而是围绕着块I/O子系统的限制，提供了大量的灵活性和动态性。
160 块I/O。块I/O层不仅是不必要的，而且可能进行 “优化”，这对面向RAM的设备来说是
162 态性，并避免棘手的竞争条件，这将不必要地大大增加frontswap和/或块I/O子系统的
|
| /linux-6.1.9/Documentation/userspace-api/media/v4l/ |
| D | io.rst | 13 The classic I/O method using the :c:func:`read()` and
18 Other methods must be negotiated. To select the streaming I/O method
22 Video overlay can be considered another I/O method, although the
27 Generally exactly one I/O method, including overlay, is associated with
35 degree, but for simplicity drivers need not support switching the I/O
39 The following sections describe the various I/O methods in more detail.
|
| /linux-6.1.9/tools/perf/Documentation/ |
| D | perf-iostat.txt | 6 perf-iostat - Show I/O performance metrics
16 Mode is intended to provide four I/O performance metrics per each PCIe root port:
18 - Inbound Read - I/O devices below root port read from the host memory, in MB
20 - Inbound Write - I/O devices below root port write to the host memory, in MB
22 - Outbound Read - CPU reads from I/O devices below root port, in MB
24 - Outbound Write - CPU writes to I/O devices below root port, in MB
|
| /linux-6.1.9/block/ |
| D | Kconfig.iosched | 5 tristate "MQ deadline I/O scheduler"
11 tristate "Kyber I/O scheduler"
14 The Kyber I/O scheduler is a low-overhead scheduler suitable for
20 tristate "BFQ I/O scheduler"
23 BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
|
| /linux-6.1.9/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 1 * Parallel I/O Ports
3 This node configures Parallel I/O ports for CPUs with QE support.
5 device that using parallel I/O ports, a child node should be created.
12 - num-ports : number of Parallel I/O ports
26 the new device trees. Instead, each Par I/O bank should be represented
|
| /linux-6.1.9/Documentation/translations/zh_CN/PCI/ |
| D | sysfs-pci.rst | 75 .. [1] rw 仅适用于 IORESOURCE_IO（I/O 端口）区域
80 检查任何尝试的mmap的返回值。其中最值得注意的是I/O端口资源，它也提供读/写访问。
98 如果底层平台支持的话，传统的I/O端口和ISA内存资源也会在sysfs中提供。它们位于PCI类的层次结构
107 legacy_io文件是一个读/写文件，可以被应用程序用来做传统的端口I/O。应用程序应该打开该文件，寻
123 评估为非零。支持I/O资源映射的平台同样定义arch_can_pci_mmap_io()。
|
| /linux-6.1.9/tools/testing/selftests/bpf/ |
| D | test_bpftool_build.sh | 104 make_with_tmpdir tools/bpf O
117 make_with_tmpdir -C tools/bpf/bpftool O
142 make_with_tmpdir bpf O
151 make_with_tmpdir O
|
| /linux-6.1.9/drivers/iio/buffer/ |
| D | Kconfig | 3 # Industrial I/O generic buffer implementations
14 tristate "Industrial I/O DMA buffer infrastructure"
23 tristate "Industrial I/O DMA buffer integration with DMAEngine"
34 tristate "Industrial I/O HW buffering"
44 tristate "Industrial I/O buffering based on kfifo"
51 tristate "Industrial I/O triggered buffer support"
|
| /linux-6.1.9/Documentation/translations/zh_CN/admin-guide/ |
| D | tainted-kernels.rst | 33 CPU: 0 PID: 4424 Comm: insmod Tainted: P W O 4.20.0-0.rc6.fc30 #1
41 Tainted: P W O
44 警告（ ``W`` ），并且加载了外部构建的模块（ ``O`` ），所以内核早些时候受到
67 Raw taint value as int/string: 4609/'P W O '
95 12 _/O 4096 已加载外部构建（“树外”）模块
146 12) ``O`` 已加载外部构建（“树外”）模块。
|