From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v10 0/7] trace: Generic event state description
Date: Fri, 1 Mar 2013 11:20:01 +0100 [thread overview]
Message-ID: <20130301102001.GA575@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <87fw0g4kic.fsf@fimbulvetr.bsc.es>
On Thu, Feb 28, 2013 at 02:48:27PM +0100, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Fri, Jan 25, 2013 at 05:33:46PM +0100, Lluís Vilanova wrote:
> >> Provides a generic event state description structure (TraceEvent) and a more
> >> detailed event control and query interface.
> >>
> >> This is achieved by creating a new "non-public" tracing backend (i.e., not
> >> selectable by the user at configure time) that will generate the appropriate
> >> event description information.
> >>
> >> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> >> ---
>
> > Hi Lluís,
> > I hit an issue testing the different backends with this series applied.
>
> > The simple trace writeout thread hangs when the 'quit' monitor command
> > is issued. Do you see the same issue?
>
> > $ ./configure --target-list=x86_64-softmmu --enable-trace-backend=simple
> > $ make -j4
> > $ cat my-events
> > bdrv_open_common
> > $ x86_64-softmmu/qemu-system-x86_64 -trace events=my-events
> > (qemu) quit
>
> I've rebased the series in master (which forced me to fix a tiny line in a
> makefile, due recent changes), and everything's working fine.
>
> I can resend the rebased series, if you want.
Okay, sounds good. I'll retest your rebased series.
Stefan
parent reply other threads:[~2013-03-01 10:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87fw0g4kic.fsf@fimbulvetr.bsc.es>]
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=20130301102001.GA575@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--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).