|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH] Flush pending AIO on reboot and shutdown. |
Date: | Wed, 13 Aug 2008 19:36:57 +0300 |
User-agent: | Thunderbird 2.0.0.16 (X11/20080723) |
Anthony Liguori wrote:
Avi Kivity wrote:Anthony Liguori wrote:I though about doing it this way, but then I saw that qemu_register_reset() is used for HW reset notification only. I don't think that hw/ide.c is theright place to register the notifier though, so I decided to call it explicitly. Do you think I should do qemu_register_reset() in block.c?But shouldn't the various disk types be the ones to flush their outstanding IO on reset?Do you mean qemu block drivers, or disk controllers?The disk controllers. It's a semantic of the disk controller itself (what happens on reset if there are outstanding requests). Do those requests complete or are the cancelled?
I imagine it depends on the controller, and that they are allowed to drop pending requests. If software wants data on the disk, it should wait for completion.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |