This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] RE: [PATCH] Xenoprof passive domain support fixes

To: "Ray Bryant" <raybry@xxxxxxxxxxxxxxxxx>, "DaSilva, Rosilmildo" <rosilmildo.dasilva@xxxxxxx>
Subject: RE: [Xen-devel] RE: [PATCH] Xenoprof passive domain support fixes
From: "Woller, Thomas" <thomas.woller@xxxxxxx>
Date: Fri, 14 Jul 2006 13:37:26 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Yang, Xiaowei" <xiaowei.yang@xxxxxxxxx>, "Santos, Jose Renato G" <joserenato.santos@xxxxxx>
Delivery-date: Fri, 14 Jul 2006 12:10:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200607140942.08529.raybry@xxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acana0SJt514JXFGRwyE0VylDawhdQABwb3w
Thread-topic: [Xen-devel] RE: [PATCH] Xenoprof passive domain support fixes
Attached patch is what we have been using internally to allow HVM guest
profiling on 64bit hv with 32bit hvm guest. Code generated by Rosimildo.
This patch is experimental and not ready for inclusion into any repo,
but might help with the next set of patches for xenoprofile support.
This patch has oprofile, SVM, VT and HVM modifications all rolled into
one inclusive patch file. For SVM, if you modify opd_kernel.c image
start/end addresses in oprofile 0.9.1 then 64bit samples seem to work.
VT does not seem to work with attached patch, but we haven't spent time
debugging why.
1) move SVM global interrupt to vmexit handler
2) add VGCF_hvm_guest_nmi flag to guest context to distinguish nmi
occuring in guest rather than in host
3) oprofile model files modified to use the new VGCF_hvm_guest_nmi flag
to determine a bit more properly the mode


Attachment: hvm_mode_fix_profile.patch
Description: hvm_mode_fix_profile.patch

Xen-devel mailing list