From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Winchell Subject: Re: Overhead incurred due to Xen for a page fault Date: Fri, 24 Mar 2006 10:27:33 -0500 Message-ID: <44240FE5.9090902@virtualiron.com> References: <032420060427.4189.442375210007CE670000105D2207024553CCCCCC050E9F@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <032420060427.4189.442375210007CE670000105D2207024553CCCCCC050E9F@comcast.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: pak333@comcast.net Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Fault path: vmx_vmexit_handler vmx_do_page_fault shadow_fault (shadow_fault_64) Put memory based trace code in shadow_fault_64, or, I presume, shadow_fault_32. You'll see shadow_fault_64 get entered multiple times. I believe the faults are as follows: 1. The data page fault. 2. The fault for the gos accessing the pte. 3. The second fault for the data page. This is for fully virtualized mode. I have not been looking at paravirtualized. I see page fault times at 20-25 usec. regards, Dave pak333@comcast.net wrote: > I would like to get some help on estimating the cost of page fault > handling in Xen. Can someone help me identify where I need to put the > hooks into the xen source. > > Thanks > Kris > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > >