From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LpQm7-0004Ny-TK
	for qemu-devel@nongnu.org; Thu, 02 Apr 2009 13:32:23 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LpQm3-0004LX-CV
	for qemu-devel@nongnu.org; Thu, 02 Apr 2009 13:32:23 -0400
Received: from [199.232.76.173] (port=42853 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LpQm3-0004LR-7U
	for qemu-devel@nongnu.org; Thu, 02 Apr 2009 13:32:19 -0400
Received: from mail-bw0-f172.google.com ([209.85.218.172]:59564)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1LpQm2-0004D3-MD
	for qemu-devel@nongnu.org; Thu, 02 Apr 2009 13:32:18 -0400
Received: by bwz20 with SMTP id 20so568122bwz.34
	for <qemu-devel@nongnu.org>; Thu, 02 Apr 2009 10:32:17 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <1238684238.18745.17.camel@nibbler.dlib.indiana.edu>
References: <1238684238.18745.17.camel@nibbler.dlib.indiana.edu>
Date: Thu, 2 Apr 2009 20:32:17 +0300
Message-ID: <f43fc5580904021032m390a4dd6h16435e393b09f2b6@mail.gmail.com>
Subject: Re: [Qemu-devel] PATCH/RFC: PCI memory mapping
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Tristan Gingold <gingold@adacore.com>

On 4/2/09, Brian Wheeler <bdwheele@indiana.edu> wrote:
> [first off, if there's an easier way to do this, let me know!]
>
>  This patch adds an address mapping function to the PCI bus so the host
>  chipset can remap PCI generated addresses to the appropriate physical
>  addresses.

This discussion has come up many, many times, but finally the design
was settled to the current dma API. It supports resolving guest
addresses to host pointers, so  that part should be extended instead
of adding new functionality. We want (one day) zero copy DMA even with
IOMMU.