From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [ide] Check that asynchronous (DMA) submission succeeds
Date: Sun, 7 Sep 2008 05:16:34 +0100 [thread overview]
Message-ID: <20080907041634.GC813@shareable.org> (raw)
In-Reply-To: <48C340FF.3000503@codemonkey.ws>
Anthony Liguori wrote:
> I'll have to look more closely, but most of the code goes to great
> lengths to use bottom halves to avoid the possibility of infinite
> recursion. The concern with recursion is not CPU consumption, it's that
> you'll eventually overrun the stack and potentially crash the QEMU process.
(Completely unrelated: "qemu -net nic -net user -net user" will
overrun the stack and crash the QEMU process as soon as the guest
makes an external TCP connection.)
-- Jamie
next prev parent reply other threads:[~2008-09-07 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:52 [Qemu-devel] [PATCH] [ide] Check that asynchronous (DMA) submission succeeds Ian Jackson
2008-08-28 20:23 ` Anthony Liguori
2008-08-29 9:41 ` Ian Jackson
2008-09-07 2:48 ` Anthony Liguori
2008-09-07 4:16 ` Jamie Lokier [this message]
2008-08-31 6:42 ` Gleb Natapov
2008-09-01 11:31 ` Ian Jackson
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=20080907041634.GC813@shareable.org \
--to=jamie@shareable.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).