mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dan Williams" <dan.j.williams@intel.com>
To: "Haavard Skinnemoen" <hskinnemoen@atmel.com>
Cc: "Shannon Nelson" <shannon.nelson@intel.com>,
	linux-kernel@vger.kernel.org,
	"David Brownell" <david-b@pacbell.net>,
	kernel@avr32linux.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] DMA: Correct invalid assumptions in the Kconfig text
Date: Fri, 26 Oct 2007 10:02:24 -0700	[thread overview]
Message-ID: <e9c3a7c20710261002m1c5063bdqa040834c30d9ca8a@mail.gmail.com> (raw)
In-Reply-To: <20071025113240.466b69ba@siona>

On 10/25/07, Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
> On Wed, 24 Oct 2007 20:16:16 +0200
> Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
>
> > [handwaving about API extensions]
>
> Oh, and we definitely need a way to report errors. Looks like the
> existing drivers want this as well -- I couldn't help but notice this
> in the iop-adma driver:
>
> static irqreturn_t iop_adma_err_handler(int irq, void *data)
> {
>         (...)
>
>         BUG();
> }
>
> That's a panic waiting to happen, isn't it?

Yes, and it should have a comment, because for now this is deliberate.
 This was primarily driven by the fact that MD has no way of
recovering from hardware errors during software-memcpy or
software-xor_blocks so there was no where to plug-in
accelerated-memcpy/xor error recovery.  I can foresee other clients
wanting to have this information reported but async_tx based clients
are supposed to be blissfully unaware of under the covers hardware
acceleration.

One idea is to pass an error-pointer as the parameter to callback
routines, but that would hamper the client's ability to recover the
context of the failure...

>
> Håvard

--
Dan

  reply	other threads:[~2007-10-26 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  9:38 Haavard Skinnemoen
2007-10-24 15:11 ` Nelson, Shannon
2007-10-24 15:55 ` Dan Williams
2007-10-24 18:16   ` Haavard Skinnemoen
2007-10-25  9:32     ` Haavard Skinnemoen
2007-10-26 17:02       ` Dan Williams [this message]
2007-10-27 13:58         ` Haavard Skinnemoen
2007-10-27 18:10           ` Dan Williams
2007-10-26 16:44     ` Dan Williams
2007-10-27 16:07       ` Haavard Skinnemoen

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=e9c3a7c20710261002m1c5063bdqa040834c30d9ca8a@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=david-b@pacbell.net \
    --cc=hskinnemoen@atmel.com \
    --cc=kernel@avr32linux.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shannon.nelson@intel.com \
    /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

all inboxes | Powered by JetHome®