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/6] trace: [tracetool] Do not rebuild event list in backend code
Date: Wed, 18 Jan 2012 14:52:12 +0530 [thread overview]
Message-ID: <4F168F44.7090104@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120111180504.25198.76946.stgit@ginnungagap.bsc.es>
On 01/11/2012 11:35 PM, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova<vilanova@ac.upc.edu>
> ---
> scripts/tracetool.py | 14 +++++++-------
> 1 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/scripts/tracetool.py b/scripts/tracetool.py
> index 6874f66..80e5684 100755
> --- a/scripts/tracetool.py
> +++ b/scripts/tracetool.py
[.. snip ..]
> @@ -510,14 +508,16 @@ class Event(object):
>
> # Generator that yields Event objects given a trace-events file object
> def read_events(fobj):
> + res = []
> event_num = 0
> for line in fobj:
> if not line.strip():
> continue
> if line.lstrip().startswith('#'):
> continue
> - yield Event(event_num, line)
> + res.append(Event(event_num, line))
> event_num += 1
> + return res
>
Hi Lluis,
This looks really nice. I can include your fixes while addressing other
review comments. Shall I fold your patches with mine or do you want to
keep them separate?
regards,
Harsh
> backend = ""
> output = ""
>
>
next prev parent reply other threads:[~2012-01-18 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 18:05 [Qemu-devel] [PATCH 1/6] trace: [tracetool] Do not rebuild event list in backend code Lluís Vilanova
2012-01-11 18:05 ` [Qemu-devel] [PATCH 2/6] trace: [tracetool] Simplify event line parsing Lluís Vilanova
2012-01-11 18:05 ` [Qemu-devel] [PATCH 3/6] trace: [ŧracetool] Do not precompute the event number Lluís Vilanova
2012-01-18 9:48 ` Harsh Bora
2012-01-18 10:34 ` Stefan Hajnoczi
2012-01-11 18:05 ` [Qemu-devel] [PATCH 4/6] trace: [tracetool] Add support for event properties Lluís Vilanova
2012-01-11 18:06 ` [Qemu-devel] [PATCH 5/6] trace: [tracetool] Process the "disable" event property Lluís Vilanova
2012-01-11 18:06 ` [Qemu-devel] [PATCH 6/6] trace: [tracetool] Rewrite event argument parsing Lluís Vilanova
2012-01-11 19:16 ` [Qemu-devel] [PATH 7/6] trace: [tracetool] Make format-specific code optional and with access to event information Lluís Vilanova
2012-01-18 9:22 ` Harsh Bora [this message]
2012-01-18 11:45 ` [Qemu-devel] [PATCH 1/6] trace: [tracetool] Do not rebuild event list in backend code Lluís Vilanova
2012-01-18 12:00 ` Lluís Vilanova
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=4F168F44.7090104@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 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).