From: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
To: Christoph Hellwig <hch@lst.de>
Cc: aliguori@us.ibm.com, sheepdog@lists.wpkg.org,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
fujita.tomonori@lab.ntt.co.jp, avi@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits
Date: Thu, 13 May 2010 04:50:50 +0900 [thread overview]
Message-ID: <4BEB069A.8060707@lab.ntt.co.jp> (raw)
In-Reply-To: <20100512140132.GA11876@lst.de>
On 2010/05/12 23:01, Christoph Hellwig wrote:
> On Wed, May 12, 2010 at 07:46:52PM +0900, MORITA Kazutaka wrote:
>> This patch calls the close handler of the block driver before the qemu
>> process exits.
>>
>> This is necessary because the sheepdog block driver releases the lock
>> of VM images in the close handler.
>>
>> Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
>
> Looks good in principle, except that bdrv_first is gone and has been
> replaced with a real list in the meantime, so this won't even apply.
>
Thank you for your comment.
I'll rebase and resend the updated version in the next days.
Thanks,
Kazutaka
next prev parent reply other threads:[~2010-05-13 3:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:46 [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-12 14:01 ` Christoph Hellwig
2010-05-12 19:50 ` MORITA Kazutaka [this message]
2010-05-12 14:28 ` [Qemu-devel] " Avi Kivity
2010-05-12 20:16 ` MORITA Kazutaka
2010-05-13 2:34 ` MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 2/2] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-12 11:38 ` [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU Kevin Wolf
2010-05-12 19:46 ` MORITA Kazutaka
2010-05-13 14:03 ` MORITA Kazutaka
2010-05-14 8:32 ` Kevin Wolf
2010-05-14 9:54 ` MORITA Kazutaka
2010-05-14 10:05 ` Kevin Wolf
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 0/3] " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-17 11:08 ` Kevin Wolf
2010-05-17 12:19 ` [Qemu-devel] " MORITA Kazutaka
2010-05-17 12:20 ` Kevin Wolf
2010-05-17 13:03 ` MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-14 12:55 ` [Qemu-devel] " Kevin Wolf
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 11:08 ` [Qemu-devel] " Kevin Wolf
2010-05-17 10:34 ` MORITA Kazutaka
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=4BEB069A.8060707@lab.ntt.co.jp \
--to=morita.kazutaka@lab.ntt.co.jp \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).