From: Keir Fraser <keir.xen@gmail.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>
Subject: Re: PVH update....
Date: Thu, 10 Jan 2013 07:34:27 +0000 [thread overview]
Message-ID: <CD141F83.48B1C%keir.xen@gmail.com> (raw)
In-Reply-To: <20130109182059.159ddd03@mantra.us.oracle.com>
On 10/01/2013 02:20, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
> On Tue, 8 Jan 2013 18:50:30 -0800
> Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
>
> Strange. So the latest is, things are OK with debug=n. With debug=y,
> I get DOUBLE FAULT at:
>
> ffff82c4802d4710: construct_dom0+d subq $0x2488, %rsp
>
> where rsp == ffff82c4802efe20 is there, but (rsp - 0x2488), ie,
> 0xffff82c4802ed998 is not there. But, the subtract instruction
> should not cause an exception like that IMO. ss is 0, but that
> should be OK. Hmm... I am at a loss on this one!
This one's not rocket science, Mukesh. The hypervisor stack is 8kB, and
construct_dom0() is trying to allocate a stack frame bigger than 8kB. Debug
builds enforce the 8kB limit with guard pages. You will actually be crashing
on the first stack writing instruction after the subq, but double fault is
imprecise (in fact reported cs:eip is undefined for a double fault).
You're allocating a ridiculously big local variable on construct_dom0's
stack. So just don't do that.
-- Keir
> thanks,
> mukesh
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-10 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 2:37 PVH update Mukesh Rathor
2013-01-09 2:50 ` Mukesh Rathor
2013-01-10 2:20 ` Mukesh Rathor
2013-01-10 7:34 ` Keir Fraser [this message]
2013-01-11 1:11 ` Mukesh Rathor
-- strict thread matches above, loose matches on Subject: below --
2012-11-09 0:59 Mukesh Rathor
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=CD141F83.48B1C%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
/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).