From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=46761 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pi80U-0008Jc-10 for qemu-devel@nongnu.org; Wed, 26 Jan 2011 11:14:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pi80S-0006P5-8q for qemu-devel@nongnu.org; Wed, 26 Jan 2011 11:14:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34319) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pi80S-0006Ol-1a for qemu-devel@nongnu.org; Wed, 26 Jan 2011 11:14:04 -0500 Message-ID: <4D404846.3050400@redhat.com> Date: Wed, 26 Jan 2011 18:13:58 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH 01/12] coroutine: Add gtk-vnc coroutines library References: <1295688567-25496-1-git-send-email-stefanha@linux.vnet.ibm.com> <1295688567-25496-2-git-send-email-stefanha@linux.vnet.ibm.com> <4D403CF3.8080102@redhat.com> <4D40450B.3070705@linux.vnet.ibm.com> In-Reply-To: <4D40450B.3070705@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin Wolf , Anthony Liguori , Stefan Hajnoczi , qemu-devel@nongnu.org On 01/26/2011 06:00 PM, Anthony Liguori wrote: > On 01/26/2011 09:25 AM, Avi Kivity wrote: >> On 01/22/2011 11:29 AM, Stefan Hajnoczi wrote: >>> Asynchronous image format code is becoming very complex. Let's try >>> using coroutines to write sequential code without callbacks but use >>> coroutines to switch stacks under the hood. >>> >>> >>> + >>> +int cc_swap(struct continuation *from, struct continuation *to) >>> +{ >>> + to->exited = 0; >>> + if (getcontext(&to->last) == -1) >>> + return -1; >>> + else if (to->exited == 0) >>> + to->exited = 1; >>> + else if (to->exited == 1) >>> + return 1; >>> + >>> + return swapcontext(&from->uc,&to->uc); >>> +} >> >> swapcontext() is very slow, involving the fpu and a syscall. >> >> A nice trick I've used in the past is to use getcontext/makecontext >> for the initial setup and setjmp/longjmp for switching. Of course >> this can be done later, as an optimization. > > Yeah, there are further optimizations that can be had but really, it's > not important here. In fact, I'd rather start with the threaded > version just because it's far more portable than ucontext. > What do you mean by threaded version? -- error compiling committee.c: too many arguments to function