From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, famz@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 3/5] coroutines: abort if we try to enter a still-sleeping coroutine
Date: Mon, 20 Nov 2017 08:45:21 -0500 [thread overview]
Message-ID: <20171120134521.GB32161@localhost.localdomain> (raw)
In-Reply-To: <20171120114334.GD4516@stefanha-x1.localdomain>
On Mon, Nov 20, 2017 at 11:43:34AM +0000, Stefan Hajnoczi wrote:
> On Sun, Nov 19, 2017 at 09:46:44PM -0500, Jeff Cody wrote:
> > diff --git a/include/qemu/coroutine_int.h b/include/qemu/coroutine_int.h
> > index 931cdc9..b071217 100644
> > --- a/include/qemu/coroutine_int.h
> > +++ b/include/qemu/coroutine_int.h
> > @@ -56,6 +56,8 @@ struct Coroutine {
> >
> > int scheduled;
> >
> > + int sleeping;
>
> s/int/bool/
>
OK.
> BTW an alternative to adding individual bools is to implement a finite
> state machine for the entire coroutine lifecycle. A single function can
> validate all state transitions:
>
> void check_state_transition(CoState old, CoState new,
> const char *action)
> {
> const char *errmsg = fsm[old][new];
> if (!errmsg) {
> return; /* valid transition! */
> }
>
> fprintf(stderr, "Cannot %s coroutine from %s state\n",
> action, state_name[old]);
> abort();
> }
>
> Specifying fsm[][] forces us to think through all possible state
> transitions. This approach is proactive whereas adding bool flags is
> reactive since it only covers a subset of states that were encountered
> after crashes. I'm not sure if it's worth it though :).
Interesting idea; maybe more for 2.12 instead of 2.11, though?
Jeff
next prev parent reply other threads:[~2017-11-20 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 2:46 [Qemu-devel] [PATCH 0/5] Fix segfault in blockjob race condition Jeff Cody
2017-11-20 2:46 ` [Qemu-devel] [PATCH 1/5] blockjob: do not allow coroutine double entry or entry-after-completion Jeff Cody
2017-11-20 11:16 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-20 13:36 ` Jeff Cody
2017-11-21 10:47 ` Stefan Hajnoczi
2017-11-20 22:25 ` Paolo Bonzini
2017-11-21 12:42 ` Kevin Wolf
2017-11-20 2:46 ` [Qemu-devel] [PATCH 2/5] coroutine: abort if we try to enter coroutine scheduled for another ctx Jeff Cody
2017-11-20 11:28 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-20 13:42 ` Jeff Cody
2017-11-20 2:46 ` [Qemu-devel] [PATCH 3/5] coroutines: abort if we try to enter a still-sleeping coroutine Jeff Cody
2017-11-20 11:43 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-20 13:45 ` Jeff Cody [this message]
2017-11-21 10:17 ` Stefan Hajnoczi
2017-11-20 22:30 ` [Qemu-devel] " Paolo Bonzini
2017-11-20 22:35 ` Jeff Cody
2017-11-20 22:47 ` Paolo Bonzini
2017-11-20 23:08 ` Jeff Cody
2017-11-20 23:13 ` Paolo Bonzini
2017-11-20 23:31 ` Jeff Cody
2017-11-20 2:46 ` [Qemu-devel] [PATCH 4/5] qemu-iotests: add option in common.qemu for mismatch only Jeff Cody
2017-11-20 2:46 ` [Qemu-devel] [PATCH 5/5] qemu-iotest: add test for blockjob coroutine race condition Jeff Cody
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=20171120134521.GB32161@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.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.