From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Setting nx bit in virtual CPU Date: Sat, 10 Apr 2010 22:34:15 +0300 Message-ID: <4BC0D2B7.5000801@redhat.com> References: <4BB126AC.8040401@huskydog.org.uk> <4BB45CA2.5040304@redhat.com> <4BB65C9D.3070505@huskydog.org.uk> <4BB99F03.3020208@redhat.com> <4BBBB63B.60007@huskydog.org.uk> <4BBC1A86.6080506@redhat.com> <4BBC7645.2070904@huskydog.org.uk> <4BBC7958.9010903@redhat.com> <4BBCED32.30304@huskydog.org.uk> <4BBCEFA5.3050900@redhat.com> <4BBD1198.6010304@huskydog.org.uk> <4BBD8474.6060809@redhat.com> <4BBE6D09.7000207@huskydog.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Richard Simpson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53315 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750974Ab0DJTeW (ORCPT ); Sat, 10 Apr 2010 15:34:22 -0400 In-Reply-To: <4BBE6D09.7000207@huskydog.org.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 04/09/2010 02:55 AM, Richard Simpson wrote: > On 08/04/10 08:23, Avi Kivity wrote: > > >> Strange. Can you hack qemu-kvm's cpuid code where it issues the ioctl >> KVM_SET_CPUID2 to show what the data is? I'm not where that code is in >> your version of qemu-kvm. >> > > So, basically I go round a loop and print out the contents of each > kvm_cpuid_entry2 structure. > > Results below, using Andre Przywara's handy nano-kernel. I do hope that > some of this makes some kind of sense! > > qemu-kvm -kernel cpuid_mb -vnc :0 > > > 80000000 0 0 8000000a 68747541 444d4163 69746e65 > 80000001 0 0 623 0 1 2181abfd > 80000001 edx bit 20 is NX, which is cleared. So it is qemu-kvm at fault here. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.