From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45704) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cC5ig-0002vu-3d for qemu-devel@nongnu.org; Wed, 30 Nov 2016 09:18:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cC5ib-0004Hb-3O for qemu-devel@nongnu.org; Wed, 30 Nov 2016 09:18:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60594) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cC5ia-0004Gm-TZ for qemu-devel@nongnu.org; Wed, 30 Nov 2016 09:18:41 -0500 References: <14abb3dd-b639-3c31-cade-073fff209ca6@redhat.com> <20161129132354.GF15786@lemon> <04fa01e1-0613-fc14-527b-e3432c6fec1a@redhat.com> <20161129141746.GA2043@lemon> <20161129152428.4w6c6fuate4eouc5@kamzik.brq.redhat.com> <20161129153944.GA11237@lemon> <20161129160123.t55xzd3ggqnlcpsj@kamzik.brq.redhat.com> <07abf6bb-ec21-da2c-bc8c-c9f136ba5c01@redhat.com> <20161129193828.cbzvz5iya7pjms44@kamzik.brq.redhat.com> <20161130090534.jor25j4hnec7dlbp@kamzik.brq.redhat.com> From: Paolo Bonzini Message-ID: <3677a5ef-a01c-b867-178b-8287017176d3@redhat.com> Date: Wed, 30 Nov 2016 15:18:32 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Linux kernel polling for QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Andrew Jones Cc: Fam Zheng , Eliezer Tamir , "Michael S. Tsirkin" , QEMU Developers , Jens Axboe , Christian Borntraeger , Stefan Hajnoczi , Davide Libenzi , Christoph Hellwig , =?UTF-8?Q?Alex_Benn=c3=a9e?= On 30/11/2016 10:46, Peter Maydell wrote: >> > The problem is indeed with the scheduling. The way it currently works >> > is to depend on the iothread to kick a reschedule once in a while, or >> > a cpu to issue an instruction that does so (wfe/wfi). However if >> > there's no io and a cpu never issues a scheduling instruction, then it >> > won't happen. We either need a sched tick or to never have an infinite >> > iothread ppoll timeout (basically using the ppoll timeout as a tick). > Ah yes, that one. I thought Alex had a patch which added > a timer to ensure that we don't allow a single guest > TCG vCPU to hog the execution thread, but maybe I'm > misremembering. Yes, it's part of MTTCG. Paolo