From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jacob Gorm Hansen <jacobg@diku.dk>
Subject: Is machine_to_phys_mapping a 4MB 'superpage'?
Date: Wed, 30 Mar 2005 19:25:08 -0800
Message-ID: <424B6D94.1080900@diku.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

hi,

The machine_to_phys_mapping table is mapped permanently at 0xFC000000 
(on x86-32). I would like to experiment with letting the domU map it at 
other locations in its virtual address space, but I suppose that for 
performance it is mapped as a 4MB 'super' page, and as such needs 
special treatment, is this correct?

Thanks,
Jacob