qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org, kwolf@redhat.com,
	stefanha@redhat.com, agraf@suse.de
Subject: Re: [Qemu-devel] [RFC 0/2] macio: split out unaligned DMA access into separate functions
Date: Fri, 22 May 2015 13:55:21 -0400	[thread overview]
Message-ID: <555F6D89.4090309@redhat.com> (raw)
In-Reply-To: <1425939893-14404-1-git-send-email-mark.cave-ayland@ilande.co.uk>



On 03/09/2015 06:24 PM, Mark Cave-Ayland wrote:
> This patchset attempts to separate out the IDE/ATAPI logic from the unaligned
> DMA access logic for macio which provides the following benefits:
> 
> 1) Reduced code complexity
> 
> The existing macio IDE/ATAPI functions were becoming extremely difficult to
> follow through the various callbacks. By splitting up the functions in this
> way it becomes much easier to follow the DMA-specific sections of code.
> 
> 2) Future-proofing
> 
> If/when the block layer becomes able to handle unaligned DMA accesses directly
> then it should be possible to switch out pmac_dma_read() and pmac_dma_write()
> with their unaligned-capable bdrv_*() equivalents without having to change any
> other logic.
> 
> 3) Fix intermittent CDROM detection under -M g3beige
> 
> The code refactoring now correctly handles non-block ATAPI transfers which
> fixes the problem with intermittent CDROM detection with Darwin under
> -M g3beige.
> 
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
> 
> 
> Mark Cave-Ayland (2):
>   macio: move unaligned DMA read code into separate pmac_dma_read()
>     function
>   macio: move unaligned DMA write code into separate pmac_dma_write()
>     function
> 
>  hw/ide/macio.c             |  487 +++++++++++++++++++++++---------------------
>  include/hw/ppc/mac_dbdma.h |    4 -
>  2 files changed, 254 insertions(+), 237 deletions(-)
> 

Code fails 32 bit build due to %lx debug prints. I'll edit them
accordingly if that is OK by you.

--js

  parent reply	other threads:[~2015-05-22 17:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 22:24 [Qemu-devel] [RFC 0/2] macio: split out unaligned DMA access into separate functions Mark Cave-Ayland
2015-03-09 22:24 ` [Qemu-devel] [RFC 1/2] macio: move unaligned DMA read code into separate pmac_dma_read() function Mark Cave-Ayland
2015-03-09 22:24 ` [Qemu-devel] [RFC 2/2] macio: move unaligned DMA write code into separate pmac_dma_write() function Mark Cave-Ayland
2015-03-17  7:23 ` [Qemu-devel] [RFC 0/2] macio: split out unaligned DMA access into separate functions Alexander Graf
2015-04-28 20:57   ` Mark Cave-Ayland
2015-04-28 21:07     ` John Snow
2015-04-28 21:13       ` Mark Cave-Ayland
2015-03-17 15:23 ` Stefan Hajnoczi
2015-05-18 19:54 ` John Snow
2015-05-19 20:50   ` Mark Cave-Ayland
2015-05-19 21:01     ` John Snow
2015-05-19 21:17       ` Mark Cave-Ayland
2015-05-22 17:55 ` John Snow [this message]
2015-05-22 18:16   ` Mark Cave-Ayland
2015-05-22 18:20     ` John Snow
2015-05-22 19:52       ` Mark Cave-Ayland
2015-05-31 19:54       ` Mark Cave-Ayland
2015-06-01 15:57         ` John Snow

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=555F6D89.4090309@redhat.com \
    --to=jsnow@redhat.com \
    --cc=agraf@suse.de \
    --cc=kwolf@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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).