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

[Xen-devel] [HVM][XENOPROFILE][PATCH][0/4] Xenoprofile support for HVM guests

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Woller, Thomas" <thomas.woller@xxxxxxx>
  • Date: Thu, 19 Oct 2006 17:28:54 -0500
  • Delivery-date: Thu, 19 Oct 2006 15:29:34 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbzzfXBa8dhg91dRNetefkD1UQyEA==
  • Thread-topic: [HVM][XENOPROFILE][PATCH][0/4] Xenoprofile support for HVM guests

The following 4 patches replace the previous Xenoprofile passive
profiling patches posted to xen-devel.

These modifications provide proper mode and eip/rip for the oprofile
logic if the NMI occurs during the HVM guest context.

You must use oprofile 0.9.2 with the addition of Renato Santos' patch
from here:

The athlon oprofile NMI handler now checks for a specific eip/rip to
determine if the
NMI occurred in the context of the guest.
1) NMI occurs in context of guest
2) NMI causes vmexit (NMI intercepted)
3) NMI held pending until STGI instruction
4) STGI instruction executes causing NMI on instruction immediately
5) NMI handler in op_module_athlon.c checks label of code after STGI
6) if eip/rip matches then call specific xenoprofile code instead of
   mainline oprofiling code.

This redesign is basically Kier's, thanks for the rework :)

Additional input and assistance from Rento Santos and Mats Petersson.

This code has been tested on AMD-V 32bit and 64bit hypervisors, with
32bit and 64bit HVM guests.

The code has not been fully verified on a VT box (patch 4/4).

Xen-devel mailing list



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