From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NliWI-00050v-6S
	for qemu-devel@nongnu.org; Sun, 28 Feb 2010 07:45:14 -0500
Received: from [199.232.76.173] (port=46526 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NliWG-00050n-Mo
	for qemu-devel@nongnu.org; Sun, 28 Feb 2010 07:45:12 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <paul@codesourcery.com>) id 1NliWG-0005w3-2k
	for qemu-devel@nongnu.org; Sun, 28 Feb 2010 07:45:12 -0500
Received: from mx20.gnu.org ([199.232.41.8]:63452)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1NliWF-0005vz-Rb
	for qemu-devel@nongnu.org; Sun, 28 Feb 2010 07:45:11 -0500
Received: from mail.codesourcery.com ([38.113.113.100])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1NliWF-00050B-0N
	for qemu-devel@nongnu.org; Sun, 28 Feb 2010 07:45:11 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCHv2 09/12] vhost: vhost net support
Date: Sun, 28 Feb 2010 12:45:07 +0000
References: <cover.1267122331.git.mst@redhat.com>
	<201002280159.27231.paul@codesourcery.com>
	<20100228101509.GB28921@redhat.com>
In-Reply-To: <20100228101509.GB28921@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201002281245.07802.paul@codesourcery.com>
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: amit.shah@redhat.com, quintela@redhat.com, kraxel@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>

> >  There certainly
> > exist machines that can change physical RAM mapping.
> 
> I am talking about mapping between phy RAM offset and qemu virt address.
> When can it change without RAM in question going away?

RAM offset or guest physical address? The two are very different.
Some machines have chip selects that allow given physical address range to be 
mapped to different banks of ram.

Paul