xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
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>
Subject: Re: x86/AMD: Nested hvm crashes in 4.3
Date: Fri, 28 Jun 2013 09:20:19 -0500	[thread overview]
Message-ID: <51CD9BA3.2060908@amd.com> (raw)
In-Reply-To: <51CD5E4802000078000E174F@nat28.tlf.novell.com>

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

  reply	other threads:[~2013-06-28 14:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  0:24 x86/AMD: Nested hvm crashes in 4.3 Suravee Suthikulanit
2013-06-27  8:22 ` Jan Beulich
2013-06-27  9:20   ` Suravee Suthikulpanit
2013-06-27  9:50     ` Egger, Christoph
2013-06-27 10:08     ` Jan Beulich
2013-06-27 10:24       ` Suravee Suthikulpanit
2013-06-27 10:28         ` Andrew Cooper
2013-06-27 10:33         ` Egger, Christoph
2013-06-27 11:14           ` Suravee Suthikulpanit
2013-06-28  0:44             ` Suravee Suthikulanit
2013-06-28  7:58               ` Jan Beulich
2013-06-28 14:20                 ` Suravee Suthikulanit [this message]
2013-06-28 14:24                   ` Andrew Cooper
2013-06-28 14:52                   ` Jan Beulich
2013-06-28 15:05                     ` Egger, Christoph
2013-06-27 11:20         ` George Dunlap
2013-06-27 11:37         ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CD9BA3.2060908@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=JBeulich@suse.com \
    --cc=Jacob.Shin@amd.com \
    --cc=chegger@amazon.de \
    --cc=sherry.hurwitz@amd.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).