From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41148) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0lpI-0001IG-3o for qemu-devel@nongnu.org; Thu, 23 Feb 2012 22:28:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S0lpG-0001H0-Nq for qemu-devel@nongnu.org; Thu, 23 Feb 2012 22:28:08 -0500 Received: from ozlabs.org ([203.10.76.45]:36306) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S0lpG-0001Gl-DB for qemu-devel@nongnu.org; Thu, 23 Feb 2012 22:28:06 -0500 From: David Gibson Date: Fri, 24 Feb 2012 14:27:35 +1100 Message-Id: <1330054063-16860-1-git-send-email-david@gibson.dropbear.id.au> Subject: [Qemu-devel] [0/8] RFC: A second batch of preliminaries towards guest visible IOMMUS List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: anthony@codemonkey.ws Cc: qemu-devel@nongnu.org Before qemu 1.0 there was some discussion, and several patch series proposed for adding support for guest visible IOMMU emulation to qemu. No agreement was reached on how to do this, but a patch series did go in preparation - a conversion of most existing PCI devices to use helper functions for their DMA which could be converted to do IOMMU translation in one place. This patch series is a further set of preliminaries, generalizing these wrapper functions to support non-PCI functions, and using this to convert several more drivers. It also introduces the concept of a DMAContext, describing a DMA address space. With this series the only one supported is NULL, meaning "no translation". However, this provides a place that we can put the necessary callback information to support IOMMU translation. If this series doesn't attract too many screams, I'll fold in feedback and repost for inclusion.