WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: how to handle paged hypercall args?

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] Re: how to handle paged hypercall args?
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Fri, 3 Dec 2010 10:03:41 +0100
Cc: Patrick Colp <pjcolp@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 03 Dec 2010 01:04:47 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1291367035; l=681; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=ZqPWdTGO2cAqZHgvxGN63BdivUs=; b=IpnmaAcIZgnlmeO2hpUrMFzjtjOBPDCcNYoloANh4JdYQ/U9eLFUcHaePKzulPYqJbC To92PhJVrSkzv+vpuYsX15bVq44sm+WkQibjlaZeFYLcq4MOiDEXUniPUR+V39DHQ4rvk Elnu5wxckqSSmGAL6vkRrx6//X4alZQchTU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C906D549.9F92%keir@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101115120459.GF21112@xxxxxxxxxxxxxxxxxxxxxxx> <C906D549.9F92%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, Nov 15, Keir Fraser wrote:

> On 15/11/2010 12:04, "Tim Deegan" <Tim.Deegan@xxxxxxxxxx> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel