On 10/18/2010 07:06 AM, Avi Kivity wrote:
> On 10/18/2010 03:58 PM, Dave Young wrote:
>>>
>>> Please patch hardware_setup() to show the value of
>>> boot_cpu_has(X86_FEATURE_NX).
>>
>> It's 0
>
> Well, that's ridiculous. Looking back at your /proc/cpuinfo:
>
>> processor : 0
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
>> lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor
>> ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow vnmi
>> flexpriority
>>
>> processor : 1
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
>> nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64
>> monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida dts tpr_shadow
>> vnmi flexpriority
>
> processor 0 doesn't have nx.
>
> Ingo, Peter, any ideas? Where did the missing feature go?
>
I don't see the original report -- in particular I can't see the kernel
version -- but I suspect this *might* be an instance of the same bug
fixed in mainline by checkin d900329e20f4476db6461752accebcf7935a8055
(for backporting 1dedefd1a066a795a87afca9c0236e1a94de9bf6 is also
needed; these both should be in -stable or on the way there.)
-hpa
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html