similar to: Intel: Overly restrictive test for availablility of CPUID masking MSRs?

Displaying 20 results from an estimated 500 matches similar to: "Intel: Overly restrictive test for availablility of CPUID masking MSRs?"

2010 Jul 02
10
Do systems have to be IDENTICAL for live migration?
I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution
2008 Jul 09
3
[PATCH]: Add support for Intel CPUID Feature mask in Xen
Hi, all Some Latest Intel CPU models (CPUID.1.EAX >= 0x00010674) support cupid mask features. Cpuid feature mask is used to limit the feature flags reported by CPUID.1.EDX:ECX. This small patch adds CPUID feature mask support in XEN by adding boot options in Grub entry as below example: kernel /boot/xen.gz com1=115200,8n1 console=com1 cpuid_mask_ecx = 0xFFFF7FFF cpuid_mask_edx = 0xFFFFFFFC
2011 Jul 29
2
[LLVMdev] Overly restrictive size argument to llvm.invariant.start
Why is it that @llvm.invariant.start requires the size argument to be a constant integer literal and does not accept constant expressions? For example the following IR: declare {}* @llvm.invariant.start(i64,i8*) define void @foo() { %1 = call {}* @llvm.invariant.start(i64 ptrtoint(i8* getelementptr(i8* %null, i32 1) to i64), i8* null) ret void } gives the following error from llvm-as:
2011 Jul 29
0
[LLVMdev] Overly restrictive size argument to llvm.invariant.start
Geoff Reedy wrote: > Why is it that @llvm.invariant.start requires the size argument to be a > constant integer literal and does not accept constant expressions? For > example the following IR: > > declare {}* @llvm.invariant.start(i64,i8*) > define void @foo() { > %1 = call {}* @llvm.invariant.start(i64 ptrtoint(i8* getelementptr(i8* > %null, i32 1) to i64), i8*
2012 Oct 17
0
[PATCH] vMCE: Implement AMD MSRs
Implement AMD MSRs for vMCE Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 _______________________________________________
2005 Jul 21
0
[PATCH]Propagate guest MSR writes to machine MSRs immediately
Propagate guest MSR writes to machine MSRs immediately Right now, we have an exposure between the time the MSR is written and used by an instruction such as syscall. If there is a context switch and we do vmx_do_restore_msrs(), everything goes fine. But if we don''t, then we execute the syscall with the wrong MSR. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com>
2012 Oct 26
0
[PATCH] MCE: Allow AMD MSRs injected via xen-mceinj
Allow AMD MSRs injected via xen-mceinj Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85689 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632
2007 Dec 10
2
[PATCH] MTRR MSRs Save/Restore
This patch adds the MTRR MSRs save/restore support. Signed-off-by: Disheng Su <disheng.su@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Oct 06
3
Writing MSRs from Domain0
Hello, I recently tried Xen 3.0.3-testing on my 2x Opteron-244 SMP machine. Everything works well exept one detail, which is not unimportant to me: the powernow-k8 driver fails to switch frequencies. A closer look on the powernow-k8 source reveals, that some MSR write operations seem to be without any effect. A rdmsr() before and after the wrmsr() call reveals that no real change on the register
2009 Nov 22
4
Xen 3.4.2 DomU Network Issues
I''ve got a new system with Dual Quad Core Intel E5520 processors and Intel 82576 NICs built on the motherboard (this is a Supermicro Nehalem based blade). I''m running Xen 3.4.2, but I''ve also tried 3.4.1 and had the same problem. Dom0''s network works flawlessly, but the DomU systems all have network issues. Whenever they transmit large packets, it is as if
2001 Nov 01
0
overly light printing HP 8000
Points, axes and axes labels on graphs printed from R are very light- almost unreadable. I am using the gui interface on the windows version to print the plot on the screen to an HP 8000 set as a postscript printer or PCL printer; the postscript output is light and the PCL output is very light. If I specify lwd =2 in the plot command, the lines are readable, but the points (open circles, in
2012 Apr 05
1
2.1.3: Overly lax FETCH parsing
These commands both work in Dovecot (as of 2.1.3): 1 UID FETCH 1:* () (CHANGEDSINCE 1) * 1 FETCH (UID 30097 MODSEQ (19554)) [...] 1 OK Fetch completed. 2 FETCH 1:* () (CHANGEDSINCE 1) * 2 FETCH (MODSEQ (19554)) [...] 2 OK Fetch completed. However, RFC 3501 indicates that an empty FETCH attribute list is incorrect: fetch = "FETCH" SP sequence-set SP ("ALL" /
2016 Jan 01
0
Fix for CVE-2015-5299 denies access to ZFS snapshots due to overly strict condition checking
On Fri, Jan 01, 2016 at 09:38:09PM +0800, QIU Quan wrote: > OS platform: FreeBSD 10.1-RELEASE-p25 > Filesystem: ZFS > Samba version: upgraded from 4.1.17 to 4.1.22 > > Problem: > > I have been using the shadow_copy2 and zfsacl VFS modules to enable > access control and the Previous Versions feature for Windows clients. > With /usr/local/etc/smb4.conf configured this
2012 Mar 07
1
.Internal(inspect(x)) gives overly verbose output for reference classes
Even for an extremely simple instance of a reference class x <- setRefClass("x") y <- x$new() calling the internal inspect function .Internal(inspect(y)) produces enough output that it takes several minutes to print to the console.? (Actually I gave up and terminated the command after ~10 mins.? It isn't clear whether the output would eventually complete.) Are reference
2011 Nov 02
1
overly long lines in pdf output of manual from package
In re-factoring my optimx package, I'm finding that the pdf output has some lines that are outside the margins (and there are warnings in R CMD check optimx). Clearly I can fix this by editing the tex file that is generated, but the build infrastructure would still get things wrong in automatic processing. So that gives rise to 3 questions: 1) How do I adjust the DESCRIPTION file to avoid too
2016 Jul 19
6
[Bug 2599] New: Overly verbose partial authentication
https://bugzilla.mindrot.org/show_bug.cgi?id=2599 Bug ID: 2599 Summary: Overly verbose partial authentication Product: Portable OpenSSH Version: 7.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at
2016 Jan 01
3
Fix for CVE-2015-5299 denies access to ZFS snapshots due to overly strict condition checking
OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot
2010 Jan 26
1
Bug#567025: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 1 seconds (XEN) EDID info not
2010 Jan 26
1
Bug#567026: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16
2010 Aug 17
6
Overly aggressive constant unloading of Rails 3.0
In Rails 3.0 (both RC and edge), any constant that''s defined while loading a file in development mode will get unloaded on each request, regardless of whether it comes from an autoload path in the application or from external code such as a gem. Example file (tested on a fresh edge app): # kittens.rb require ''nibbler/json'' # "nibbler" is a gem specified