From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-block@nongnu.org
Cc: hare@suse.de, stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] ide: unify io_buffer_offset increments
Date: Tue, 8 Sep 2015 12:01:38 -0400 [thread overview]
Message-ID: <55EF0662.60703@redhat.com> (raw)
In-Reply-To: <55EDBD4F.7070204@redhat.com>
On 09/07/2015 12:37 PM, Paolo Bonzini wrote:
>
>
> On 26/08/2015 01:45, John Snow wrote:
>> IDEState's io_buffer_offset was originally added to keep track of offsets
>> in AHCI rather exclusively, but it was added to IDEState instead of an
>> AHCI-specific structure.
>
> Interesting to see something weird turn into feature. :)
>
There's lots of stuff in places where it doesn't really belong in the
IDE universe, so it takes a while to sift through all the usages and
start to straighten it all out.
> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
>
Grazie.
>> AHCI fakes all PIO transfers using DMA and a scatter-gather list. When
>> the core or atapi layers invoke HBA-specific mechanisms for transfers,
>> they do not always know that it is being backed by DMA or a sglist, so
>> this offset is not always updated by the HBA code everywhere.
>>
>> If we modify it in dma_buf_commit, however, any HBA that needs to use
>> this offset to manage operating on only part of a sglist will have
>> access to it.
>>
>> This will fix ATAPI PIO transfers performed through the AHCI HBA,
>> which were previously not modifying this value appropriately.
>>
>> This will fix ATAPI PIO transfers larger than one sector.
>
Thanks, applied to my IDE tree:
https://github.com/jnsnow/qemu/commits/ide
https://github.com/jnsnow/qemu.git
--js
prev parent reply other threads:[~2015-09-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 23:45 [Qemu-devel] [PATCH 0/1] ahci: fix ATAPI PIO John Snow
2015-08-25 23:45 ` [Qemu-devel] [PATCH 1/1] ide: unify io_buffer_offset increments John Snow
2015-09-07 16:37 ` Paolo Bonzini
2015-09-08 16:01 ` John Snow [this message]
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=55EF0662.60703@redhat.com \
--to=jsnow@redhat.com \
--cc=hare@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.