From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uz9Md-0003yN-CF for qemu-devel@nongnu.org; Tue, 16 Jul 2013 13:48:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uz9Mc-0005hk-K7 for qemu-devel@nongnu.org; Tue, 16 Jul 2013 13:48:39 -0400 Sender: Paolo Bonzini Message-ID: <51E5876B.2040500@redhat.com> Date: Tue, 16 Jul 2013 19:48:27 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1373995321-2470-1-git-send-email-aarcange@redhat.com> <20130716173844.GC19826@otherpad.lan.raisama.net> <51E586E6.1060001@redhat.com> In-Reply-To: <51E586E6.1060001@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] fix guest physical bits to match host, to go beyond 1TB guests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Andrea Arcangeli , qemu-stable@nongnu.org, Eduardo Habkost , Gleb Natapov , qemu-devel@nongnu.org Il 16/07/2013 19:46, Paolo Bonzini ha scritto: >>> >> (see PUD with bit >=40 set) >> > >> > I am not sure I understand what caused this: if we are advertising 40 >> > physical bits to the guest, why are we ending up with a PUD with >> > bit >= 40 set? > Because we create a guest that has bigger memory than what we advertise > in CPUID. > Also, note that the guest does not really care about this CPUID. It is only used by KVM itself to decide which bits in the page tables are reserved. Paolo