From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpc2c-0000R0-ES for qemu-devel@nongnu.org; Wed, 06 Sep 2017 11:15:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpc2W-0006c3-CV for qemu-devel@nongnu.org; Wed, 06 Sep 2017 11:14:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40512) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dpc2W-0006bV-6g for qemu-devel@nongnu.org; Wed, 06 Sep 2017 11:14:52 -0400 Date: Wed, 6 Sep 2017 16:14:37 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20170906151436.GF2215@work-vm> References: <1503471071-2233-1-git-send-email-peterx@redhat.com> <20170906145043.GG15535@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170906145043.GG15535@stefanha-x1.localdomain> Subject: Re: [Qemu-devel] [RFC v2 0/8] monitor: allow per-monitor thread List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Peter Xu , qemu-devel@nongnu.org, Laurent Vivier , Fam Zheng , Juan Quintela , Markus Armbruster , mdroth@linux.vnet.ibm.com, Paolo Bonzini * Stefan Hajnoczi (stefanha@gmail.com) wrote: > On Wed, Aug 23, 2017 at 02:51:03PM +0800, Peter Xu wrote: > > The root problem is that, monitor commands are all handled in main > > loop thread now, no matter how many monitors we specify. And, if main > > loop thread hangs due to some reason, all monitors will be stuck. > > I see a larger issue with postcopy: existing QEMU code assumes that > guest memory access is instantaneous. > > Postcopy breaks this assumption and introduces blocking points that can > now take unbounded time. > > This problem isn't specific to the monitor. It can also happen to other > components in QEMU like the gdbstub. > > Do we need an asynchronous memory API? Synchronous memory access should > only be allowed in vcpu threads. It would probably be useful for gdbstub where the overhead of async doesn't matter; but doing that for all IO emulation is hard. Dave > Stefan -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK