public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [patch 2/2] KVM: switch to get_user_pages_fast
Date: Thu, 11 Sep 2008 17:06:30 +0300	[thread overview]
Message-ID: <48C925E6.5070009@qumranet.com> (raw)
In-Reply-To: <20080911134425.012616301@localhost.localdomain>

Marcelo Tosatti wrote:
> Convert gfn_to_pfn to use get_user_pages_fast, which can do lockless
> pagetable lookups on x86. Kernel compilation on 4-way guest is 3.7%
> faster on VMX.
>
> Hollis, can you fix kvmppc_mmu_map? gfn_to_page must not be called with
> mmap_sem held.
>
> Looks tricky:
> /* Must be called with mmap_sem locked for writing. */
> static void kvmppc_44x_shadow_release(struct kvm_vcpu *vcpu,
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> CC: Hollis Blanchard <hollisb@us.ibm.com>
>
>   

I'll wait until this is resolved, since I don't want to break ppc.

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


  reply	other threads:[~2008-09-11 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 13:43 [patch 0/2] switch to get_user_pages_fast Marcelo Tosatti
2008-09-11 13:43 ` [patch 1/2] KVM: opencode gfn_to_page in kvm_vm_fault Marcelo Tosatti
2008-09-11 13:43 ` [patch 2/2] KVM: switch to get_user_pages_fast Marcelo Tosatti
2008-09-11 14:06   ` Avi Kivity [this message]
2008-09-11 15:04   ` Hollis Blanchard
2008-09-11 15:15     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2008-09-16 23:54 [patch 0/2] " Marcelo Tosatti
2008-09-16 23:54 ` [patch 2/2] KVM: " Marcelo Tosatti
2008-09-17 14:42   ` Hollis Blanchard

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=48C925E6.5070009@qumranet.com \
    --to=avi@qumranet.com \
    --cc=hollisb@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox