From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] hcd-ohci: add dma error handling
Date: Fri, 26 Jul 2013 20:10:48 +1000 [thread overview]
Message-ID: <1374833448.6142.130.camel@pasglop> (raw)
In-Reply-To: <51F2484E.4020308@redhat.com>
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 <aik@ozlabs.ru>
>
> 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.
next prev parent reply other threads:[~2013-07-26 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 9:10 [Qemu-devel] [PATCH v3] hcd-ohci: add dma error handling Alexey Kardashevskiy
2013-07-26 9:58 ` Gerd Hoffmann
2013-07-26 10:10 ` Benjamin Herrenschmidt [this message]
2013-07-26 10:23 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374833448.6142.130.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).