From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm userspace release 6 Date: Tue, 12 Dec 2006 20:05:50 +0200 Message-ID: <457EEF7E.80008@qumranet.com> References: <457D42F3.3000000@qumranet.com> <457D97ED.6090606@mr511.de> <457E939C.1030501@qumranet.com> <457EEA18.70204@mr511.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: To: Michael Riepe In-Reply-To: <457EEA18.70204-0QoEqw4nQxo@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Michael Riepe wrote: > vmx_get_msr() actually works fine. The problem is in vmx_vcpu_setup(), > in the loop starting at line 1142. It tries to read all the MSRs listed > in vmx_msr_index, but it fails for MSR_K6_STAR. With earlier releases, I > also used to see the kernel message "kvm: msrs: 1" - that is, only > MSR_EFER is found. According to Intel's docs, that's correct - the > register does not exist on a Core Duo which isn't 64-bit capable (but, > of course, on a Core 2 Duo - or a Xeon 51xx/53xx, aka "Woodcrest" and > "Clovertown"). > I see now. So the fix would be to tell the cpu the syscall feature doesn't exist, presumably via cpuid (which is handled in userspace). -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- 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