search for: stgi

Displaying 15 results from an estimated 15 matches for "stgi".

Did you mean: sgi
2006 Sep 15
10
[HVM][XENOPROFILE][RFC][0/3] xenoprofile HVM patches
...#39;'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 patch is merely the same patch that I posted a few weeks ago. The STGI code is moved from the exits.S files, and into the vmexit handler. The extra do_nmi() is removed allowing the host to handle the NMI when the stgi instruction is executed. This patch allows the second patch to properly set "guest NMI" flag for the oprofile code to determine proper rip/e...
2005 Jul 25
1
Winbind and AD issues
Hello, I've been working on integrating a Fedora Core 2 box into Active Directory over the weekend.. it's a file server running Samba. I seem to have partial success but it isn't really working how I want it to and maybe some clever person here can see the problem. I've joined it to the AD and I see the computer account in there.. Kerberos seems to work: ***************
2006 Jul 25
0
[SVM][PATCH] fix CONFIG_PAGING_LEVELS tests
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 http://lists.xensource.com/xen-devel
2006 Sep 15
0
[HVM][XENOPROFILE][PATCH][2/3] xenoprofile HVM patches
...ction (svm_oprofile_get_eip()) This new hvm table function is called from the op_module_athlon.c code, and returns the proper eip and "mode" for use in the xenoprof_log_event() function. 2) The vmexit handler code now checks the exitcode and if an NMI was intercepted, then prior to the stgi(), a flag (VGCF_hvm_guest_nmi) is set in the v->arch.guest_context.flags field. The VGCF_hvm_guest_nmi bit is checked during NMI processing via the hvm function callback. Tom _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.x...
2006 Oct 19
0
[HVM][XENOPROFILE][PATCH][1/4] remove do_nmi() from AMD-V vmexit handler
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 to be in a 3.0.3-1 base whenever th...
2014 Feb 06
2
r noobie, reading my text file into r
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
2007 Aug 09
0
[PATCH] x86/hvm: miscellaneous CPUID handling changes
...SE4A (6*32+ 6) /* AMD Streaming SIMD Extensions-4a */ +#define X86_FEATURE_MISALIGNSSE (6*32+ 7) /* Misaligned SSE Access */ +#define X86_FEATURE_3DNOWPF (6*32+ 8) /* 3DNow! Prefetch */ +#define X86_FEATURE_OSVW (6*32+ 9) /* OS Visible Workaround */ +#define X86_FEATURE_SKINIT (6*32+ 12) /* SKINIT, STGI/CLGI, DEV */ +#define X86_FEATURE_WDT (6*32+ 13) /* Watchdog Timer */ #define cpu_has(c, bit) test_bit(bit, (c)->x86_capability) #define boot_cpu_has(bit) test_bit(bit, boot_cpu_data.x86_capability) _______________________________________________ Xen-devel mailing list Xen-devel@lists.x...
2013 Aug 26
5
[RFC PATCH 0/2] GLOBAL() macro for asm code.
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
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
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
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
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
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
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
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
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
2018 May 23
33
[PATCH v3 00/27] x86: PIE support and option to extend KASLR randomization
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
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
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
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
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