similar to: [HVM][XENOPROFILE][PATCH][1/4] remove do_nmi() from AMD-V vmexit handler

Keir, The following 3 patches allow HVM (SVM and VT) guests to be passively profiled using the very latest patches from Renato. These patches apply to 11470. Renato''s patches: http://xenoprof/sourceforge.net oprofile-0.9.1-xen-r2.patch And also a patch not posted FAIK (oprofile-0.9.1-fix-hvm-addr-overlap.patch) which is in the attached tar.bz2 file. hvm_xenoprofile_1.patch - The first

second patch (SVM) for hvm xenoprofile support. Applies cleanly to 11470. Signed-off-by: Tom Woller <thomas.woller@amd.com> Please apply to xen-unstable.hg. hvm_xenoprofile_2.patch - The second patch adds the actual xenoprofile fixes for SVM: 1) hvm function (svm_oprofile_get_eip()) This new hvm table function is called from the op_module_athlon.c code, and returns the proper eip and

Add xenoprofile function to oprofile to obtain the mode, adding check for hvm guest. Applies cleanly to xen-unstable c/s 11831. Please apply to xen-unstable.hg. We also want these patches to be in a 3.0.3-1 base whenever that is branched. Signed-off-by: Tom Woller <thomas.woller@amd.com> --Tom _______________________________________________ Xen-devel mailing list

Third patch (VT) for hvm xenoprofile support. Applies cleanly to 11470. Signed-off-by: Tom Woller <thomas.woller@amd.com> Please apply to xen-unstable.hg. hvm_xenoprofile_3.patch - The third patch adds the actual xenoprofile fixes for VT: I checked (verified by Renato), that the VT traces look ok also. There is some code that I am unsure about in the vmx_oprofile_get_eip(): i.e using the

These two patches affect the interrupt injection logic for AMD-V (only). These patches fix issues with Windows HVM guests during boot menu screen: 1) the timer countdown is no longer very slow 2) kbd response is now no longer slow or non-existent We have also seen an occasional "dma lost interrupt"/expiry errors, and these patches seem to help with these, especially with SUSE10 HVM

Patch 2/2 - Add flag to indicate that an exception event needs injecting, and to delay the ext interrupt injection. Remove unnecessary check of RFLAGS.IF for ExtInt injection. Applies cleanly to xen-unstable c/s 11831. Please apply to xen-unstable.hg. We would also want this patch to be in a 3.0.3-1 base whenever that is branched. Signed-off-by: Travis Betak <travis.betak@amd.com>

Cleanup vmx vmexit handler. Current code doesn''t handle vmexits caused by triple fault, INIT, SIPI, etc, which are listed in IA32 Architecture System Programming Guide 2, Appendix I VMX Basic Exit Reasons, and calls __hvm_bug() when not handling such cases, actually domain crash should be good enough. Also various coding style cleanups. Signed-off-by: Xin Li <xin.b.li@intel.com>

The self_nmi() code cause''s an NMI to be triggered by sending an APIC message to the local processor. However, NMIs are blocked by the VMEXIT, until the next iret or VMENTER. Volume 3 Chapter 27 Section 1 of the Intel SDM states: An NMI causes subsequent NMIs to be blocked, but only after the VM exit completes. As a result, as soon as the VMENTER happens, an immediate VMEXIT happens

Correct compile time compare of CONFIG_PAGING_LEVELS for 64bit and 32bit PAE guests. This code affects accesses to the CR4 register by the SVM guest. Applies cleanly to 10729 + posted NMI/STGI SVM patch. Please apply to xen-unstable.hg. Signed-off-by: Tom Woller <thomas.woller@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Renato, If one creates an HVM domain (say domain 1) and then does echo 1 > /dev/oprofile/passive_domains one then gets the following on the Xen serial console: (XEN) xenoprof.c:143:d0 xenoprof/x86 with autotranslated mode enabledisn''t supported yet (XEN) xenoprof.c:143:d0 xenoprof/x86 with autotranslated mode enabledisn''t supported yet (XEN) xenoprof.c:143:d0

Remove visibility of the FFXSR CPUID bit to an HVM guest. This patch allows HVM Windows x64 to install/boot on AMD-V platforms. This patches applies cleanly to xen-unstable 13743. Please apply to xen-unstable/3.0.5. If possible, pls apply to xen-3.0.4-testing. --Tom thomas.woller@amd.com AMD Corporation 5204 E. Ben White Blvd. UBC1 Austin, Texas 78741 +1-512-602-0059

Hi, Lately I was puzzled by a vmexit reason 31 which was defined as EXIT_REASON_MSR_READ I allocated an array in xen data section and assigned its MFN to an EPT entry of a domainU, I thought the domU could access this array but after that the domainU crashed and xen gave me this exit reason "Bad vmexit (reason 31)" But there is nothing to do with MSR READ, so I''m confused...

Hi All, I am trying to provide services to guest VMs where I wish to run guest VMs in a loop. I wish to use a core to schedule a guest VM, service it eg. execute an ISR etc and then return to the context of Xen on that core, so that I can then schedule the next VM on that core. In doing all this, the goal is to avoid the calls to VMEntry and VMExit. Is there a workaround for this to be done or

My recent interest in the TPR-write problem has got me thinking about if there is any other optimisation that could be done for windows, especially as a few people have reported issues with more than a few processors, and they say they are already running 2K3sp2 which should have TPR optimisation in it already. Is there any facility currently for profiling the frequency of vmexit''s to

This patch enables tracing VMEXIT/ENTRY for 64-bit systems (are there any 32-bit VT enabled systems out there?) Signed-off by Himanshu Raj (rhim.list@nosuchaddr.com) -- ------------------------------------------------------------------------- Himanshu Raj PhD Student, GaTech (www.cc.gatech.edu/~rhim) I prefer to receive attachments in an open, non-proprietary format.

SVM patch to add add init intercept handler. Applies cleanly to 9622. Please apply. Signed-off-by: Tom Woller <thomas.woller@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Attached patch for svm will enable a tlb flush for each vmrun. Applies cleanly to 8781:dcc2beb8a1d2 Signed-off-by: Tom Woller <thomas.woller@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This adds support for core and core2 chips. Tested on Woodcrest processors. Requires Oprofile 0.9.2. -Andrew Signed-off-by: Andrew Theurer <habanero@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I want to get the performance data like documents <<Xenoprofoverview&Networking Performance Analysis>> (http://www.xensource.com/files/xs0106_xenoprof.pdf ). But how can I get the modules'' profile in kernel? Now I use command: Opcontrol --no-vmlinux --separate=kernel,cpu --start-daemon ...run benchmark Opcontrol --sutdown Opreport >list The report shows: CPU:

Hi. I got a asus SABERTOOTH 990FX, reading about vt-d, I read the MoBo that support IOMMU and there was chip 990FX, them I pick this MoBo, the BIOS that came with the board was 0402 05/11. I follow the xen wiki, I''m running Xen 4.1.1 from Gitco on Centos 5.7 x64, by default the MoBo have the IOMMU disable, I enable the feature IOMMU = 64MB, save the bios settings, restart, turn off