qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: aliguori@us.ibm.com, kraxel@redhat.com
Cc: afaerber@web.de, qemu-devel@nongnu.org, mst@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Preliminaries for DMA/IOMMU support
Date: Wed,  4 Apr 2012 10:15:56 +1000	[thread overview]
Message-ID: <1333498558-20897-1-git-send-email-david@gibson.dropbear.id.au> (raw)

This series contains some preliminary patches to my big DMA series.
This adds support for dma_addr_t type properties and uses that to
convert the usb-xhci to use the existing pci dma wrapper functions.

Changes since last version:
 * Added copyright notice (GPL v2 or later) to qdev-dma.h

             reply	other threads:[~2012-04-04  0:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  0:15 David Gibson [this message]
2012-04-04  0:15 ` [Qemu-devel] [PATCH 1/2] Better support for dma_addr_t variables David Gibson
2012-04-04  0:15 ` [Qemu-devel] [PATCH 2/2] usb-xhci: Use PCI DMA helper functions 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=1333498558-20897-1-git-send-email-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=afaerber@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --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).