All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: shashank rachamalla <shashank.rachamalla@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Questing regarding KVM Guest PMU
Date: Sun, 18 Mar 2012 18:51:20 +0200	[thread overview]
Message-ID: <20120318165120.GF27306@redhat.com> (raw)
In-Reply-To: <CAMONAZ5H9iet-sHS_tOZP7XoTyusttNYwrt4vNkaqV50woH-eQ@mail.gmail.com>

On Sun, Mar 18, 2012 at 09:47:55PM +0530, shashank rachamalla wrote:
> >> I guess things are working fine with perf. But why not with oprofile ?
> >>
> > Looks like it. I never tried oprofile. Will try to reproduce your
> > problem and see what oprofile is doing.
> 
> I am using ubuntu 10.04 with 2.6.32-21-generic kernel as guest and
> oprofile 0.9.6.
> Also, I have tried to capture kvm-events ( perf patch ) in host while
> running oprofile and perf in guest.
> Please see the attachment. I have run the tests in three cases for the
> around 5 secs.
> 
> There are more number of MSR reads and writes in case of perf which I
> think is normal. However, there are very few MSR reads and writes with
> oprofile. Also, the number of NMI exceptions are too high in case of
> oprofile.
> 
Which host kernel are you using? Try latest kvm.git and check if you see
something unusual in dmesg.

--
			Gleb.

  reply	other threads:[~2012-03-18 16:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 10:18 Questing regarding KVM Guest PMU shashank rachamalla
2012-03-18 10:30 ` Gleb Natapov
2012-03-18 12:57   ` shashank rachamalla
2012-03-18 14:50     ` Avi Kivity
2012-03-18 14:50     ` Gleb Natapov
2012-03-18 16:17       ` shashank rachamalla
2012-03-18 16:51         ` Gleb Natapov [this message]
2012-03-19  6:50           ` shashank rachamalla
2012-03-19  7:07             ` Gleb Natapov
2012-04-03 13:50               ` shashank rachamalla
2012-04-03 16:58                 ` Gleb Natapov
2012-04-03 18:43                   ` shashank rachamalla
2012-04-03 18:54                     ` shashank rachamalla
2012-04-04  7:04                       ` Gleb Natapov
2012-04-04 10:19                         ` shashank rachamalla
2012-04-04 10:29                           ` Gleb Natapov
2012-04-05  2:37                             ` shashank rachamalla
2012-04-05 12:27                             ` Avi Kivity
2012-04-05 12:37                               ` Gleb Natapov
2012-04-05 12:48                                 ` Avi Kivity
2012-04-05 13:26                                   ` Gleb Natapov
2012-04-05 13:28                                     ` Avi Kivity
2012-04-05 13:48                                       ` Gleb Natapov
2012-04-05 13:57                                         ` Gleb Natapov
2012-04-05 14:38                                           ` Avi Kivity
2012-04-05 14:41                                             ` Gleb Natapov
2012-04-06  5:13                                               ` shashank rachamalla
2012-04-06  6:50                                                 ` Gleb Natapov
2012-04-08 15:27                                                   ` Gleb Natapov
2012-04-09  9:26                                                     ` Gleb Natapov
2012-04-10  3:18                                                       ` shashank rachamalla

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=20120318165120.GF27306@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=shashank.rachamalla@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.