From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Joerg Rodel <Joerg.Rodel@amd.com>,
qemu-devel@nongnu.org, anthony@codemonkey.ws,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 4/8] Add universal DMA helper functions
Date: Mon, 27 Feb 2012 13:55:20 +0200 [thread overview]
Message-ID: <20120227115520.GA8770@localhost> (raw)
In-Reply-To: <20120227103349.GB6731@redhat.com>
On Mon, Feb 27, 2012 at 12:33:49PM +0200, Michael S. Tsirkin wrote:
> On Mon, Feb 27, 2012 at 11:22:43AM +1100, David Gibson wrote:
> > On Sun, Feb 26, 2012 at 12:04:49PM +0200, Michael S. Tsirkin wrote:
> > > On Fri, Feb 24, 2012 at 02:27:39PM +1100, David Gibson wrote:
[snip]
> > >
> > > I'm a bit confused with all the stubbing going on.
> > > Is this the final form of the pci_* functions or just
> > > a stub? If the final form, we probably should just
> > > open-code them - they don't buy us much.
> > > If not, let's add a comment?
> >
> > Well.. it's the intended final form of pci_dma_*() - which do become
> > trivial wrappers, yes.
>
> I'd say let's drop them then (in a follow-up patch). The topic is
> confusing enough without having to wade through layers of wrappers :)
>
Drop them how? Using dma_* stuff directly? That might work, but I
remember others suggesting we should use a specialized PCI wrapper.
Perhaps it makes sense if some other bus, or PCI itself at some point,
needs to do something special.
> > It's _not_ the intended final form of dma_*(),
> > which need to grow code to do actual IOMMU translation. I'll add a
> > comment about this in the next round.
> >
> > --
> > David Gibson | I'll have my music baroque, and my code
> > david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
> > | _way_ _around_!
> > http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-02-27 11:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:27 [Qemu-devel] [0/8] RFC: A second batch of preliminaries towards guest visible IOMMUS David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 1/8] Use DMADirection type for dma_bdrv_io David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 2/8] Better support for dma_addr_t variables David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 3/8] usb-xhci: Use PCI DMA helper functions David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 4/8] Add universal " David Gibson
2012-02-26 10:04 ` Michael S. Tsirkin
2012-02-26 21:09 ` Eduard - Gabriel Munteanu
2012-02-27 0:22 ` David Gibson
2012-02-27 10:33 ` Michael S. Tsirkin
2012-02-27 11:55 ` Eduard - Gabriel Munteanu [this message]
2012-02-26 21:24 ` Eduard - Gabriel Munteanu
2012-02-24 3:27 ` [Qemu-devel] [PATCH 5/8] usb-ohci: Use " David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 6/8] Make sglists and dma_bdrv helpers use new universal DMA herlpers David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 7/8] ide/ahci: Use universal DMA helper functions David Gibson
2012-02-24 3:27 ` [Qemu-devel] [PATCH 8/8] Make dma_addr_t 64 bit always David Gibson
2012-02-24 4:57 ` David Gibson
2012-02-26 21:46 ` Blue Swirl
2012-02-27 12:58 ` David Gibson
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=20120227115520.GA8770@localhost \
--to=eduard.munteanu@linux360.ro \
--cc=Joerg.Rodel@amd.com \
--cc=anthony@codemonkey.ws \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).