From: Artyom Tarasenko <atar4qemu@gmail.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/8] sun4m : sparc32_dma tidy-ups
Date: Tue, 10 Oct 2017 10:21:59 +0200 [thread overview]
Message-ID: <CACXAS8CO9K4967T_BdShaNGpznSDXWCYdsBa43mwdvBHh=KZng@mail.gmail.com> (raw)
In-Reply-To: <1507583223-14819-1-git-send-email-mark.cave-ayland@ilande.co.uk>
On Mon, Oct 9, 2017 at 11:06 PM, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
> This patchset aims to tidy-up the sparc32_dma code by improving the
> modelling of the espdma/ledma devices using both QOM and the memory
> API which didn't exist when the code was first written.
>
> The result is that it is now possible to remove both the iommu_opaque
> and is_ledma workarounds from the code.
>
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Reviewed-by: Artyom Tarasenko <atar4qemu@gmail.com>
>
> Mark Cave-Ayland (8):
> sparc32_dma: rename SPARC32_DMA type to SPARC32_DMA_DEVICE
> sparc32_dma: split esp and le into separate DMA devices
> sparc32_dma: move type declarations from sparc32_dma.c to
> sparc32_dma.h
> sun4m: move DMA device wiring from sparc32_dma_init() to
> sun4m_hw_init()
> sun4m_iommu: move TYPE_SUN4M_IOMMU declaration to sun4m.h
> sparc32_dma: use object link instead of qdev property to pass IOMMU
> reference
> sparc32_dma: introduce new SPARC32_DMA type container object
> sparc32_dma: remove is_ledma hack and replace with memory region
> alias
>
> hw/dma/sparc32_dma.c | 165 ++++++++++++++++++++++++++--------------
> hw/dma/sun4m_iommu.c | 14 ----
> hw/sparc/sun4m.c | 40 +++++-----
> include/hw/sparc/sparc32_dma.h | 49 ++++++++++++
> include/hw/sparc/sun4m.h | 16 ++++
> 5 files changed, 194 insertions(+), 90 deletions(-)
>
> --
> 1.7.10.4
>
--
Regards,
Artyom Tarasenko
SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu
next prev parent reply other threads:[~2017-10-10 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 21:06 [Qemu-devel] [PATCH 0/8] sun4m : sparc32_dma tidy-ups Mark Cave-Ayland
2017-10-09 21:06 ` [Qemu-devel] [PATCH 1/8] sparc32_dma: rename SPARC32_DMA type to SPARC32_DMA_DEVICE Mark Cave-Ayland
2017-10-09 21:06 ` [Qemu-devel] [PATCH 2/8] sparc32_dma: split esp and le into separate DMA devices Mark Cave-Ayland
2017-10-09 21:06 ` [Qemu-devel] [PATCH 3/8] sparc32_dma: move type declarations from sparc32_dma.c to sparc32_dma.h Mark Cave-Ayland
2017-10-09 21:06 ` [Qemu-devel] [PATCH 4/8] sun4m: move DMA device wiring from sparc32_dma_init() to sun4m_hw_init() Mark Cave-Ayland
2017-10-09 21:07 ` [Qemu-devel] [PATCH 5/8] sun4m_iommu: move TYPE_SUN4M_IOMMU declaration to sun4m.h Mark Cave-Ayland
2017-10-09 21:07 ` [Qemu-devel] [PATCH 6/8] sparc32_dma: use object link instead of qdev property to pass IOMMU reference Mark Cave-Ayland
2017-10-09 21:07 ` [Qemu-devel] [PATCH 7/8] sparc32_dma: introduce new SPARC32_DMA type container object Mark Cave-Ayland
2017-10-09 21:07 ` [Qemu-devel] [PATCH 8/8] sparc32_dma: remove is_ledma hack and replace with memory region alias Mark Cave-Ayland
2017-10-09 22:23 ` [Qemu-devel] [PATCH 0/8] sun4m : sparc32_dma tidy-ups no-reply
2017-10-10 6:33 ` Mark Cave-Ayland
2017-10-10 8:21 ` Artyom Tarasenko [this message]
2017-10-14 17:56 ` Mark Cave-Ayland
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='CACXAS8CO9K4967T_BdShaNGpznSDXWCYdsBa43mwdvBHh=KZng@mail.gmail.com' \
--to=atar4qemu@gmail.com \
--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).