From: Richard Henderson <rth@twiddle.net>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: add separate monitor command to dump opcode counters
Date: Tue, 04 Nov 2014 16:02:52 +0100 [thread overview]
Message-ID: <5458EA9C.3080208@twiddle.net> (raw)
In-Reply-To: <1414960121-18335-1-git-send-email-jcmvbkbc@gmail.com>
On 11/02/2014 09:28 PM, Max Filippov wrote:
> Currently 'info jit' outputs half of the information to monitor and the
> rest to qemu log. Dumping opcode counts to monitor as a part of 'info
> jit' command doesn't sound useful. Add new monitor command 'info
> opcount' that only dumps opcode counters.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> include/exec/cpu-all.h | 1 +
> monitor.c | 12 ++++++++++++
> tcg/tcg.c | 12 ++++++++----
> tcg/tcg.h | 1 +
> translate-all.c | 5 +++++
> 5 files changed, 27 insertions(+), 4 deletions(-)
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
next prev parent reply other threads:[~2014-11-04 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 20:28 [Qemu-devel] [PATCH] tcg: add separate monitor command to dump opcode counters Max Filippov
2014-11-04 15:02 ` Richard Henderson [this message]
2014-11-04 15:27 ` Alex Bennée
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=5458EA9C.3080208@twiddle.net \
--to=rth@twiddle.net \
--cc=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).