From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52410) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEByJ-0005YN-BY for qemu-devel@nongnu.org; Wed, 19 Sep 2012 00:33:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEByI-0006Hf-64 for qemu-devel@nongnu.org; Wed, 19 Sep 2012 00:33:11 -0400 Received: from mail-lpp01m010-f45.google.com ([209.85.215.45]:62146) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEByH-0006Ha-Ug for qemu-devel@nongnu.org; Wed, 19 Sep 2012 00:33:10 -0400 Received: by lagz14 with SMTP id z14so361586lag.4 for ; Tue, 18 Sep 2012 21:33:08 -0700 (PDT) Date: Wed, 19 Sep 2012 06:32:57 +0200 From: "Edgar E. Iglesias" Message-ID: <20120919043257.GB29439@zapo> References: <504F0A64.9000306@redhat.com> <504F0CA5.5030405@siemens.com> <504F1A8B.3080604@redhat.com> <504F1BBC.3030409@siemens.com> <504F2C80.3040803@redhat.com> <504F2DD6.8070807@siemens.com> <504F2EE6.8060606@redhat.com> <504F3021.5090802@siemens.com> <504F3113.1000708@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH V3 10/11] vcpu: introduce lockmap List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Peter Maydell , Igor Mitsyanko , Jan Kiszka , Marcelo Tosatti , "qemu-devel@nongnu.org" , liu ping fan , Avi Kivity , Anthony Liguori , Paolo Bonzini On Wed, Sep 19, 2012 at 02:25:48PM +1000, Peter Crosthwaite wrote: > Ping for PMM, > > This is the root case of your block on the SDHCI series - this is a > discussion on resolution to bogus infinite looping DMA. For current > participants in this discussion, heres our thread on the same topic > over in SD land: > > http://lists.gnu.org/archive/html/qemu-devel/2012-08/msg01017.html > > With the findings here and acknowledgement that this is a general > problem, we either need to declare this issue of scope for SDHCI, or > work with these guys (in the immediate future) on the DMA infinite > loop problem flagged here. I dont mind if SDHCI+ADMA is the guinea pig > here, but can we get a decisive plan for going forward with this issue > if it is going to continue to block SDHCI. > > Thanks to Igor for identifying the overlap between these discussions. Hi, A couple of dumb questions. What is the reason for the blocker? that possible guest dos is worse than no functionality at all? Can't you put the DMA/IO processing into the background? what's the diff between setup of bad descriptors and writing a while (1) loop in the guest CPU? Cheers, E