From: Richard Henderson <rth@twiddle.net>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg: dump op count to the same stream as other info
Date: Sun, 02 Nov 2014 11:53:11 -0800 [thread overview]
Message-ID: <54568BA7.50705@twiddle.net> (raw)
In-Reply-To: <1414915640-9543-1-git-send-email-jcmvbkbc@gmail.com>
On 11/02/2014 01:07 AM, Max Filippov wrote:
> Otherwise 'info jit' outputs half of the information to monitor and the
> rest to qemu log.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> tcg/tcg.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
Well, yes, but do you really want 60+ lines of per-opcode use counts on the
monitor? I'm pretty sure I would never find that useful...
r~
next prev parent reply other threads:[~2014-11-02 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 8:07 [Qemu-devel] [PATCH] tcg: dump op count to the same stream as other info Max Filippov
2014-11-02 19:53 ` Richard Henderson [this message]
2014-11-02 19:56 ` Max Filippov
2014-11-02 20:00 ` Richard Henderson
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=54568BA7.50705@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).