search for: stgy

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

...newbiz guest ok = no create mask = 0770 [Common] comment = Common browseable = yes writable = yes path = /common guest ok = no create mask = 0770 [Studio] comment = Studio browseable = yes writable = yes path = /studio guest ok = no create mask = 0777 [Stgy] comment = Stgy browseable = yes writable = yes path = /stgy guest ok = no create mask = 0777 [InfoTech] comment = System public = no valid users = aj tom vitus EWNS.NET+administrator writable = yes path = /infotech guest ok = no create mask = 0770 [Acct]...

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

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

Remove the do_nmi() call from the vmexit logic, as the NMI is held pending and will be handled in the context of the host when the STGI instruction is executed. This patch only modifies AMD-V code. This patch is required even without the other Xenoprofile patches applied. Applies cleanly to c/s 11831. Please apply to xen-unstable.hg regardless of the other patches. We also want these patches

Hi everyone, this is my first time using r and I think I'm overlooking something small and I just need some help seeing it. I have a file in notepad that I need to read into r. > ceosalary<-read.table(file="C:/Users/mz106_010/Desktop/ceosalary.csv",header > = TRUE,sep="\t") Error in file(file, "rt") : cannot open the connection In addition: Warning

- use __clear_bit() rather than clear_bit() - use switch statements instead of long series of if-s - eliminate pointless casts (Applies cleanly only on top of the previously sent SVM/EFER patch.) Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-08-08/xen/arch/x86/hvm/hvm.c =================================================================== ---

Hello, This series has been split into two patches, one for arm and one for x86. I figured that this was easier than doing it as a single combined patch, especially as the changes are functionally independent. x86 has been boot tested, but arm has not even been compile tested as I lack a suitable cross compiler. However, the changes are just text replacement, so I dont expect any issues. The

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends