All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: Abel Gordon <ABELG@il.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Ren, Yongjie" <yongjie.ren@intel.com>
Subject: Re: [nVMX Test] Build kernel (defconfig) on L2, w/ VMCS Shadowing enabled on L0
Date: Mon, 13 May 2013 11:34:48 +0300	[thread overview]
Message-ID: <20130513083448.GM10830@redhat.com> (raw)
In-Reply-To: <CAOaxAcYwWsUeUECaOjiZREZw6XpXaqaQaaH1T6B5DnuAEmCDzA@mail.gmail.com>

On Mon, May 13, 2013 at 01:41:28PM +0530, Kashyap Chamarthy wrote:
> >
> > Yep, kvm_stat is the simplest way to monitor the exits frequency.
> 
> Attached is kvm_stat results from L1, captured from several seconds of
> intervals.
> 
You should run it on L0 while compilation is running in L2 once for each
of two cased: with and without shadow vmcs.

--
			Gleb.

  reply	other threads:[~2013-05-13  8:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  4:58 [nVMX Test] Build kernel (defconfig) on L2, w/ VMCS Shadowing enabled on L0 Kashyap Chamarthy
2013-05-13  6:10 ` Ren, Yongjie
2013-05-13  6:21   ` Kashyap Chamarthy
2013-05-13  7:07     ` Kashyap Chamarthy
2013-05-13  7:16       ` Abel Gordon
2013-05-13  7:31         ` Kashyap Chamarthy
2013-05-13  7:51           ` Abel Gordon
2013-05-13  8:11             ` Kashyap Chamarthy
2013-05-13  8:34               ` Gleb Natapov [this message]
2013-05-13 12:30                 ` Kashyap Chamarthy
2013-05-13 13:02                   ` Abel Gordon
2013-05-13 15:13                     ` Kashyap Chamarthy
2013-05-13 15:19                       ` Abel Gordon
2013-05-13 15:29                         ` Kashyap Chamarthy
2013-05-13 18:55                           ` Kashyap Chamarthy
2013-05-15  4:17                             ` Kashyap Chamarthy
2013-05-13  7:30       ` Ren, Yongjie
2013-05-13  7:38         ` Kashyap Chamarthy

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=20130513083448.GM10830@redhat.com \
    --to=gleb@redhat.com \
    --cc=ABELG@il.ibm.com \
    --cc=kashyap.cv@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=yongjie.ren@intel.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.