From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Vrable Subject: Full Shadow Mode and phys_to_machine_mapping Date: Mon, 21 Feb 2005 13:29:04 -0800 Message-ID: <20050221212904.GA4689@vrable.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org I'm trying to figure out how full shadow mode is implemented; I understand that this only works with VMX support at the moment. The phys_to_machine_mapping function is giving me a bit of trouble. This function seems to be used to look up an entry in the PFN-to-MFN mapping table, which as I understand it for full shadow mode should be maintained by Xen instead of the domain. This table can be up to 4 MB in size. __phys_to_machine_mapping is set to point at the per-domain virtual memory area. Isn't this area already used for per-domain GDT/LDT mappings, leaving no room for the PFN-to-MFN table? I haven't been able to find where in the code the PFN-to-MFN table is ever initialized, either. What am I missing? --Michael Vrable ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click