public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: akpm@osdl.org
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	mingo@elte.hu
Subject: Re: [PATCH] KVM: Fix lockup on 32-bit intel hosts with nx disabled in the	bios
Date: Wed, 31 Jan 2007 17:02:03 +0200	[thread overview]
Message-ID: <45C0AF6B.4020406@qumranet.com> (raw)
In-Reply-To: <20070131150017.020B9A0014@il.qumranet.com>

Avi Kivity wrote:
> Intel hosts, without long mode, and with nx support disabled in the bios
> have an efer that is readable but not writable.  This causes a lockup on
> switch to guest mode (even though it should exit with reason 34 according to
> the documentation).
>
>   

Andrew, I believe this is 2.6.20 material.

> Signed-off-by: Avi Kivity <avi@qumranet.com>
>
> Index: linux-2.6/drivers/kvm/vmx.c
> ===================================================================
> --- linux-2.6.orig/drivers/kvm/vmx.c
> +++ linux-2.6/drivers/kvm/vmx.c
> @@ -1128,6 +1128,8 @@ static int vmx_vcpu_setup(struct kvm_vcp
>  
>  		if (rdmsr_safe(index, &data_low, &data_high) < 0)
>  			continue;
> +		if (wrmsr_safe(index, data_low, data_high) < 0)
> +			continue;
>  		data = data_low | ((u64)data_high << 32);
>  		vcpu->host_msrs[j].index = index;
>  		vcpu->host_msrs[j].reserved = 0;
>   


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2007-01-31 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 15:00 [PATCH] KVM: Fix lockup on 32-bit intel hosts with nx disabled in the bios Avi Kivity
2007-01-31 15:02 ` Avi Kivity [this message]
2007-02-01  2:52 ` [kvm-devel] " Jeff Chua
2007-02-01  7:55 ` Ingo Molnar

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=45C0AF6B.4020406@qumranet.com \
    --to=avi@qumranet.com \
    --cc=akpm@osdl.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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