From: Kevin Wolf <kwolf@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qcow2: Unlock during COW
Date: Wed, 23 Nov 2011 18:01:09 +0100 [thread overview]
Message-ID: <4ECD26D5.4040501@redhat.com> (raw)
In-Reply-To: <1321293318-19177-1-git-send-email-kwolf@redhat.com>
Am 14.11.2011 18:55, schrieb Kevin Wolf:
> Unlocking during COW allows for more parallelism. One change it requires is
> that buffers are dynamically allocated instead of just using a per-image
> buffer.
>
> While touching the code, drop the synchronous qcow2_read() function and replace
> it by a bdrv_read() call.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This seems to break an IDE guest for me. I don't quite understand why
yet, but maybe someone has an idea.
hw/ide/pci.c:313: bmdma_cmd_writeb: Assertion `bm->bus->dma->aiocb ==
((void *)0)' failed.
Kevin
next prev parent reply other threads:[~2011-11-23 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 17:55 [Qemu-devel] [PATCH v2] qcow2: Unlock during COW Kevin Wolf
2011-11-15 12:07 ` Stefan Hajnoczi
2011-11-23 17:01 ` Kevin Wolf [this message]
2012-05-05 0:21 ` Marc-André Lureau
2012-05-05 3:17 ` Zhi Yong Wu
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=4ECD26D5.4040501@redhat.com \
--to=kwolf@redhat.com \
--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).