public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
	kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>,
	linux-kernel@vger.kernel.org, Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH] KVM x86: remove memset, use vzalloc and don't assign the same value to a variable twice
Date: Wed, 3 Nov 2010 10:47:11 -0200	[thread overview]
Message-ID: <20101103124711.GB16809@amt.cnet> (raw)
In-Reply-To: <alpine.LNX.2.00.1011020509590.11973@swampdragon.chaosbits.net>

On Tue, Nov 02, 2010 at 05:11:19AM +0100, Jesper Juhl wrote:
> On Tue, 2 Nov 2010, Takuya Yoshikawa wrote:
> 
> > Hi Jesper, (dropped some addresses from Cc)
> > 
> > > > Jesper Juhl wrote:
> > > There's definately a positive size impact for the generated object code 
> > > and we save having to do the call to memset() and the cost of a vzalloc() 
> > > call looks more or less the same as a call to vmalloc() to me.
> > 
> > > > This patch is not based on kvm.git, I guess.
> > > > 
> > > Nope. It was generated against mainline git as of a couple of days ago. I 
> > > can generate a version against kvm.git if you prefer.
> > 
> > Sorry, I should have said more clearly.
> > 
> > kvm_vm_ioctl_get_dirty_log() has been changed since latest mainline kernel was released.
> > Furthermore, vmalloc() in it is to be removed soon, currently in kvm's next.
> > 
> > I have checked all vmalloc() + memset() in kvm, and there are three remaining.
> > See the patch below.
> >   - I have tested on x86.
> >   - I can test ppc later if needed, but this is so trivial that Alex will see
> >     no problem about this, probably.
> > 
> > So please write your Signed-off-by and ask Avi and Marcelo to apply.
> > 
> > Thanks,
> >   Takuya
> > 
> > ===
> > Subject: [PATCH] KVM: replace vmalloc and memset with vzalloc
> > 
> > Let's use newly introduced vzalloc().
> > 
> > Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
> 
> Signed-off-by: Jesper-juhl <jj@chaosbits.net>

Applied, thanks.



      reply	other threads:[~2010-11-03 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 18:28 [PATCH] KVM x86: remove memset, use vzalloc and don't assign the same value to a variable twice Jesper Juhl
2010-11-01  0:49 ` Takuya Yoshikawa
2010-11-01 18:42   ` Jesper Juhl
2010-11-02  1:49     ` Takuya Yoshikawa
2010-11-02  4:11       ` Jesper Juhl
2010-11-03 12:47         ` Marcelo Tosatti [this message]

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=20101103124711.GB16809@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=jj@chaosbits.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoshikawa.takuya@oss.ntt.co.jp \
    /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