All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, jun.nakajima@intel.com
Subject: Re: BUG: x86-64 VT crash backtrace
Date: Tue, 25 Jul 2006 13:09:05 -0400	[thread overview]
Message-ID: <44C65031.4090203@redhat.com> (raw)
In-Reply-To: <db0800e5f2f7d9a13682b1a1ef9899cc@cl.cam.ac.uk>

Keir Fraser wrote:
> 
> On 25 Jul 2006, at 17:02, Rik van Riel wrote:
> 
>> Hi Jun,
>>
>> here is the x86-64 VT crash backtrace, as promised.  I can trigger it 
>> within minutes by simply starting up a 64 bit VT domain on a 64 bit 
>> system.
> 
> The hideously long (but apparently valid) call sequence has overflowed 
> the 4kB Xen stack. Given that stacks are only per-cpu on x86 Xen, I 
> should probably just make them bigger (perhaps 8kB on debug builds, 16kB 
> on non-debug builds). 64-bit non-debug builds already have (almost) 8kB 
> stacks, so shouldn't see this crash.

These crashes are on a 64 bit system.

So yes, even with 8kB stacks it crashes.

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

  reply	other threads:[~2006-07-25 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25 16:02 BUG: x86-64 VT crash backtrace Rik van Riel
2006-07-25 16:55 ` Rik van Riel
2006-07-25 17:12   ` Keir Fraser
2006-07-25 16:57 ` Keir Fraser
2006-07-25 17:09   ` Rik van Riel [this message]
2006-07-25 17:15     ` Keir Fraser
2006-07-25 18:42       ` Rik van Riel

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=44C65031.4090203@redhat.com \
    --to=riel@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.