All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Fontenot <nfont@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Linas Vepstas <linas@austin.ibm.com>,
	akpm@osdl.org, linuxppc64-dev@ozlabs.org, anton@samba.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PPC64: EEH Recovery
Date: Wed, 19 Jan 2005 10:00:22 -0600	[thread overview]
Message-ID: <41EE8416.502@austin.ibm.com> (raw)
In-Reply-To: <16877.63693.915740.385920@cargo.ozlabs.ibm.com>


Paul Mackerras wrote:

> 5. AFAICS userland will get an unplug notification for the device, but
>    nothing to indicate that is due to an EEH slot isolation event.  I
>    think userland should be told about EEH events.
> 

Currently there is a way for userland to determine if a hotplug event 
they receive is due to an EEH slot isolation event.  It's not very 
pretty and requires the rtas_errd daemon to be running.

The RTAS event generated from the EEH event is logged to 
/var/log/platform by rtas_errd.  Userland scripts would have to search 
the file for a recent EEH event matching their device to make this 
determination.  This isn't as nice as a direct notification but is what 
we have at this point.

-- 
Nathan Fontenot

  reply	other threads:[~2005-01-19 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:24 [PATCH] PPC64: EEH Recovery Linas Vepstas
2005-01-17 20:14 ` Linas Vepstas
2005-01-19  6:06   ` Paul Mackerras
2005-01-19 16:00     ` Nathan Fontenot [this message]
2005-01-20 22:39     ` Linas Vepstas
2005-01-21  2:50       ` Paul Mackerras
2005-01-20 22:48     ` Linas Vepstas
  -- strict thread matches above, loose matches on Subject: below --
2004-11-17 23:52 Linas Vepstas

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=41EE8416.502@austin.ibm.com \
    --to=nfont@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.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 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.