public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, Andrew Theurer <habanero@linux.vnet.ibm.com>
Subject: Re: [PATCH] don't call adjust_vmx_controls() second time
Date: Thu, 27 Aug 2009 19:21:43 +0300	[thread overview]
Message-ID: <4A96B297.5090003@redhat.com> (raw)
In-Reply-To: <20090827154130.GR30093@redhat.com>

On 08/27/2009 06:41 PM, Gleb Natapov wrote:
> Don't call adjust_vmx_controls() two times for the same control.
> It restores options that was dropped earlier.
>    

Applied, thanks.  Andrew, if you rerun your benchmark atop kvm.git 
'next' branch, I believe you will see dramatically better results.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-08-27 16:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 15:41 [PATCH] don't call adjust_vmx_controls() second time Gleb Natapov
2009-08-27 16:21 ` Avi Kivity [this message]
2009-08-27 20:42   ` Andrew Theurer
2009-08-30  8:59     ` Avi Kivity
2009-08-31 13:05       ` Andrew Theurer
2009-08-31 13:52         ` 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=4A96B297.5090003@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.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