From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, wenchaoqemu@gmail.com,
stefanha@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2.1 1/3] blockjob: Fix recent BLOCK_JOB_READY regression
Date: Wed, 02 Jul 2014 10:05:02 -0600 [thread overview]
Message-ID: <53B42DAE.2010000@redhat.com> (raw)
In-Reply-To: <53B41F33.7080904@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On 07/02/2014 09:03 AM, Paolo Bonzini wrote:
>>>> What if an underlying device doesn't support [rw]error=stop? Not all
>>>> do...
>>>
>>> Then the "fix" is to add support to the underlying device. IDE, SCSI
>>> and virtio-blk (plus virtio-scsi via SCSI of course) are covered;
>>
>> Where "covered" means "device model calls bdrv_error_action() somewhere"
>> rather than "device model calls bdrv_error_action() exactly when it
>> should".
>>
>> Case in point: SCSI calls it when UNMAP fails, but IDE doesn't call it
>> when TRIM fails. IDE and virtio-blk call it for I/O beyond the end of
>> the medium, but SCSI doesn't.
>>
>> This is of course fixable. I'm working on it.
>>
>>> the
>>> main one that's left out is SD.
>>
>> Qdevified devices with a qdev_prop_drive: isa-fdc, sysbus-fdc,
>> SUNW,fdtwo, nand, onenand, cfi.pflash01, cfi.pflash02, spapr-nvram,
>> scsi-generic, nvme. SD isn't in this list, because it still hasn't been
>> qdevified. There may be more.
>
> I think there is a page with unfinished transition. Can you add this one?
Listed: http://wiki.qemu.org/CodeTransitions#Reliable_block_job_polling
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-02 16:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:24 [Qemu-devel] [PATCH v2 2.1 0/3] Fix two recent event regressions Markus Armbruster
2014-06-27 17:24 ` [Qemu-devel] [PATCH v2 2.1 1/3] blockjob: Fix recent BLOCK_JOB_READY regression Markus Armbruster
2014-07-01 17:08 ` Eric Blake
2014-07-01 17:10 ` Paolo Bonzini
2014-07-02 6:55 ` Markus Armbruster
2014-07-02 8:23 ` Paolo Bonzini
2014-07-02 8:44 ` Kevin Wolf
2014-07-02 8:59 ` Paolo Bonzini
2014-07-02 14:58 ` Markus Armbruster
2014-07-02 15:03 ` Paolo Bonzini
2014-07-02 16:05 ` Eric Blake [this message]
2014-07-03 7:19 ` Markus Armbruster
2014-07-03 9:25 ` Paolo Bonzini
2014-07-03 15:06 ` Markus Armbruster
2014-06-27 17:24 ` [Qemu-devel] [PATCH v2 2.1 2/3] blockjob: Fix recent BLOCK_JOB_ERROR regression Markus Armbruster
2014-07-01 14:42 ` Wenchao Xia
2014-07-01 16:46 ` Paolo Bonzini
2014-07-02 6:46 ` Markus Armbruster
2014-07-02 8:20 ` Paolo Bonzini
2014-06-27 17:24 ` [Qemu-devel] [PATCH v2 2.1 3/3] docs/qmp: Fix documentation of BLOCK_JOB_READY to match code Markus Armbruster
2014-06-27 17:42 ` Luiz Capitulino
2014-07-01 17:12 ` Eric Blake
2014-07-02 6:49 ` Markus Armbruster
2014-07-02 8:48 ` Kevin Wolf
2014-07-02 7:55 ` Paolo Bonzini
2014-06-27 18:37 ` [Qemu-devel] [PATCH v2 2.1 0/3] Fix two recent event regressions 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=53B42DAE.2010000@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wenchaoqemu@gmail.com \
/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).