From: Jason Baron <jbaron@redhat.com>
To: anthony@codemonkey.ws, benh@kernel.crashing.org
Cc: mst@redhat.com, jan.kiszka@siemens.com, armbru@redhat.com,
qemu-devel@nongnu.org, yamahata@valinux.co.jp,
alex.williamson@redhat.com, ddutile@redhat.com, afaerber@suse.de
Subject: [Qemu-devel] [PATCH 0/3] iommu: isa dma engine support
Date: Wed, 20 Jun 2012 16:11:00 -0400 [thread overview]
Message-ID: <cover.1340220655.git.jbaron@redhat.com> (raw)
Hi,
Based on Benjamin Herrenschmidt's iommu series - these patches provide
infrastructure for a chipset topology where an iommu can sit between
main memory and the isa dma engine. The idea is remap addresses according
to the iommu's wish when we are performing a dma engine r/w operation.
Since the iommu context is tied to the isa device structure, it can be set
independently of the bus on which the isa device resides. Thus, I'm hoping that
this patchset allows us to correctly model more complex chipset topologies.
Thanks,
-Jason
Jason Baron (3):
iommu: remove extra 'typedef struct DMAContext'
iommu: add support for the isa dma engine
iommu: add generic mapping support for the isa bus
dma.h | 5 ++---
hw/cs4231a.c | 2 +-
hw/dma.c | 19 ++++++++++++-------
hw/fdc.c | 10 +++++-----
hw/gus.c | 2 +-
hw/isa-bus.c | 14 ++++++++++++++
hw/isa.h | 9 ++++++++-
hw/sb16.c | 4 ++--
hw/sun4m.c | 2 +-
hw/sun4u.c | 2 +-
10 files changed, 47 insertions(+), 22 deletions(-)
next reply other threads:[~2012-06-20 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 20:11 Jason Baron [this message]
2012-06-20 20:11 ` [Qemu-devel] [PATCH 1/3] iommu: remove extra 'typedef struct DMAContext' Jason Baron
2012-06-22 2:02 ` Benjamin Herrenschmidt
2012-06-20 20:11 ` [Qemu-devel] [PATCH 2/3] iommu: add support for the isa dma engine Jason Baron
2012-06-20 20:11 ` [Qemu-devel] [PATCH 3/3] iommu: add generic mapping support for the isa bus Jason Baron
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=cover.1340220655.git.jbaron@redhat.com \
--to=jbaron@redhat.com \
--cc=afaerber@suse.de \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=ddutile@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).