From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] KVM: Fix MAXPHYADDR calculation when cpuid does not support
 it
Date: Sun, 11 Apr 2010 16:35:01 +0300
Message-ID: <4BC1D005.5090203@cs.helsinki.fi>
References: <1270989212-3117-1-git-send-email-avi@redhat.com> <4BC1CF54.4020804@cs.helsinki.fi> <4BC1CFBC.5060406@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from courier.cs.helsinki.fi ([128.214.9.1]:38113 "EHLO
	mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751718Ab0DKNfI (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 11 Apr 2010 09:35:08 -0400
In-Reply-To: <4BC1CFBC.5060406@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity wrote:
>> Hmm, doesn't seem to work here. I still that triple fault in guest.
> 
> Can you add a printk to see what value is returned and why?

Argh, it's a off-by one bug in my userspace tool... So the CPU really 
does support 0x80000008 and I'm just an idiot. :-)

			Pekka