From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tarantool-patches-bounce@freelists.org>
Received: from localhost (localhost [127.0.0.1])
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 965992B950
	for <tarantool-patches@freelists.org>; Tue, 25 Sep 2018 19:34:04 -0400 (EDT)
Received: from turing.freelists.org ([127.0.0.1])
	by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JzZDePVWfVrt for <tarantool-patches@freelists.org>;
	Tue, 25 Sep 2018 19:34:04 -0400 (EDT)
Received: from smtp38.i.mail.ru (smtp38.i.mail.ru [94.100.177.98])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 572B52B94F
	for <tarantool-patches@freelists.org>; Tue, 25 Sep 2018 19:34:04 -0400 (EDT)
Date: Wed, 26 Sep 2018 02:34:02 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 2/3] Proper unwind for currently
 executing fiber
Message-ID: <20180925233402.GJ3137@chai>
References: <cover.1537535602.git.georgy@tarantool.org>
 <7b844650e2e0799813e82b32ea2d637982bc3395.1537535602.git.georgy@tarantool.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7b844650e2e0799813e82b32ea2d637982bc3395.1537535602.git.georgy@tarantool.org>
Sender: tarantool-patches-bounce@freelists.org
Errors-to: tarantool-patches-bounce@freelists.org
Reply-To: tarantool-patches@freelists.org
List-help: <mailto:ecartis@freelists.org?Subject=help>
List-unsubscribe: <tarantool-patches-request@freelists.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: tarantool-patches <tarantool-patches.freelists.org>
List-subscribe: <tarantool-patches-request@freelists.org?Subject=subscribe>
List-owner: <mailto:>
List-post: <mailto:tarantool-patches@freelists.org>
List-archive: <http://www.freelists.org/archives/tarantool-patches>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>

* Georgy Kirichenko <georgy@tarantool.org> [18/09/22 00:21]:
> A fiber's coro context stores execution state for a corresponding
> already yielded fiber. If fiber is on the execution then it hasn't
> valid stored coro state and might be backtraced without a special unwind
> context builder.

I did not understand what's going on from the comment. I assume
this is an optimization, in which you try to avoid re-fetching the
registers in some cases?

Please clarify.
> --
-- 
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov