From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kt8It-0007kl-LV for qemu-devel@nongnu.org; Thu, 23 Oct 2008 18:05:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kt8Is-0007jm-JC for qemu-devel@nongnu.org; Thu, 23 Oct 2008 18:05:15 -0400 Received: from [199.232.76.173] (port=59595 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kt8Is-0007jd-E9 for qemu-devel@nongnu.org; Thu, 23 Oct 2008 18:05:14 -0400 Received: from bart.se.axis.com ([195.60.68.10]:49653) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kt8Ir-0005bc-NK for qemu-devel@nongnu.org; Thu, 23 Oct 2008 18:05:14 -0400 Received: from bart.se.axis.com (bart.se.axis.com [127.0.0.1]) by bart.se.axis.com (Postfix) with ESMTP id 3996E64110 for ; Fri, 24 Oct 2008 00:04:54 +0200 (CEST) Received: from axis.com (edgar.se.axis.com [10.93.151.1]) by bart.se.axis.com (Postfix) with ESMTP id 22DE0640F9 for ; Fri, 24 Oct 2008 00:04:54 +0200 (CEST) Date: Fri, 24 Oct 2008 00:04:54 +0200 From: "Edgar E. Iglesias" Subject: Re: [Qemu-devel] [PATCH][RFT] Make DMA timer driven Message-ID: <20081023220453.GA15547@edgar.se.axis.com> References: <1224797417-26044-1-git-send-email-aliguori@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1224797417-26044-1-git-send-email-aliguori@us.ibm.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Edgar Iglesias , Anthony Liguori On Thu, Oct 23, 2008 at 04:30:17PM -0500, Anthony Liguori wrote: > The current DMA routines are driven by a call in main_loop_wait() after every > select. The effect of this is that the DMA runs at a 10ms frequency depending > on whether IO is pending. > > This patch converts the DMA code from using this implicit 10ms frequency to > having an explicit 10ms frequency using a QEMUTimer. This means boards no > longer have to stub out DMA_run() functions. > > The only two architectures implementing DMA_run() are cris and i386. For cris, > I converted it to a simple repeating timer. I've only compile tested this so > I'd appreciate if you could test it Edgar (or point me to an image). Hello Anthony, You can find info regarding CRIS/ETRAX testing here: http://lists.gnu.org/archive/html/qemu-devel/2008-09/msg00279.html I tested the patch. It works but unfortunately DMA transfers to/from the ethernet block now seem to emulate very slowly. Best regards