From: Gleb Natapov <gleb@kernel.org>
To: Razya Ladelsky <RAZYA@il.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
abel.gordon@gmail.com, Anthony Liguori <anthony@codemonkey.ws>,
asias@redhat.com, digitaleric@google.com,
Eran Raichstein <ERANRA@il.ibm.com>,
gleb@redhat.com, jasowang@redhat.com,
Joel Nider <JOELN@il.ibm.com>,
kvm@vger.kernel.org, kvm-owner@vger.kernel.org,
pbonzini@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
Yossi Kuperman1 <YOSSIKU@il.ibm.com>,
Eyal Moscovici <EYALMO@il.ibm.com>,
bsd@redhat.com
Subject: Re: Updated Elvis Upstreaming Roadmap
Date: Tue, 24 Dec 2013 18:21:03 +0200 [thread overview]
Message-ID: <20131224162103.GB5365@minantech.com> (raw)
In-Reply-To: <OFAAB02888.70858D88-ONC2257C43.00545F93-C2257C44.00376177@il.ibm.com>
On Tue, Dec 17, 2013 at 12:04:42PM +0200, Razya Ladelsky wrote:
> 4. vhost statistics
>
> The issue that was raised for the vhost statistics was using ftrace
> instead of the debugfs mechanism.
> However, looking further into the kvm stat mechanism, we learned that
> ftrace didn't replace the plain debugfs mechanism, but was used in
> addition to it.
>
It did. Statistics in debugfs is deprecated. No new statistics are
added there. kvm_stat is using ftrace now (if available) and of course
ftrace gives seamless integration with perf.
--
Gleb.
next prev parent reply other threads:[~2013-12-24 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:04 Updated Elvis Upstreaming Roadmap Razya Ladelsky
2013-12-18 10:43 ` Michael S. Tsirkin
2013-12-19 6:40 ` Abel Gordon
2013-12-19 10:13 ` Michael S. Tsirkin
2013-12-19 10:36 ` Abel Gordon
2013-12-19 11:37 ` Michael S. Tsirkin
2013-12-19 12:56 ` Abel Gordon
2013-12-19 13:48 ` Michael S. Tsirkin
2013-12-19 14:19 ` Abel Gordon
2013-12-19 14:48 ` Michael S. Tsirkin
2013-12-24 12:50 ` Razya Ladelsky
2013-12-24 16:21 ` Gleb Natapov [this message]
2013-12-25 7:38 ` Razya Ladelsky
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=20131224162103.GB5365@minantech.com \
--to=gleb@kernel.org \
--cc=ERANRA@il.ibm.com \
--cc=EYALMO@il.ibm.com \
--cc=JOELN@il.ibm.com \
--cc=RAZYA@il.ibm.com \
--cc=YOSSIKU@il.ibm.com \
--cc=abel.gordon@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=asias@redhat.com \
--cc=bsd@redhat.com \
--cc=digitaleric@google.com \
--cc=gleb@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm-owner@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox