[Xen-devel] Is machine_to_phys_mapping a 4MB 'superpage'?

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] Is machine_to_phys_mapping a 4MB 'superpage'?
From:	Jacob Gorm Hansen <jacobg@xxxxxxx>
Date:	Wed, 30 Mar 2005 19:25:08 -0800
Delivery-date:	Thu, 31 Mar 2005 03:25:55 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mozilla Thunderbird 1.0 (X11/20050302)

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 atother locations in its virtual address space, but I suppose that forperformance it is mapped as a 4MB 'super' page, and as such needsspecial treatment, is this correct?


Thanks,
Jacob

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel