From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G2bEO-0004UF-O8 for qemu-devel@nongnu.org; Mon, 17 Jul 2006 18:06:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G2bEM-0004Tl-4V for qemu-devel@nongnu.org; Mon, 17 Jul 2006 18:06:24 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G2bEL-0004Ti-WF for qemu-devel@nongnu.org; Mon, 17 Jul 2006 18:06:22 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1G2bH6-00063M-GJ for qemu-devel@nongnu.org; Mon, 17 Jul 2006 18:09:12 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1G2bE4-0007kO-G1 for qemu-devel@nongnu.org; Tue, 18 Jul 2006 00:06:04 +0200 Received: from cpe-70-116-9-243.austin.res.rr.com ([70.116.9.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Jul 2006 00:06:04 +0200 Received: from anthony by cpe-70-116-9-243.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 18 Jul 2006 00:06:04 +0200 From: Anthony Liguori Date: Mon, 17 Jul 2006 17:01:23 -0500 Message-ID: References: <20060717091859.137890@gmx.net> <20060717140154.120660@gmx.net> <44BBE6DE.9080200@bellard.org> <46d6db660607171428i6ac08754q55f621c78bbed25e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: Problem: Keyboard dead after "-loadvm" 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 On Mon, 17 Jul 2006 23:28:40 +0200, Christian MICHON wrote: > On 7/17/06, Fabrice Bellard wrote: >> Sometimes I try :-) But evaluating patches takes a large amount of time >> and in a program like QEMU regressions are difficult to track and very >> easy to introduce... >> >> > not all on this list do contribute patches (in my case, not much > contribution at this level). But I believe we're tons of testers of > incoming patches :) > > you're not alone to test these patches: this is what I mean... > > I remember the asynchronous/dma patch could be also a good candidate for > insertion, if it could be updated... I actually think the last dma patch I saw was addressing the problem in the wrong way. IIRC, it was using threads? We really ought to do the work to make the block API properly asynchronous. It may seem tedious now, but it would also allow the use of something like linux-aio down the road which has the potential to have a pretty huge performance impact on block performance (with pbrook's recent SCSI emulation). Regards, Anthony Liguori