From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: qemu-devel@nongnu.org, Joerg.Rodel@amd.com,
benh@kernel.crashing.org, aik@ozlabs.ru, agraf@suse.de,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] Supporting emulation of IOMMUs
Date: Sat, 14 May 2011 18:27:46 +0300 [thread overview]
Message-ID: <20110514152746.GA2951@localhost> (raw)
In-Reply-To: <20110510014426.GA12722@yookeroo.fritz.box>
On Tue, May 10, 2011 at 11:44:26AM +1000, David Gibson wrote:
> On Thu, Apr 21, 2011 at 09:47:31PM +0300, Eduard - Gabriel Munteanu wrote:
> > On Thu, Apr 21, 2011 at 05:03:47PM +1000, David Gibson wrote:
> > > A few months ago, Eduard - Gabriel Munteanu posted a series of patches
> > > implementing support for emulating the AMD PCI IOMMU
> > > (http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg03196.html).
> > >
> > > In fact, this series implemented a general DMA/IOMMU layer which can
> > > be used by any device model, and one translation backend for this
> > > implementing the AMD specific PCI IOMMU.
> > >
> > > These patches don't seem to have gone anywhere for the last few
> > > months, however, and so far I've been unable to contact the author
> > > (trying again with this mail).
> > >
> > > I have an interest in this code, because the pSeries machine will also
> > > need IOMMU emulation support. At present we only support virtual
> > > devices, through the PAPR interface, and we have support for the
> > > hypervisor-controller IOMMU translation in the PAPR VIO code.
> > > However, we want to add PCI device support and this will also need
> > > IOMMU translation.
> > >
> > > The series seems to have the right basic approach, so if the author is
> > > indeed MIA, I was planning to pick up the patches and resubmit them
> > > (with support for the pSeries IOMMU added).
> >
> > Hi,
> >
> > Not really MIA, but I've been a bit busy lately, so I'm sorry if I
> > couldn't answer your mail in a timely fashion.
> >
> > I'll try making another merge attempt tonight/tomorrow.
>
> Ok. Did this happen? Sorry, I've been away the last couple of weeks
> - I had a google at the qemu-devel archives but couldn't spot a new
> merge, but did I just not look hard enough?
[snip]
No, I've made some progress but I've still got a few concerns to
address, mainly how to handle unaligned accesses and some things related
to the IOMMU behavior like target aborts.
I've added some macro magic to declare bus-specific interfaces and
converted PCI devices to use pci_memory_*().
I'll try not to hold this back too much, but I can't make promises wrt
timing.
Eduard
next prev parent reply other threads:[~2011-05-14 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 7:03 [Qemu-devel] Supporting emulation of IOMMUs David Gibson
2011-04-21 9:39 ` Alexander Graf
2011-04-28 21:57 ` Richard Henderson
2011-04-29 14:27 ` Richard Henderson
2011-05-09 3:28 ` David Gibson
2011-05-09 2:06 ` David Gibson
2011-05-09 2:05 ` David Gibson
2011-04-21 18:47 ` Eduard - Gabriel Munteanu
2011-05-10 1:44 ` David Gibson
2011-05-14 15:27 ` Eduard - Gabriel Munteanu [this message]
2011-05-14 23:16 ` Benjamin Herrenschmidt
2011-04-26 15:58 ` Joerg Roedel
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=20110514152746.GA2951@localhost \
--to=eduard.munteanu@linux360.ro \
--cc=Joerg.Rodel@amd.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=benh@kernel.crashing.org \
--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).