From: John Snow <jsnow@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Aurelien Jarno <aurelien@aurel32.net>
Cc: agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2] macio: handle non-block ATAPI DMA transfers the same as block DMA transfers
Date: Mon, 24 Aug 2015 11:43:42 -0700 [thread overview]
Message-ID: <55DB65DE.5090704@redhat.com> (raw)
In-Reply-To: <55D7CC27.1080901@ilande.co.uk>
On 08/21/2015 06:11 PM, Mark Cave-Ayland wrote:
> On 21/08/15 20:04, John Snow wrote:
>
> (lots cut)
>
>> Do you want to resend the V3 here directly to the ML with Aurelien
>> Jarno's R-B?
>
> I was actually looking at this yesterday, and it seems with some more
> testing that only the DBDMA flush part is required. It could be that
> fixing the flush semantics prevents the macio device getting into the
> incorrect state that makes the macio patch necessary in the first place.
>
> In this case the DBDMA patch should probably go via Alex since it's
> fairly specific to the Mac DMA hardware rather than being related just
> to the IDE interface.
>
>
> ATB,
>
> Mark.
>
Even better! 8-)
Thanks,
--js
prev parent reply other threads:[~2015-08-24 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 16:54 [Qemu-devel] [PATCHv2] macio: handle non-block ATAPI DMA transfers the same as block DMA transfers Mark Cave-Ayland
2015-08-01 18:33 ` Aurelien Jarno
2015-08-01 18:54 ` Mark Cave-Ayland
2015-08-03 17:01 ` John Snow
2015-08-13 22:03 ` Mark Cave-Ayland
2015-08-13 22:59 ` John Snow
2015-08-17 20:39 ` Aurelien Jarno
2015-08-21 19:04 ` John Snow
2015-08-22 1:11 ` Mark Cave-Ayland
2015-08-24 18:43 ` 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=55DB65DE.5090704@redhat.com \
--to=jsnow@redhat.com \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=mark.cave-ayland@ilande.co.uk \
--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).