qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] block: Avoid direct AIO callback
Date: Fri, 10 Jun 2011 12:32:43 -0300	[thread overview]
Message-ID: <20110610123243.0b12b24c@doriath> (raw)
In-Reply-To: <1307456313-9884-1-git-send-email-kwolf@redhat.com>

On Tue,  7 Jun 2011 16:18:30 +0200
Kevin Wolf <kwolf@redhat.com> wrote:

> This series fixes some cases of block drivers calling AIO callbacks too early.
> It fixes the IDE assertion failure reported by Luiz (in error cases, the DMA
> status, including acb, could first be reset in the callback and only then be
> set by the caller, resulting in a dangling acb and wrong status register value).

This fixes the reported bug, thanks.

I know this is a different subject, but I'm still unable to use the host cdrom
if the -snapshot flag is passed, I think the idea of ignoring the flag for a
read-only device would fix this, no?

> 
> Kevin Wolf (3):
>   qcow2: Avoid direct AIO callback
>   qcow: Avoid direct AIO callback
>   vdi: Avoid direct AIO callback
> 
>  block/qcow.c  |   58 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  block/qcow2.c |   39 +++++++++++++++++++++++++++++--------
>  block/vdi.c   |   40 +++++++++++++++++++++++++++++++++++---
>  3 files changed, 122 insertions(+), 15 deletions(-)
> 

  parent reply	other threads:[~2011-06-10 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 14:18 [Qemu-devel] [PATCH 0/3] block: Avoid direct AIO callback Kevin Wolf
2011-06-07 14:18 ` [Qemu-devel] [PATCH 1/3] qcow2: " Kevin Wolf
2011-06-07 14:18 ` [Qemu-devel] [PATCH 2/3] qcow: " Kevin Wolf
2011-06-07 14:18 ` [Qemu-devel] [PATCH 3/3] vdi: " Kevin Wolf
2011-06-15 12:39   ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2011-06-10 15:32 ` Luiz Capitulino [this message]
2011-06-10 15:57   ` [Qemu-devel] [PATCH 0/3] block: " Kevin Wolf

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=20110610123243.0b12b24c@doriath \
    --to=lcapitulino@redhat.com \
    --cc=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).