From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir@xen.org>
Cc: Patrick Colp <pjcolp@cs.ubc.ca>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Re: how to handle paged hypercall args?
Date: Fri, 3 Dec 2010 10:03:41 +0100 [thread overview]
Message-ID: <20101203090341.GA6055@aepfle.de> (raw)
In-Reply-To: <C906D549.9F92%keir@xen.org>
On Mon, Nov 15, Keir Fraser wrote:
> On 15/11/2010 12:04, "Tim Deegan" <Tim.Deegan@citrix.com> wrote:
> > Will it
> > need per-vcpu stacks? (and will they, in turn, use order>0 allocations? :))
>
> Of a sort. I propose to keep the per-pcpu stacks and then copy context
> to/from a per-vcpu memory area for the setjmp-like behaviour. Guest call
> stacks won't be very deep -- I reckon a 1kB or 2kB per-vcpu area will
> suffice.
Keir,
in my testing the BUG_ON in __prepare_to_wait() triggers, 1500 is too
small. I changed it to 4096 - (4*sizeof(void*)) to fix it for me.
3K would be enough as well.
How large can the stack get, is there an upper limit?
Olaf
next prev parent reply other threads:[~2010-12-03 9:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 8:58 how to handle paged hypercall args? Olaf Hering
2010-11-11 14:33 ` Olaf Hering
2010-11-11 20:08 ` Keir Fraser
2010-11-11 20:34 ` Olaf Hering
2010-11-11 21:00 ` Keir Fraser
2010-11-12 9:45 ` Jan Beulich
2010-11-12 10:22 ` Keir Fraser
2010-11-12 10:47 ` Jan Beulich
2010-11-12 14:32 ` Keir Fraser
2010-11-15 13:12 ` Olaf Hering
2010-11-17 16:52 ` Keir Fraser
2010-11-18 12:33 ` Keir Fraser
2010-11-18 13:51 ` Olaf Hering
2010-12-02 10:11 ` Olaf Hering
2010-12-02 10:22 ` Keir Fraser
2010-12-02 10:30 ` Keir Fraser
2010-12-03 9:14 ` Olaf Hering
2010-12-03 14:37 ` Keir Fraser
2010-12-02 10:25 ` Jan Beulich
2010-12-03 9:06 ` Olaf Hering
2010-12-03 14:18 ` Keir Fraser
2010-12-02 10:18 ` Olaf Hering
2010-12-02 10:25 ` Keir Fraser
2010-12-07 9:25 ` Olaf Hering
2010-12-07 16:45 ` Keir Fraser
2010-12-07 17:16 ` Olaf Hering
2010-12-07 18:08 ` Keir Fraser
2010-12-07 18:50 ` Olaf Hering
2010-11-15 9:37 ` Tim Deegan
2010-11-15 9:53 ` Jan Beulich
2010-11-15 10:09 ` Keir Fraser
2010-11-15 10:20 ` Tim Deegan
2010-11-15 10:33 ` Keir Fraser
2010-11-15 10:49 ` Tim Deegan
2010-11-15 11:55 ` Keir Fraser
2010-11-15 12:04 ` Tim Deegan
2010-11-15 12:17 ` Keir Fraser
2010-12-03 9:03 ` Olaf Hering [this message]
2010-12-03 14:13 ` Keir Fraser
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=20101203090341.GA6055@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@novell.com \
--cc=Tim.Deegan@citrix.com \
--cc=keir@xen.org \
--cc=pjcolp@cs.ubc.ca \
--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.