public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Richard Simpson <rs1002@huskydog.org.uk>, Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Setting nx bit in virtual CPU
Date: Sat, 10 Apr 2010 01:45:43 +0200	[thread overview]
Message-ID: <4BBFBC27.8040007@amd.com> (raw)
In-Reply-To: <4BBE4967.9020201@huskydog.org.uk>

Richard Simpson wrote:
> On 08/04/10 09:52, Andre Przywara wrote:
> 
>> Can you try to boot the attached multiboot "kernel", which just outputs
>> a brief CPUID dump?
>> $ qemu-kvm -kernel cpuid_mb -vnc :0
>> (Unfortunately I have no serial console support in there yet, so you
>> either have to write the values down or screenshot it).
>> In the 4th line from the button it should print NX (after SYSCALL).
> 
> OK, that was fun!  Resulting screen shots are attached.
> 
> ...default.png		With command line above.
> ...cpu_host.png		With -cpu host option added.
> ...no_kvm.png		With -no-kvm option added.
> 
> I hope that helps!

OK, AFAIK there are several flags missing. I dimly remember there was a 
bug with masking the CPUID bits in older kernels, so I guess you have to 
celebrate your uptime for the last time and then give it a reboot with a 
more up-to-date host kernel.
(I also rebooted my desktop after I made the one year and now am gone 
green with turning it off over night ;-)
Maybe you get around with rebuilding fixed versions of kvm.ko and 
kvm_amd.ko, I can provide a fix for you if you wish (please point me to 
a way to get the actual kernel source you use).
The userspace was up-to-date? (qemu-kvm 0.12.3)?

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 488-3567-12


  reply	other threads:[~2010-04-09 23:44 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
2010-04-08  8:52                   ` Andre Przywara
2010-04-08 21:23                     ` Richard Simpson
2010-04-09 23:45                       ` Andre Przywara [this message]
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=4BBFBC27.8040007@amd.com \
    --to=andre.przywara@amd.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox