qemu-trivial
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] docs: Replace Qemu -> QEMU


From: Knut Omang
Subject: Re: [PATCH] docs: Replace Qemu -> QEMU
Date: Fri, 22 Apr 2022 10:38:59 +0200
User-agent: Evolution 3.42.4 (3.42.4-1.fc35)

On Fri, 2022-04-22 at 10:30 +0200, Stefan Weil wrote:
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
>  docs/pcie_sriov.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/docs/pcie_sriov.txt b/docs/pcie_sriov.txt
> index f5e891e1d4..11158dbf88 100644
> --- a/docs/pcie_sriov.txt
> +++ b/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
>  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:
>  
>  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 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
>  the PF.
>  

Reviewed-by: Knut Omang <knuto@ifi.uio.no>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]