From: Gabriel Kerneis <gabriel@kerneis.info>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com, pbonzini@redhat.com,
charlie@ctshepherd.com
Subject: Re: [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a blocking_fn annotation
Date: Fri, 6 Sep 2013 15:46:47 +0100 [thread overview]
Message-ID: <20130906144647.GC7398@kerneis.info> (raw)
In-Reply-To: <1378477839-7353-1-git-send-email-gabriel@kerneis.info>
On Fri, Sep 06, 2013 at 03:30:38PM +0100, Gabriel Kerneis wrote:
> More precisely, here is what CoroCheck does for each file of QEMU:
> - produce a .dot file that can be processed with graphviz to produce a
> pdf of the annotated call graph (with wrong annotations showing up in
> red - this still needs to be documented properly).
For those of you interested in finding out what those graphs look like,
I have uploaded the result for qemu-coroutine-lock.c here:
http://www.scribd.com/doc/166033638/qemu-coroutine-lock-c
As explained on the right:
- Square = should be coroutine_fn
- Circle = need not be coroutine_fn
- Dashed red = wrong annotation (either missing or spurious)
Best regards,
--
Gabriel
next prev parent reply other threads:[~2013-09-06 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 14:30 [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a blocking_fn annotation Gabriel Kerneis
2013-09-06 14:30 ` [Qemu-devel] [RFC] Introduce " Gabriel Kerneis
2013-09-06 14:46 ` Gabriel Kerneis [this message]
2013-09-06 15:36 ` [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a " Charlie Shepherd
2013-09-06 16:05 ` Gabriel Kerneis
2013-09-06 16:28 ` Kevin Wolf
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=20130906144647.GC7398@kerneis.info \
--to=gabriel@kerneis.info \
--cc=charlie@ctshepherd.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).