All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>,
	Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: A question about HTL VM-Exit handling time
Date: Tue, 28 Oct 2014 11:16:17 +0100	[thread overview]
Message-ID: <544F6CF1.5080501@redhat.com> (raw)
In-Reply-To: <20141027235245.GC27081@kernel>

On 10/28/2014 12:52 AM, Wanpeng Li wrote:
> As you know, kernel build which Feng used is a CPU bound workload,
> so why 22.28% samples is halt?

Because in a CPU bound workload you don't have many exits in the first
place.  But there could also be some issues with the way he used perf.
213821 interrupts seem to be really few.

Paolo

  reply	other threads:[~2014-10-28 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  8:15 A question about HTL VM-Exit handling time Wu, Feng
2014-10-21 18:39 ` Paolo Bonzini
2014-10-23  4:56   ` Wu, Feng
2014-10-23 12:23     ` Paolo Bonzini
2014-10-24  1:14       ` Wu, Feng
2014-10-27 23:52   ` Wanpeng Li
2014-10-28 10:16     ` Paolo Bonzini [this message]
2014-10-28  7:46   ` Christian Borntraeger

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=544F6CF1.5080501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=wanpeng.li@linux.intel.com \
    --cc=xiaoguangrong.eric@gmail.com \
    /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.