public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH RFC] KVM: busy-spin detector
Date: Fri, 11 Jun 2010 14:46:27 -0300	[thread overview]
Message-ID: <20100611174627.GF6913@amt.cnet> (raw)
In-Reply-To: <20100611140634.GI5191@balbir.in.ibm.com>

On Fri, Jun 11, 2010 at 07:36:34PM +0530, Balbir Singh wrote:
> * Marcelo Tosatti <mtosatti@redhat.com> [2010-06-10 23:25:51]:
> 
> > 
> > The following patch implements a simple busy-spin detector. It considers
> > a vcpu as busy-spinning if there are two consecutive exits due to
> > external interrupt on the same RIP, and sleeps for 100us in that case.
> > 
> > It is very likely that if the vcpu is making progress it will either
> > exit for other reasons or change RIP.
> > 
> > The percentage numbers below represent improvement in kernel build
> > time in comparison with mainline (RHEL 5.4 guest).
> >
> 
> Interesting approach, is there a reason to tie it in with pause loop
> exits? 

Hum, i don't see any. PLE exits provide the same detection, but more
accurately.

> Can't we do something more generic or even para-virtish.

This is pretty generic already? Or what do you mean?

The advantage is it does not require paravirt modifications in the      
guest (at the expense of guessing what the guest is doing).


  parent reply	other threads:[~2010-06-11 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  2:25 [PATCH RFC] KVM: busy-spin detector Marcelo Tosatti
2010-06-11 14:06 ` Balbir Singh
2010-06-11 15:03   ` Huang, Zhiteng
2010-06-11 17:38     ` Balbir Singh
2010-06-11 17:46   ` Marcelo Tosatti [this message]
2010-06-11 19:18     ` Balbir Singh
2010-06-16  8:22 ` 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=20100611174627.GF6913@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=balbir@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