/openbmc/linux/Documentation/translations/zh_CN/virt/acrn/ |
H 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在一定范围内。每个客户虚拟机 36 可以关联多个I/O客户端。每个客户虚拟机都有一个特殊的客户端,称为默认客户端,负责处理 [all …]
|
/openbmc/linux/drivers/comedi/drivers/tests/ |
H A 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 …]
|
/openbmc/linux/Documentation/virt/acrn/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/lmbench/lmbench/ |
H A D | 0002-build-Adjust-CFLAGS-LDFLAGS-to-append-values-passed-.patch | 35 @@ -112,8 +112,8 @@ LIBOBJS= $O/lib_tcp.o $O/lib_udp.o $O/lib_unix.o $O/lib_timing.o \ 36 $O/lib_sched.o 39 - @env CFLAGS=-O MAKE="$(MAKE)" MAKEFLAGS="$(MAKEFLAGS)" CC="$(CC)" OS="$(OS)" ../scripts/build all 40 - -@env CFLAGS=-O MAKE="$(MAKE)" MAKEFLAGS="k$(MAKEFLAGS)" CC="$(CC)" OS="$(OS)" ../scripts/build o… 41 + @env CFLAGS+=-O MAKE="$(MAKE)" MAKEFLAGS="$(MAKEFLAGS)" CC="$(CC)" OS="$(OS)" ../scripts/build all 42 + -@env CFLAGS+=-O MAKE="$(MAKE)" MAKEFLAGS="k$(MAKEFLAGS)" CC="$(CC)" OS="$(OS)" ../scripts/build … 50 - @env CFLAGS=-O MAKE="$(MAKE)" MAKEFLAGS="$(MAKEFLAGS)" CC="${CC}" OS="${OS}" ../scripts/build in… 51 + @env CFLAGS+=-O MAKE="$(MAKE)" MAKEFLAGS="$(MAKEFLAGS)" CC="${CC}" OS="${OS}" ../scripts/build i… 55 @@ -155,16 +155,16 @@ all: $(EXES) $O/lmbench 63 - @env CFLAGS="-g -O -Wall" MAKE="$(MAKE)" MAKEFLAGS="$(MAKEFLAGS)" CC="${CC}" OS="${OS}" ../script… [all …]
|
H A D | obey-ranlib.patch | 28 @@ -217,7 +218,7 @@ $O/lmbench : ../scripts/lmbench version.h 29 $O/lmbench.a: $(LIBOBJS) 30 /bin/rm -f $O/lmbench.a 31 $(AR) $(ARCREATE) $O/lmbench.a $(LIBOBJS) 32 - -ranlib $O/lmbench.a 33 + -$(RANLIB) $O/lmbench.a 35 $O/lib_timing.o : lib_timing.c $(INCS) 36 $(COMPILE) -c lib_timing.c -o $O/lib_timing.o
|
/openbmc/u-boot/board/freescale/lx2160a/ |
H A D | README | 90 |Connect I/O cable to IO_SLOT1(J110) 93 |Connect I/O cable to IO_SLOT2(J113) 97 |Connect I/O cable to IO_SLOT1(J110) 100 |Connect I/O cable to IO_SLOT2(J113) 104 |Connect I/O cable to IO_SLOT1(J110) 107 |Connect I/O cable to IO_SLOT2(J113) 111 |Connect I/O cable to IO_SLOT1(J110) 114 |Connect I/O cable to IO_SLOT2(J113) 118 |Connect I/O cable to IO_SLOT1(J110) 121 |Connect I/O cable to IO_SLOT2(J113) [all …]
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H 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, 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 …]
|
/openbmc/linux/Documentation/hwmon/ |
H 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 …]
|
H 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, 72 be used to force the base I/O address of the hardware monitoring block. 78 # Enter the Super I/O config space:: [all …]
|
H 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 …]
|
/openbmc/linux/Documentation/arch/s390/ |
H A 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 …]
|
H A 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 …]
|
/openbmc/linux/Documentation/driver-api/ |
H 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 …]
|
H 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
|
/openbmc/linux/Documentation/block/ |
H A 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 …]
|
/openbmc/openbmc/poky/meta/recipes-devtools/nasm/nasm/ |
H A D | 0001-stdlib-Add-strlcat.patch | 26 LIBOBJ_NW = stdlib/snprintf.$(O) stdlib/vsnprintf.$(O) stdlib/strlcpy.$(O) \ 27 - stdlib/strnlen.$(O) stdlib/strrchrnul.$(O) \ 28 + stdlib/strnlen.$(O) stdlib/strrchrnul.$(O) stdlib/strlcat.$(O) \ 30 nasmlib/ver.$(O) \ 31 nasmlib/alloc.$(O) nasmlib/asprintf.$(O) nasmlib/errfile.$(O) \
|
/openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
H A D | 0001-testsuite-use-www.example.org-for-wget-test-cases.patch | 13 testsuite/wget/wget--O-overrides--P | 2 +- 19 diff --git a/testsuite/wget/wget--O-overrides--P b/testsuite/wget/wget--O-overrides--P 21 --- a/testsuite/wget/wget--O-overrides--P 22 +++ b/testsuite/wget/wget--O-overrides--P 27 -busybox wget -q -O index.html -P foo http://www.google.com/ 28 +busybox wget -q -O index.html -P foo http://www.example.org/ 46 -busybox wget -q -O foo http://www.google.com/ 47 +busybox wget -q -O foo http://www.example.org/
|
/openbmc/qemu/docs/ |
H A D | throttle.txt | 12 I/O operations. The code itself is generic and independent of the I/O 14 and operations per second (IOPS) when performing disk I/O. 20 Using throttling to limit disk I/O 22 Two aspects of the disk I/O can be limited: the number of bytes per 27 I/O limits can be set using the throttling.* parameters of -drive, or 71 I/O bursts 74 user to do bursts of I/O for a configurable amount of time. A burst is 75 an amount of I/O that can exceed the basic limit. Bursts are useful to 81 I/O they allow. These two can be configured separately for each one of 85 The I/O limit during bursts is set using 'iops-total-max', and the [all …]
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | O-UDA-1.0 | 3 This is the Open Use of Data Agreement, Version 1.0 (the "O-UDA"). Capitalized terms are defined in… 7 … the Data made available to you by the Data Provider under this O-UDA if you follow the O-UDA's te… 9 …out of the use, modification, or distribution of the Data provided you meet the terms of the O-UDA. 11 …1.3 This O-UDA does not restrict your use, modification, or distribution of any portions of the Da… 15 2.1. The O-UDA does not impose any restriction with respect to: 27 …r Upstream Data Providers at least as broad as those contained in Section 4.2 and 4.3 of the O-UDA. 39 …5.1. "Data" means the material you receive under the O-UDA in modified or unmodified form, but not… 41 … Provider" means the source from which you receive the Data and with whom you enter into the O-UDA. 43 …rson or persons who receives the Data directly or indirectly from you in accordance with the O-UDA. 47 …h the Data Provider directly or indirectly received, under the terms of the O-UDA, material that i…
|
/openbmc/linux/Documentation/translations/zh_CN/sound/hd-audio/ |
H A D | controls.rst | 21 制多I/O插孔的插孔重分配。 53 输入“和”线路输入“以确定输入偏置,或者当引脚是环绕声道的多I/O插孔时,它 61 一个枚举控件,用于为环绕输出重新分配多个I/O插孔的任务。当它打开时,相应 98 被使用的通道数:”2ch“、”4ch“和”6ch“。根据配置,这还控制多I/O插孔的插孔重
|
/openbmc/linux/tools/scripts/ |
H A 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)
|
/openbmc/linux/arch/powerpc/boot/ |
H 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
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/vblade/files/ |
H A D | makefile-add-ldflags.patch | 12 O=aoe.o bpf.o ${PLATFORM}.o ata.o dat.o 14 vblade: $O 15 - ${CC} -o vblade $O 16 + ${CC} ${LDFLAGS} -o vblade $O
|
/openbmc/linux/Documentation/features/scripts/ |
H 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
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H 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.
|