| /linux/Documentation/translations/zh_CN/virt/acrn/ |
| A 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在一定范围内。每个客户虚拟机 39 下面的图示显示了I/O请求共享缓冲区、I/O请求和I/O客户端之间的关系。 [all …]
|
| /linux/drivers/comedi/drivers/tests/ |
| A D | ni_routes_test.c | 47 static const int bad_dest = O(8), dest0 = O(0), desti = O(5); 80 O(x1), O(x2), O(x3), O(x4), O(x5), O(x6), O(x7), O(x8), O(x9), \ 313 unittest(ni_route_to_register(O(0), O(0), T) < 0, in test_ni_route_to_register() 402 unittest(!route_is_valid(O(0), O(0), T), in test_route_is_valid() 404 unittest(route_is_valid(O(0), O(1), T), in test_route_is_valid() 406 unittest(route_is_valid(O(5), O(6), T), in test_route_is_valid() 408 unittest(route_is_valid(O(8), O(9), T), in test_route_is_valid() 565 unittest(ni_get_reg_value(O(0), O(0), T) == -1, in test_ni_get_reg_value() 567 unittest(ni_get_reg_value(O(0), O(1), T) == 0, in test_ni_get_reg_value() 569 unittest(ni_get_reg_value(O(5), O(6), T) == 5, in test_ni_get_reg_value() [all …]
|
| /linux/Documentation/virt/acrn/ |
| A D | io-request.rst | 3 I/O request handling 8 corresponding to the address range of the I/O request. Details of I/O request 11 1. I/O request 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 26 An I/O client is responsible for handling User VM I/O requests whose accessed 34 I/O requests and I/O clients. 67 3. I/O request state transition 84 4. Processing flow of I/O requests [all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A 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, 49 data buffer for the I/O. This service can be handy if the caller needs to do 59 callback routine and a pointer to some context data for the I/O:: 65 In the case of an write-I/O to multiple regions, this bitset allows dm-io to [all …]
|
| A D | dm-flakey.rst | 40 unreliability, all I/O returns errors. 43 All read I/O is failed with an error signalled. 44 Write I/O is handled correctly. 47 All write I/O is silently ignored. 48 Read I/O is handled correctly. 51 All write I/O is failed with an error signalled. 52 Read I/O is handled correctly.
|
| /linux/Documentation/hwmon/ |
| A 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 …]
|
| A 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, 78 # Enter the Super I/O config space:: 87 # Set the base I/O address (to 0x290 in this example):: [all …]
|
| A 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/Documentation/arch/s390/ |
| A D | cds.rst | 6 Device Driver I/O Support Routines 67 initiate an I/O request. 120 they are presenting I/O completion a unified way : I/O interruptions. Every 193 ccw_device_start() - Initiate I/O Request 232 cdev ccw_device the I/O is destined for 237 particular I/O request. 306 interrupt will be presented to indicate I/O completion as the I/O request was 381 next it can reduce I/O processing overhead by chaining a NoOp I/O command 448 ccw_device_halt() - Halt I/O Request Processing 466 the I/O request is returned [all …]
|
| A D | vfio-ccw.rst | 13 I/O access method, which is so called Channel I/O. It has its own access 26 to perform I/O instructions. 31 - A good start to know Channel I/O in general: 32 https://en.wikipedia.org/wiki/Channel_I/O 72 way: I/O interruptions. 92 and starts the I/O with issuing a privileged Channel I/O instruction 95 - I/O completion will be signaled to the host with I/O interruptions. 190 vfio-ccw I/O region 213 irb_area stores the I/O result. 395 the I/O region. [all …]
|
| /linux/Documentation/driver-api/ |
| A 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 …]
|
| A 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/Documentation/block/ |
| A D | stat.rst | 30 read merges requests number of read 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 87 This value counts the number of I/O requests that have been issued to 88 the device driver but have not yet completed. It does not include I/O 95 had I/O requests queued. [all …]
|
| /linux/tools/power/cpupower/ |
| A D | Makefile | 12 OUTPUT := $(O)/ 330 @echo ' to "O" cmdline option dir (default: current dir)' 332 @echo ' dir defined by "O" cmdline option (default: current dir)' 336 @echo ' dir defined by "O" cmdline option (default: current dir)' 340 @echo ' dir defined by "O" cmdline option (default: current dir) and' 348 @echo ' dir defined by "O" cmdline option (default: current dir)' 352 @echo ' output dir defined by "O" cmdline option (default: current dir)' 357 @echo ' clean - Clean build artifacts from the dir defined by "O" cmdline'
|
| A D | README | 69 There are 2 make's command-line variables 'O' and 'DESTDIR' that setup 71 'O' - build directory 78 $ make O=<your_custom_build_catalog> 81 $ make O=/home/hedin/prj/cpupower/build 86 $ make O=<your_custom_build_catalog> DESTDIR=<your_custom_install_catalog> 89 $ make O=/home/hedin/prj/cpupower/build DESTDIR=/home/hedin/prj/cpupower \ 92 Notice that both variables 'O' and 'DESTDIR' have been provided. The reason 93 is that the build results are saved in the custom output dir defined by 'O' 136 Use 'O' command line variable to remove previously built files from the 138 $ make O=<your_custom_build_catalog> clean [all …]
|
| /linux/Documentation/translations/zh_CN/sound/hd-audio/ |
| A D | controls.rst | 21 制多I/O插孔的插孔重分配。 53 输入“和”线路输入“以确定输入偏置,或者当引脚是环绕声道的多I/O插孔时,它 61 一个枚举控件,用于为环绕输出重新分配多个I/O插孔的任务。当它打开时,相应 98 被使用的通道数:”2ch“、”4ch“和”6ch“。根据配置,这还控制多I/O插孔的插孔重
|
| /linux/arch/powerpc/boot/ |
| A 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/tools/scripts/ |
| A D | Makefile.include | 2 ifneq ($(O),) 4 $(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/Documentation/features/scripts/ |
| A 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/Documentation/userspace-api/media/v4l/ |
| A 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/tools/testing/selftests/hid/ |
| A D | vmtest.sh | 45 If you build your kernel using KBUILD_OUTPUT= or O= options, these 48 O=<kernel_build_path> $0 -- ./tools/testing/selftests/hid/hid_bpf 253 if is_rel_path "${O}"; then 254 O="$(realpath "${PWD}/${O}")" 256 kernel_bzimage="${O}/${BZIMAGE}" 257 make_command="${make_command} O=${O}"
|
| /linux/tools/perf/Documentation/ |
| A 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/block/ |
| A 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/Documentation/translations/zh_CN/PCI/ |
| A 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/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| A 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
|