From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: question about nested ntp Date: Wed, 13 Oct 2010 11:59:34 +0200 Message-ID: <20101013095934.GA19207@redhat.com> References: <20101012132611.GA28070@redhat.com> <20101013085755.GK1983@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "kvm@vger.kernel.org" To: "Roedel, Joerg" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2228 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750754Ab0JMJ7i (ORCPT ); Wed, 13 Oct 2010 05:59:38 -0400 Content-Disposition: inline In-Reply-To: <20101013085755.GK1983@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Oct 13, 2010 at 10:57:55AM +0200, Roedel, Joerg wrote: > Hi Gleb, > > On Tue, Oct 12, 2010 at 09:26:11AM -0400, Gleb Natapov wrote: > > I have a question about nested ntp code. Comment in init_kvm_nested_mmu() > > function says "arch.mmu.gva_to_gpa translates l2_gva to l1_gpa". If > > I read the code correctly at the time of nested guest execution > > arch.mmu.gva_to_gpa() points to one of paging*_gva_to_gpa() variants. The > > function calls walk_addr() with provided address which should be > > l2_gva according to the comment. Now when NPF happens while nested > > guest runs arch.mmu.page_fault() is called which translates to call > > to one of paging*_page_fault() variants. paging*_page_fault() calls > > walk_addr() too, but now it gets l2_gpa as a parameter since during > > NPF svm->vmcb->control.exit_info_2 will not point to l2_gva, but l2_gpa > > instead. Do I miss something here? > > No, the comment is wrong. The comment actually was right in -v1 of the > patch-series. But I changed that in -v2 and forgot the update/remove the > comment. Thanks for mentioning that :-) > Ah, good. I thought I am going crazy. -- Gleb.