From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] simpletrace: Thread-safe tracing
Date: Sun, 27 Feb 2011 18:14:27 +0200 [thread overview]
Message-ID: <4D6A7863.2030406@redhat.com> (raw)
In-Reply-To: <1298818682-5404-1-git-send-email-stefanha@linux.vnet.ibm.com>
On 02/27/2011 04:58 PM, Stefan Hajnoczi wrote:
> Trace events outside the global mutex cannot be used with the simple
> trace backend since it is not thread-safe. There is no check to prevent
> them being enabled so people sometimes learn this the hard way.
>
> This patch restructures the simple trace backend with a ring buffer
> suitable for multiple concurrent writers. A writeout thread empties the
> trace buffer when threshold fill levels are reached. Should the
> writeout thread be unable to keep up with trace generation, records will
> simply be dropped.
It would be good to have an indication of the fact that records were
dropped in the file.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-27 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 14:58 [Qemu-devel] [PATCH] simpletrace: Thread-safe tracing Stefan Hajnoczi
2011-02-27 15:13 ` [Qemu-devel] " Paolo Bonzini
2011-02-27 17:02 ` Stefan Hajnoczi
2011-02-27 18:16 ` Paolo Bonzini
2011-02-28 9:35 ` Stefan Hajnoczi
2011-02-27 16:14 ` Avi Kivity [this message]
2011-02-27 17:06 ` [Qemu-devel] " Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2011-02-28 9:38 Stefan Hajnoczi
2011-03-22 23:52 ` Andreas Färber
2011-03-23 7:39 ` Stefan Hajnoczi
2011-03-23 7:58 ` Stefan Hajnoczi
2011-03-23 7:59 ` Stefan Hajnoczi
2011-03-23 8:16 ` Alexander Graf
2011-03-23 20:42 ` Andreas Färber
2011-03-23 20:47 ` Stefan Hajnoczi
2011-03-23 20:58 ` Andreas Färber
2011-03-23 21:05 ` Stefan Hajnoczi
2011-03-23 21:24 ` Andreas Färber
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=4D6A7863.2030406@redhat.com \
--to=avi@redhat.com \
--cc=kwolf@redhat.com \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).