From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57089) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SAXYR-0003Yr-9m for qemu-devel@nongnu.org; Wed, 21 Mar 2012 22:15:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SAXYP-0002TS-MG for qemu-devel@nongnu.org; Wed, 21 Mar 2012 22:15:06 -0400 Received: from ozlabs.org ([203.10.76.45]:34329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SAXYP-0002OR-At for qemu-devel@nongnu.org; Wed, 21 Mar 2012 22:15:05 -0400 From: David Gibson Date: Thu, 22 Mar 2012 13:14:35 +1100 Message-Id: <1332382488-12869-1-git-send-email-david@gibson.dropbear.id.au> Subject: [Qemu-devel] [0/13] RFC: Guest visible IOMMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Here's another version of my series implementing the nevessary framework for emulation of guest-visible IOMMUs. I've incorporated the feedback from the last posting. I'm fairly confident that preliminary patches 1-3 are ready to go in, the rest might still need more consideration. In particular, if anyone has thoughts on how to handle the case where an IOMMU mapping is invalidated by the guest where a qemu-side device currently has that piece of IOVA-space dma_memory_map()ed, I'd be interested to hear it.