From: Kevin Wolf <kwolf@redhat.com>
To: "Gugnani, Shashank" <gugnani.2@buckeyemail.osu.edu>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] Co-routine re-entered recursively
Date: Wed, 11 Oct 2017 14:07:06 +0200 [thread overview]
Message-ID: <20171011120706.GF4593@dhcp-200-186.str.redhat.com> (raw)
In-Reply-To: <CY4PR0101MB291815E29308B3C75D26876FE9740@CY4PR0101MB2918.prod.exchangelabs.com>
[ Cc: qemu-block ]
Am 09.10.2017 um 21:11 hat Gugnani, Shashank geschrieben:
> Hi,
>
> I'm trying to modify the NVMe emulator in QEMU to use multiple threads.
>
> After making necessary changes, I see this error: 'Co-routine re-entered recursively'
>
> Can anybody tell me the reason for this error? Is there anything I can do to fix this issue?
I suspect that you need to fix your locking. Are you sure you're holding
the AioContext locks while you're making requests to the block layer?
Kevin
next prev parent reply other threads:[~2017-10-11 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 19:11 [Qemu-devel] Co-routine re-entered recursively Gugnani, Shashank
2017-10-11 12:07 ` Kevin Wolf [this message]
2017-10-13 21:17 ` Gugnani, Shashank
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=20171011120706.GF4593@dhcp-200-186.str.redhat.com \
--to=kwolf@redhat.com \
--cc=gugnani.2@buckeyemail.osu.edu \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).