All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
	Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>,
	mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [RFC PATCH] KVM: x86: Skip request checking branches in vcpu_enter_guest() more effectively
Date: Mon, 24 Sep 2012 16:53:09 +0200	[thread overview]
Message-ID: <506073D5.7040307@redhat.com> (raw)
In-Reply-To: <20120924233250.ee28141b66d47b6c8bd39727@gmail.com>

On 09/24/2012 04:32 PM, Takuya Yoshikawa wrote:
> On Mon, 24 Sep 2012 12:09:00 +0200
> Avi Kivity <avi@redhat.com> wrote:
> 
>> > while (vcpu->request) {
>> > 	xchg(vcpu->request, request);
>> > 
>> > 	for_each_set_bit(request) {
>> > 		clear_bit(X);
>> > 
>> > 		......
>> > 	}
>> > 	
>> > }
>> 
>> In fact I had something like that in one of the earlier versions, but it
>> was problematic.  I'll try to see what the issue was.
> 
> Unless there are many requests, the cost of for_each_set_bit() and a few
> added code may exceed that of the original code.
> (Looping using __ffs() is an alternative because requests is "long".)
> 
> So I wanted to know the most common requests pattern.

See other branch of this thread.  But in short, I now think you are
right and the special-case is warranted.

(not for STEAL_UPDATE - that's likely a bug, it should only happen on
overcommit)


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

  reply	other threads:[~2012-09-24 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24  6:24 [RFC PATCH] KVM: x86: Skip request checking branches in vcpu_enter_guest() more effectively Takuya Yoshikawa
2012-09-24  6:59 ` Xiao Guangrong
2012-09-24 10:09   ` Avi Kivity
2012-09-24 14:32     ` Takuya Yoshikawa
2012-09-24 14:53       ` Avi Kivity [this message]
2012-09-24 13:55   ` Takuya Yoshikawa
2012-09-24  7:16 ` Gleb Natapov
2012-09-24 10:10   ` Avi Kivity
2012-09-24 13:58   ` Takuya Yoshikawa
2012-10-04 16:11   ` Takuya Yoshikawa
2012-09-24 10:18 ` Avi Kivity
2012-09-24 14:14   ` Takuya Yoshikawa
2012-09-24 14:50     ` Avi Kivity
2012-09-26  2:06       ` Takuya Yoshikawa
2012-09-27  9:28         ` 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=506073D5.7040307@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=takuya.yoshikawa@gmail.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    --cc=yoshikawa_takuya_b1@lab.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.