Hi! Am 08.11.2011 19:33, schrieb Brynet:
On Tue, Nov 08, 2011 at 01:27:37PM -0500, Brynet wrote:@@ -190,7 +190,7 @@ k1x_init(struct cpu_info *ci) #if NACPICPU> 0 msr = rdmsr(MSR_K1X_STATUS); - k1x_acpi_init(cstate, msr); + k1x_acpi_init(cstate);Whoops, fixed patch for amd64.
Does the patch fix the following? I've forwarding the bug report to the Linux KVM developers. The response: On 09.11.2011 14:40, Avi Kivity wrote: > Actually, it looks like an OpenBSD bug. According to the AMD > documentation: >> "The current P-state value can be read using the P-State Status >> Register. The P-State Current Limit Register and the P-State >> Status Register are read-only registers. Writes to these >> registers cause a #GP exception. Support for hardware P-state >> control is indicated by EDX bit 7 as returned by CPUID function >> 8000_0007h. Figure 18-1 shows the format of the P-State Current >> Limit register." and >> Can you check what cpuid 80000007 returns by running 'x86info -r >> | grep 80000007' in a Linux guest with the same command line? if >> edx returns zero, then it's OpenBSD not checking cpuid >> correctly. EDX is zero in a Linux guest (i386 and x86_64). Walter
