From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: aneesh.kumar@linux.vnet.ibm.com, qemu-devel@nongnu.org,
stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/3] monitor: remove unused do_info_trace
Date: Tue, 08 May 2012 10:41:36 +0530 [thread overview]
Message-ID: <4FA8AB08.5070505@linux.vnet.ibm.com> (raw)
In-Reply-To: <87vck8xfvy.fsf@fimbulvetr.bsc.es>
On 05/07/2012 07:16 PM, Lluís Vilanova wrote:
> Harsh Prateek Bora writes:
>
>> Going forward with simpletrace v2 variable size trace records, we cannot
>> have a generic function to print trace event info and therefore this
>> interface becomes invalid.
>
>> As per Stefan Hajnoczi:
>
>> "This command is only available from the human monitor. It's not very
>> useful because it historically hasn't been able to pretty-print events
>> or show them in the right order (we use a ringbuffer but it prints
>> them out from index 0).
>
>> Therefore, I don't think we're under any obligation to keep this
>> command around. No one has complained about it's limitations - I
>> think this is a sign that no one has used it. I'd be okay with a
>> patch that removes it."
>
>> Ref: http://lists.gnu.org/archive/html/qemu-devel/2012-01/msg01268.html
>
> Eliminating 'do_info_trace' makes 'st_print_trace' unused; so maybe it could
> also be eliminated.
>
Yeah, though that gets removed in 2/3 patch, it makes sense to remove
that here.
- Harsh
>
> Lluis
>
>
>> Signed-off-by: Harsh Prateek Bora<harsh@linux.vnet.ibm.com>
>> ---
>> monitor.c | 16 ----------------
>> 1 files changed, 0 insertions(+), 16 deletions(-)
>
>> diff --git a/monitor.c b/monitor.c
>> index 8946a10..bebf864 100644
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -812,13 +812,6 @@ static void do_info_cpu_stats(Monitor *mon)
>> }
>> #endif
>
>> -#if defined(CONFIG_TRACE_SIMPLE)
>> -static void do_info_trace(Monitor *mon)
>> -{
>> - st_print_trace((FILE *)mon,&monitor_fprintf);
>> -}
>> -#endif
>> -
>> static void do_trace_print_events(Monitor *mon)
>> {
>> trace_print_events((FILE *)mon,&monitor_fprintf);
>> @@ -2585,15 +2578,6 @@ static mon_cmd_t info_cmds[] = {
>> .help = "show roms",
>> .mhandler.info = do_info_roms,
>> },
>> -#if defined(CONFIG_TRACE_SIMPLE)
>> - {
>> - .name = "trace",
>> - .args_type = "",
>> - .params = "",
>> - .help = "show current contents of trace buffer",
>> - .mhandler.info = do_info_trace,
>> - },
>> -#endif
>> {
>> .name = "trace-events",
>> .args_type = "",
>> --
>> 1.7.1.1
>
>
>
next prev parent reply other threads:[~2012-05-08 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:56 [Qemu-devel] [PATCH 0/3] Simpletrace v2: Support multiple args, strings Harsh Prateek Bora
2012-05-03 17:56 ` [Qemu-devel] [PATCH 1/3] monitor: remove unused do_info_trace Harsh Prateek Bora
2012-05-07 13:46 ` Lluís Vilanova
2012-05-08 5:11 ` Harsh Bora [this message]
2012-05-03 17:56 ` [Qemu-devel] [PATCH 2/3] simpletrace v2: Support var number of args, strings Harsh Prateek Bora
2012-05-03 17:56 ` [Qemu-devel] [PATCH 3/3] Update simpletrace.py to support new v2 log format Harsh Prateek Bora
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=4FA8AB08.5070505@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=vilanova@ac.upc.edu \
/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.