From: cdall@cs.columbia.edu (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: KVM: add support for minimal host vs guest profiling
Date: Wed, 6 Mar 2013 16:49:46 -0800 [thread overview]
Message-ID: <20130307004946.GB23427@gmail.com> (raw)
In-Reply-To: <1362453480-23886-1-git-send-email-marc.zyngier@arm.com>
On Tue, Mar 05, 2013 at 03:18:00AM +0000, Marc Zyngier wrote:
> In order to be able to correctly profile what is happening on the
> host, we need to be able to identify when we're running on the guest,
> and log these events differently.
>
> Perf offers a simple way to register callbacks into KVM. Mimic what
> x86 does and enjoy being able to profile your KVM host.
Thanks, this has been applied to kvm-arm-next.
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <cdall@cs.columbia.edu>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] ARM: KVM: add support for minimal host vs guest profiling
Date: Wed, 6 Mar 2013 16:49:46 -0800 [thread overview]
Message-ID: <20130307004946.GB23427@gmail.com> (raw)
In-Reply-To: <1362453480-23886-1-git-send-email-marc.zyngier@arm.com>
On Tue, Mar 05, 2013 at 03:18:00AM +0000, Marc Zyngier wrote:
> In order to be able to correctly profile what is happening on the
> host, we need to be able to identify when we're running on the guest,
> and log these events differently.
>
> Perf offers a simple way to register callbacks into KVM. Mimic what
> x86 does and enjoy being able to profile your KVM host.
Thanks, this has been applied to kvm-arm-next.
-Christoffer
next prev parent reply other threads:[~2013-03-07 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 3:18 [PATCH] ARM: KVM: add support for minimal host vs guest profiling Marc Zyngier
2013-03-05 3:18 ` Marc Zyngier
2013-03-07 0:49 ` Christoffer Dall [this message]
2013-03-07 0:49 ` Christoffer Dall
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=20130307004946.GB23427@gmail.com \
--to=cdall@cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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 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.