All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Fix typos in Documentation/kvm/mmu.txt
Date: Thu, 17 Jun 2010 11:10:53 +0300	[thread overview]
Message-ID: <4C19D88D.5020707@redhat.com> (raw)
In-Reply-To: <1276752758-22382-1-git-send-email-jasowang@redhat.com>

On 06/17/2010 08:32 AM, Jason Wang wrote:
> Signed-off-by: Jason Wang<jasowang@redhat.com>
> ---
>   Documentation/kvm/mmu.txt |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kvm/mmu.txt b/Documentation/kvm/mmu.txt
> index 8cb42b9..5d3343f 100644
> --- a/Documentation/kvm/mmu.txt
> +++ b/Documentation/kvm/mmu.txt
> @@ -77,10 +77,10 @@ Memory
>
>   Guest memory (gpa) is part of the user address space of the process that is
>   using kvm.  Userspace defines the translation between guest addresses and user
> -addresses (gpa->hva); note that two gpas may alias to the same gva, but not
> +addresses (gpa->hva); note that two gvas may alias to the same gpa, but not
>   vice versa.
>    

Should really be, two gpas may alias to the same hva.

> -These gvas may be backed using any method available to the host: anonymous
> +These gpas may be backed using any method available to the host: anonymous
>    

Should be: These hvas.

>   memory, file backed memory, and device memory.  Memory might be paged by the
>   host at any time.
>
>    


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-06-17  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  5:32 [PATCH] KVM: Fix typos in Documentation/kvm/mmu.txt Jason Wang
2010-06-17  8:10 ` Avi Kivity [this message]
2010-06-17  8:28   ` Jason Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C19D88D.5020707@redhat.com \
    --to=avi@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.