From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Subject: Re: x86/AMD: Nested hvm crashes in 4.3
Date: Fri, 28 Jun 2013 09:20:19 -0500
Message-ID: <51CD9BA3.2060908@amd.com>
References: <51CB863B.6020405@amd.com>
	<51CC125E02000078000E10CE@nat28.tlf.novell.com>
	<51CC03C9.60800@amd.com>
	<51CC2B2702000078000E1178@nat28.tlf.novell.com>
	<51CC12EC.7050608@amd.com> <51CC150B.8040001@amazon.de>
	<51CC1EAB.1060103@amd.com> <51CCDC72.5070008@amd.com>
	<51CD5E4802000078000E174F@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <51CD5E4802000078000E174F@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>, Christoph Egger <chegger@amazon.de>, Jacob Shin <Jacob.Shin@amd.com>, Sherry Hurwitz <sherry.hurwitz@amd.com>
List-Id: xen-devel@lists.xenproject.org

On 6/28/2013 2:58 AM, Jan Beulich wrote:
>>>> On 28.06.13 at 02:44, Suravee Suthikulanit <suravee.suthikulpanit@amd.com> wrote:
>> So, I have finally able to get the crash dump (see below). The crash is due
>> to an assert
>>
>>       (XEN) Assertion 'va >= XEN_VIRT_START' failed at
>> /sandbox/xen/xen.git/xen/include/asm/x86_64/page.h:86
>>
>> * Debugging show the va=ffff82c40002d000, XEN_VIRT_START=ffff82c4c0000000,
>> DIRECTMAP_VIRT_END=ffffff8000000000.
>> * Backtrace symbol showing the crash is in "svm_vmexit_handler()", which is
>> inlined from "svm_vmexit_do_vmsave()" and "svm_vmsave()".
> Which helps in no way identifying where the problem is -
> svm_vmexit_handler() is just too large to spot this without either
> the matching xen-syms at hand, or you adding further
> instrumentation.
>
> Jan

What I am trying to say is, the assertion is in the __virt_to_maddr which is called from
svm_vmexit_do_vmsave().  However, this is a bit complicate due to macros and inlines.
Here is the callchain supposed to look like:

     ASSERT(va >= XEN_VIRT_START )
     __virt_to_maddr        <---- inlined
     virt_to_mfn ()         <---- macro
     __pa ()                <---- macro
     smv_vmasave()          <---- inlined
     svm_vmexit_do_vmsave() <---- inlined
     svm_vmexit_handler()   <---- symbol

Suravee