All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 2/3] KVM: VMX: Simplify pdptr and cr3 management
Date: Tue, 02 Jun 2009 14:44:49 +0300	[thread overview]
Message-ID: <4A2510B1.6070900@redhat.com> (raw)
In-Reply-To: <200906021931.08737.sheng@linux.intel.com>

Sheng Yang wrote:
> Yes, you are right. Quite beautiful. :)
>   

Thanks :)

It's basically a continuation of RIP/RSP caching.  I plan to continue it 
for cr0/cr3.

> Sorry for misunderstood the meaning of "on demand" without looking at the 
> patch carefully...
>
> Looks fine now. Thanks!
>
> BTW: one extra blank line above function kvm_pdptr_read() in patch 3. ;)
>   

Will fix.

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


  reply	other threads:[~2009-06-02 11:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 13:22 [PATCH 0/3] Cache PDPTRs under ept/npt Avi Kivity
2009-06-01 13:22 ` [PATCH 1/3] KVM: VMX: Avoid duplicate ept tlb flush when setting cr3 Avi Kivity
2009-06-01 13:22 ` [PATCH 2/3] KVM: VMX: Simplify pdptr and cr3 management Avi Kivity
2009-06-02  9:22   ` Sheng Yang
2009-06-02  9:26     ` Avi Kivity
2009-06-02  9:30       ` Sheng Yang
2009-06-02  9:46         ` Avi Kivity
2009-06-02  9:56           ` Sheng Yang
2009-06-02 10:16             ` Avi Kivity
2009-06-02 11:31               ` Sheng Yang
2009-06-02 11:44                 ` Avi Kivity [this message]
2009-06-01 13:22 ` [PATCH 3/3] KVM: Cache pdptrs Avi Kivity
2009-06-02  9:04   ` Joerg Roedel
2009-06-02  9:09     ` Avi Kivity
2009-06-02  9:30       ` Joerg Roedel
2009-06-02  9:44         ` Avi Kivity
2009-06-02 11:50       ` Avi Kivity

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=4A2510B1.6070900@redhat.com \
    --to=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.intel.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.