Browse Source

docs: Replace Qemu -> QEMU

Signed-off-by: Stefan Weil <sw@weilnetz.de>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Knut Omang <knuto@ifi.uio.no>
Message-Id: <20220422083007.1082667-1-sw@weilnetz.de>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Stefan Weil 3 years ago
parent
commit
9b76572431
1 changed files with 3 additions and 3 deletions
  1. 3 3
      docs/pcie_sriov.txt

+ 3 - 3
docs/pcie_sriov.txt

@@ -8,8 +8,8 @@ of a PCI Express device. It allows a single physical function (PF) to appear as
 virtual functions (VFs) for the main purpose of eliminating software
 virtual functions (VFs) for the main purpose of eliminating software
 overhead in I/O from virtual machines.
 overhead in I/O from virtual machines.
 
 
-Qemu now implements the basic common functionality to enable an emulated device
-to support SR/IOV. Yet no fully implemented devices exists in Qemu, but a
+QEMU now implements the basic common functionality to enable an emulated device
+to support SR/IOV. Yet no fully implemented devices exists in QEMU, but a
 proof-of-concept hack of the Intel igb can be found here:
 proof-of-concept hack of the Intel igb can be found here:
 
 
 git://github.com/knuto/qemu.git sriov_patches_v5
 git://github.com/knuto/qemu.git sriov_patches_v5
@@ -18,7 +18,7 @@ Implementation
 ==============
 ==============
 Implementing emulation of an SR/IOV capable device typically consists of
 Implementing emulation of an SR/IOV capable device typically consists of
 implementing support for two types of device classes; the "normal" physical device
 implementing support for two types of device classes; the "normal" physical device
-(PF) and the virtual device (VF). From Qemu's perspective, the VFs are just
+(PF) and the virtual device (VF). From QEMU's perspective, the VFs are just
 like other devices, except that some of their properties are derived from
 like other devices, except that some of their properties are derived from
 the PF.
 the PF.