public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Huihong Luo <huisinro-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Bugs on MacBook, and proposed code change
Date: Mon, 11 Dec 2006 11:35:29 +0200	[thread overview]
Message-ID: <457D2661.9060006@qumranet.com> (raw)
In-Reply-To: <20061211044746.1006.qmail-jCIPyZ9Nm/SvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>

Huihong Luo wrote:
> I tried to compile kvm on an Intel Mac (MacBook laptop
> runing Linux 2.6.17). It does not work, qemu simply
> hangs.
>
> I spent sometime to fix the issues, can you correct
> the issues? There are to do with the kernel module.
> After the following 2 corrections, I can launch
> windows XP SP2 on a MacBook.
>
> (1) hvm_main.c
>
> There seems to be extra put_cpu()
> static void vcpu_put(struct kvm_vcpu *vcpu)
> {
> 	kvm_arch_ops->vcpu_put(vcpu);
> 	/* put_cpu(); extra one Huihong */
> 	mutex_unlock(&vcpu->mutex);
> }
>   

Yup, a bug.  Will fix.


> (2) in vmx.c:
>
> static __init void hardware_enable(void *garbage)
> {
> 	int cpu = raw_smp_processor_id();
> 	u64 phys_addr = __pa(per_cpu(vmxarea, cpu));
> 	u32 eax, edx;
>
> 	rdmsr(MSR_IA32_FEATURE_CONTROL, eax, edx);
> 		
> 	if (eax & 1) {
> 		if ((eax & 4) == 0) {
> 			printk("VMX disabled by Feature Control MSR.\n");
> 			return;
> 		}
> 	}
> 	else {
> 		/* enable and lock */
> 		wrmsr(MSR_IA32_FEATURE_CONTROL, 5, 0);
> 	}
>   

I don't understand this one.

There are 4 possible values of [FEATURE_CONTROL.2, FEATURE_CONTROL.]:

00: disabled, unlocked: handled correctly by the original code
01: disabled, locked: cannot be handled, but should be caught by 
vmx_disabled_by_bios().
10: enabled, unlocked: handled correctly by the original code
11: enabled, locked: handled correctly by the original code

No?

> #if 0 /* Huihong, original */
> 	if ((old & 5) == 0)
> 		/* enable and lock */
> 		wrmsrl(MSR_IA32_FEATURE_CONTROL, old | 5);
> #endif
>
> Huihong
> 	
>
>   

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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

      parent reply	other threads:[~2006-12-11  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11  4:47 Bugs on MacBook, and proposed code change Huihong Luo
     [not found] ` <20061211044746.1006.qmail-jCIPyZ9Nm/SvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2006-12-11  9:35   ` Avi Kivity [this message]

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=457D2661.9060006@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=huisinro-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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