From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45470) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpW4a-0003h0-LI for qemu-devel@nongnu.org; Thu, 29 Sep 2016 03:48:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpW4Z-0001bE-NR for qemu-devel@nongnu.org; Thu, 29 Sep 2016 03:48:04 -0400 References: <1474958276-7715-1-git-send-email-famz@redhat.com> <1474958276-7715-6-git-send-email-famz@redhat.com> <20160929030543.GD6412@lemon> From: Paolo Bonzini Message-ID: <3a5afa67-e580-cd20-6d19-9c9071bf55a0@redhat.com> Date: Thu, 29 Sep 2016 09:47:53 +0200 MIME-Version: 1.0 In-Reply-To: <20160929030543.GD6412@lemon> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 5/5] block: keep AioContext pointer in BlockBackend List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng , Max Reitz Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, Kevin Wolf , qemu-stable@nongnu.org, stefanha@redhat.com On 29/09/2016 05:05, Fam Zheng wrote: > > So whether we can move a certain BB from some context to another depends > > on what the frontend supports, I don't think there is a generic answer > > we can implement here in the generic BB code. NBD for instance allows > > any movement; but devices probably only allow movements they have > > initiated themselves (e.g. dataplane will allow exactly what you > > describe here with that assertion, and any other device will probably > > not allow anything but the main loop). > > Indeed, you make me think this should be an op blocker (that applies on whole > graph). The concept of a BDS or BB's AioContext is going to disappear sooner or later, take this into account to decide how much effort to put into fixing this. Paolo