From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42423) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rwxu6-0002QE-KW for qemu-devel@nongnu.org; Mon, 13 Feb 2012 10:33:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rwxu5-0008BX-Cn for qemu-devel@nongnu.org; Mon, 13 Feb 2012 10:33:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:14103) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rwxu5-0008BC-6I for qemu-devel@nongnu.org; Mon, 13 Feb 2012 10:33:21 -0500 Message-ID: <4F392E0B.4060809@redhat.com> Date: Mon, 13 Feb 2012 16:36:43 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <1329144150-7720-1-git-send-email-abarcelo@ac.upc.edu> <1329144150-7720-3-git-send-email-abarcelo@ac.upc.edu> In-Reply-To: <1329144150-7720-3-git-send-email-abarcelo@ac.upc.edu> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/3] coroutine: adding control flags (enable/disable) for ucontext compilation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Barcelo Cc: qemu-devel@nongnu.org Am 13.02.2012 15:42, schrieb Alex Barcelo: > Configure tries, as a default, ucontext functions for the > coroutines. But now the user can force its use or disable > it at all (enable and disable flags) > > Signed-off-by: Alex Barcelo I think a better approach would be to have a --coroutines=[ucontext|sigaltstack|gthread|windows] option, with the appropriate default whereever it's possible to detect. This would allow to build with gthread based coroutines even when another option is available. Kevin