From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2ez9-0000OE-2G for qemu-devel@nongnu.org; Fri, 26 Jul 2013 06:10:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V2ez8-0001iA-4P for qemu-devel@nongnu.org; Fri, 26 Jul 2013 06:10:54 -0400 Received: from gate.crashing.org ([63.228.1.57]:53551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2ez7-0001hw-QC for qemu-devel@nongnu.org; Fri, 26 Jul 2013 06:10:54 -0400 Message-ID: <1374833448.6142.130.camel@pasglop> From: Benjamin Herrenschmidt Date: Fri, 26 Jul 2013 20:10:48 +1000 In-Reply-To: <51F2484E.4020308@redhat.com> References: <1374829812-5201-1-git-send-email-aik@ozlabs.ru> <51F2484E.4020308@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3] hcd-ohci: add dma error handling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Alexey Kardashevskiy , Anthony Liguori , qemu-devel@nongnu.org On Fri, 2013-07-26 at 11:58 +0200, Gerd Hoffmann wrote: > On 07/26/13 11:10, Alexey Kardashevskiy wrote: > > Current hcd-ohci does not handle DMA errors. However they may happen > > so here we introduce simple error handling. > > > > On such errors, a typical OHCI will stop operating, signal the guest > > about the error by sending "UnrecoverableError Event", set itself into > > error state and set "Detected Parity Error" in its PCI config space > > to signal that it got an error and so does the patch. > > > > This also adds ohci_stop() call to ohci_bus_start() to handle possible > > failure of qemu_new_timer_ns(). > > > > Signed-off-by: Alexey Kardashevskiy > > Looks sane to me now. When I get an ack from Benjamin I'll go put it > into the usb patch queue. >>From me ? Heh, I barely remember what the code looks like in there, if you are both happy with it I don't think you need me :-) The only possibly comment is that I would have called ohci_stop() something a bit clearer such as ohci_die() or ohci_buserror() ... IE. That function does more than just "stop", it also signals an error, and that attribute should probably be described by the function name. Cheers, Ben.