All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <markn@au1.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, michael@ellerman.id.au
Cc: Tseng-hui Lin <tsenglin@us.ibm.com>, engebret@us.ibm.com
Subject: Re: [PATCH] powerpc/pseries: Make request_ras_irqs() available to other pseries code
Date: Wed, 19 May 2010 16:54:42 +1000	[thread overview]
Message-ID: <201005191654.42483.markn@au1.ibm.com> (raw)
In-Reply-To: <1274250954.7574.1.camel@concordia>

On Wednesday 19 May 2010 16:35:54 Michael Ellerman wrote:
> On Wed, 2010-05-19 at 16:35 +1000, Mark Nelson wrote:
> > Hi Michael,
> > 
> > Thanks for looking over these patches!
> ..
> > > 
> > > Existing code I know, but the error handling in here is a little lax,
> > > what's not going to work if we miss some or all of the interrupts?
> > 
> > That's a good point. For the existing code, if we miss an EPOW event
> > it just means that the event won't be logged (as that's all we do with
> > those events at the moment, although there is a comment saying
> > that it should be fixed to take appropriate action depending upon the
> > type of power failure); but it's a bigger problem if we miss one of the
> > RAS errors because then we could miss a fatal event that we should halt
> > the machine on. And for the upcoming IO events it's even worse as we'd
> > miss an interrupt from the device...
> 
> Yeah that's what I was thinking.
> 
> > I would do it in a follow-on patch rather than this one, but what would
> > be a good course of action if we can't request the interrupt?
> 
> Yes a follow on patch is the way to do it.
> 
> There shouldn't be that many reasons the request fails, other than
> ENOMEM, or broken device tree perhaps. It's definitely worth a
> WARN_ON(), people notice those at least.

That sounds good. I'll do a simple follow-on patch that adds the
WARN_ON().

Thanks!
Mark

  reply	other threads:[~2010-05-19  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 12:33 [PATCH] powerpc/pseries: Make request_ras_irqs() available to other pseries code Mark Nelson
2010-05-18 12:40 ` Michael Ellerman
2010-05-19  6:35   ` Mark Nelson
2010-05-19  6:35     ` Michael Ellerman
2010-05-19  6:54       ` Mark Nelson [this message]
2010-05-19  8:51         ` [PATCH v2] " Mark Nelson
2010-05-27  6:56         ` powerpc/pseries: Add WARN_ON() to request_event_sources_irqs() on irq allocation/request failure Mark Nelson

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=201005191654.42483.markn@au1.ibm.com \
    --to=markn@au1.ibm.com \
    --cc=engebret@us.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=tsenglin@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.