From: Dean Nelson <dcn@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] Extend notify_die() hooks for IA64
Date: Fri, 21 Oct 2005 19:00:27 +0000 [thread overview]
Message-ID: <20051021190027.GA20883@sgi.com> (raw)
In-Reply-To: <10137.1128667602@kao2.melbourne.sgi.com>
On Fri, Oct 07, 2005 at 04:46:42PM +1000, Keith Owens wrote:
> This mail is only for discussion, the patch is 2.6.15-rc1 material. It
> has been compiled and has minimal testing. Against 2.6.14-rc3.
>
> notify_die() added for MCA_{MONARCH,SLAVE,RENDEZVOUS}_{ENTER,PROCESS,LEAVE} and
> INIT_{MONARCH,SLAVE}_{ENTER,PROCESS,LEAVE}. We need multiple
> notification points for these events because they can take many seconds
> to run which has nasty effects on the behaviour of the rest of the
> system.
>
> DIE_SS replaced by a generic DIE_FAULT which checks the vector number,
> to allow interception of faults other than SS.
>
> DIE_MACHINE_{HALT,RESTART} added to allow last minute close down
> processing, especially when the halt/restart routines are called from
> error handlers.
I'm very interested in seeing these proposed changes be accepted in
some form if not as is. In particular, the DIE_MACHINE_RESTART and
DIE_MACHINE_HALT callouts.
XPC (as in arch/ia64/sn/kernel/xp*) has a need to notify other partitions
(SGI Altix) whenever a partition is going down in order to get them to
disengage from accessing the halting partition's memory. If this is not
done before the reset of the hardware, the other partitions can find
themselves encountering MCAs that bring them down.
Being that XPC is a module, the ability to safely unregister_die_notifier()
also would be necessary. I see that this functionality is missing. Could this
be added in as well?
Thanks,
Dean
next prev parent reply other threads:[~2005-10-21 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 6:46 [RFC] Extend notify_die() hooks for IA64 Keith Owens
2005-10-21 19:00 ` Dean Nelson [this message]
2005-10-26 19:15 ` Dean Nelson
2005-10-27 0:29 ` Keith Owens
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=20051021190027.GA20883@sgi.com \
--to=dcn@sgi.com \
--cc=linux-ia64@vger.kernel.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