public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/8] KVM: MMU: hypercall based pte updates and TLB flushes
Date: Tue, 04 Mar 2008 11:33:46 +0200	[thread overview]
Message-ID: <47CD177A.9050603@qumranet.com> (raw)
In-Reply-To: <20080303144335.GA3281@dmt>

Marcelo Tosatti wrote:
> Hi Avi,
>
> Looks nice.
>
> On Sun, Mar 02, 2008 at 06:31:17PM +0200, Avi Kivity wrote:
>   
>> +int kvm_pv_mmu_op(struct kvm_vcpu *vcpu, unsigned long bytes,
>> +		  gpa_t addr, unsigned long *ret)
>> +{
>> +	int r;
>> +	struct kvm_pv_mmu_op_buffer buffer;
>>     
>
> Perhaps this structure is a little large to be on stack.
>
>   

512 bytes should be fine as this isn't part of a particularly deep 
path.  If it gives us trouble we can reduce it as the size is 
independent from the guest buffer size.

>> +	down_read(&current->mm->mmap_sem);
>> +	down_read(&vcpu->kvm->slots_lock);
>>     
>
> The order should be slots_locks then mmap_sem. Need some comment in the
> code.
>   

Changed, thanks.

As the patchset (less cr3 caching) passed the regression tests I'll 
apply it.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-04  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 16:31 [PATCH 4/8] KVM: MMU: hypercall based pte updates and TLB flushes Avi Kivity
2008-03-03 14:43 ` Marcelo Tosatti
2008-03-04  9:33   ` Avi Kivity [this message]
2008-03-04 10:19     ` 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=47CD177A.9050603@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.org \
    /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