From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abkhR-00026l-Lh for qemu-devel@nongnu.org; Fri, 04 Mar 2016 03:03:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1abkhQ-000408-Pe for qemu-devel@nongnu.org; Fri, 04 Mar 2016 03:03:01 -0500 Message-ID: <1457078568.3574.67.camel@redhat.com> From: Gerd Hoffmann Date: Fri, 04 Mar 2016 09:02:48 +0100 In-Reply-To: References: <1456787490-17112-1-git-send-email-Andrew.Baumann@microsoft.com> <1457021768.3574.58.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH RFC] bcm2835_dma: add emulation of Raspberry Pi DMA controller List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Peter Crosthwaite , Stefan Weil , =?ISO-8859-1?Q?Gr=E9gory?= ESTRADE , QEMU Developers , Andrew Baumann , qemu-arm , Paolo Bonzini Hi, > I guess a more general approach to the problem would be to have > a (hopefully easy) way to say "if this has been going on for too > long then arrange to defer continued processing of it til later, > and for now resume the guest". Doable today, by simply applying some limit and if we hit it schedule a timer to continue later. uhci emulation does this, but it's basically no extra work there as usb emulation is timer based _anyway_. > That's too big a can of worms for > this patch, though. (And for something that's only used in TCG > emulation we care much less about malicious guests than for devices > that can be used with KVM.) Agree, given the use case this isn't critical by any means. cheers, Gerd