[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Information required on TRACE_VMEXIT working.


  • To: "aditya shevalkar" <aditya27783@xxxxxxxxxxx>
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.