[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Re: how to handle paged hypercall args?
- To: Olaf Hering <olaf@xxxxxxxxx>
- From: Keir Fraser <keir@xxxxxxx>
- Date: Fri, 03 Dec 2010 06:13:43 -0800
- 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 06:15:35 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:cc:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=AhjxFrEKc/BYB0GH2u7KFwSY5JzwZunc9/4rDe2En9s=; b=A0TxG2WdM9/Qzw8QVE8LPCuoLnkK89J+94KCdbAXxJ9bgt4aExdJK+R1xYeuR1kdFO 7JXOsPuXVb70IalDqINl3G9PCZObKCD1TOBS8GOqk5+D9h/tqsUPmY8KNHpgppobBMzj 4/OBtqOevmB9zmH8pxrk+kQDlW7Db2LO8wzHA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=IglSpzGz4T4HX7Sne/a33Wqd67mMZ2MQIaebOinErtKaJCXAhtuXaFeDYUIZlvcKnA OBE28fXVCAZ03Dr4HHDV7DDXzNCpbJ3Gaq4MyDQNzb7wdczj+M0pbpcVdcmtGS+reDmR Ab2Sb0qOSTGmZojnJZhlMp8GIr3895YBNASgQ=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcuS9EqDrjOoDggHu0GBaJlL9y2X7Q==
- Thread-topic: [Xen-devel] Re: how to handle paged hypercall args?
On 03/12/2010 01:03, "Olaf Hering" <olaf@xxxxxxxxx> wrote:
> 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?
It can get pretty deep with nested interrupts. I wouldn't expect a guest's
hypercall stack to get very deep at all. Send me a BUG_ON() backtrace. That
said, making the saved-stack area bigger isn't really a problem.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel