 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Information required on TRACE_VMEXIT working.
| To: | "aditya shevalkar" <aditya27783@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Information required on TRACE_VMEXIT working. |
| From: | "George Dunlap " <dunlapg@xxxxxxxxx> |
| Date: | Mon, 27 Nov 2006 09:41:35 -0500 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Mon, 27 Nov 2006 06:41:38 -0800 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=qohrSn6lK+v4Y8UHyB2jJOi1qOJRpVtNYN90/pmgp6hfaVqhtfKESk3gVotqrQE37tfFOMwSGQYfx0LaGLQTyGL8+UvrJc+x3WuMwA4XB3TQTVPGFnetuOwh3h8LsANB4BYu9bq8hopBvpNf5hi1EXtUJKUCY/dmXLQMWfcVyPs= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <de76405a0611270638l547b235cmea8a12a2d5e9140d@xxxxxxxxxxxxxx> |
| 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> |
| References: | <20061127054321.45514.qmail@xxxxxxxxxxxxxxxxxxxxxxxxx> <de76405a0611270638l547b235cmea8a12a2d5e9140d@xxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
When a VMEXIT happens, vmx_trace_vmexit() is called, and a trace record is generated. (This includes an RDTSC timetamp). Then, as the VMEXIT is handled, the various trace_values[] are filled in, depending upon what kind of vmexit it is. Then, just before the next [stupid mailer program...] VMENTER, another trace record is generated with the values in trace_values[]. This turns out to be a pretty powerful profiling and analysis tool; the two RDTSC values can be used to calculate how many cycles Xen spent in the hypervisor for any particular type of VMEXIT. The records are only generated if tracing is actually enabled, of course. See tools/xentrace and xen/public/trace.h for more information. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Information required on TRACE_VMEXIT working., George Dunlap |
|---|---|
| Next by Date: | RE: [Xen-devel] machine check support in HVM guests, Petersson, Mats |
| Previous by Thread: | Re: [Xen-devel] Information required on TRACE_VMEXIT working., George Dunlap |
| Next by Thread: | RE: [Xen-devel] Information required on TRACE_VMEXIT working., Li, Xin B |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
