From: Charlie Shepherd <charlie@ctshepherd.com>
To: Gabriel Kerneis <gabriel@kerneis.info>
Cc: kwolf@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a blocking_fn annotation
Date: Fri, 06 Sep 2013 16:36:47 +0100 [thread overview]
Message-ID: <5229F68F.8060704@ctshepherd.com> (raw)
In-Reply-To: <1378477839-7353-1-git-send-email-gabriel@kerneis.info>
On 06/09/2013 15:30, Gabriel Kerneis wrote:
> Note that CoroCheck has been written as a plugin to CIL [5]. Contrary to
> CPC, which is still somewhat of a prototype (although a pretty good
> one!), CIL is a solid piece of software, packaged in both Fedora and
> (very soon) Debian. CoroCheck makes use of the CIL plugin facility which
> has not made its way into a released version yet, but this should happen
> in the next few months. Therefore, in a not-too-distant future, it is
> reasonable to imagine that static checking of QEMU coroutine_fn
> annotations could be (an optional) part of QEMU test suite. Adding
> blocking_fn annotations would make even more sense in this context.
I definitely think static checking of coroutine_fn annotations is the
only way to ensure that the QEMU tree is coroutine safe. I think Stefan
mentioned a bug that occurred previously due to a function that expected
to be called in a coroutine context being called normally.
However, I'm not sure it makes sense to use blocking_fn until the
convert-block series (which currently needs a respin after Stefan's
review) is fully upstreamed. Maybe this patch makes most sense at the
start of that series?
Charlie
next prev parent reply other threads:[~2013-09-06 15:37 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 ` [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a " Gabriel Kerneis
2013-09-06 15:36 ` Charlie Shepherd [this message]
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=5229F68F.8060704@ctshepherd.com \
--to=charlie@ctshepherd.com \
--cc=gabriel@kerneis.info \
--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 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.