From: Avi Kivity <avi@redhat.com>
To: Richard Simpson <rs1002@huskydog.org.uk>
Cc: kvm@vger.kernel.org
Subject: Re: Setting nx bit in virtual CPU
Date: Sat, 10 Apr 2010 22:34:15 +0300 [thread overview]
Message-ID: <4BC0D2B7.5000801@redhat.com> (raw)
In-Reply-To: <4BBE6D09.7000207@huskydog.org.uk>
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.
next prev parent reply other threads:[~2010-04-10 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:16 Setting nx bit in virtual CPU Richard Simpson
2010-03-30 2:12 ` Chris Wright
2010-03-30 20:42 ` Richard Simpson
2010-04-01 8:43 ` Avi Kivity
2010-04-02 21:07 ` Richard Simpson
2010-04-05 8:27 ` Avi Kivity
2010-04-06 22:31 ` Richard Simpson
2010-04-07 5:39 ` Avi Kivity
2010-04-07 12:10 ` Richard Simpson
2010-04-07 12:23 ` Avi Kivity
2010-04-07 20:38 ` Richard Simpson
2010-04-07 20:48 ` Avi Kivity
2010-04-07 23:13 ` Richard Simpson
2010-04-08 7:23 ` Avi Kivity
2010-04-08 23:55 ` Richard Simpson
2010-04-10 19:34 ` Avi Kivity [this message]
2010-04-08 8:52 ` Andre Przywara
2010-04-08 21:23 ` Richard Simpson
2010-04-09 23:45 ` Andre Przywara
2010-04-12 21:15 ` Richard Simpson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC0D2B7.5000801@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rs1002@huskydog.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.