All of lore.kernel.org
 help / color / mirror / Atom feed
From: davisg@Celestica.com
To: Philipp Rumpf <prumpf@puffin.external.hp.com>
Cc: davisg@Celestica.com, Bas Valkema <b_valkema@hotmail.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Couple of questions
Date: Tue, 28 Mar 2000 12:16:49 -0500	[thread overview]
Message-ID: <852568B0.005EEA6A.00@tormta3.tor.cel.com> (raw)



Greetings,

Philipp Rumpf wrote:
> > Transfer-Of-Control button/switch merely appears to result in a system
> > reset, its primary use is to recover from system hang conditions while
> > preserving the machine state for later analysis, i.e. where and why was
> > the sytem hung.
> >
> > So, in summary, although TOC on the surface appears to merely 'reset' the
> > system, it is capable of much more provided the OS specifies an OS_TOC
> > entry point for recovery and debug of machine state at any point during
> > system run time.
>
> Actually, that's exactly what reset does on (most) x86 boxes.  Remember
> getting 286s out of protected mode by resetting them ?
>

Oh yeah - I vaguely recall this. Painful, ugly and slow.

>
> I'm not convinced having customized TOC / HPMC handlers for Linux/PA-RISC
> is a good idea yet.

Agreed!  It's a lot of effort to add support for this. Looking back over the
parisc-linux archives, the alternative
is to use the platform firmware 'pim [hpmc|toc]' command to retrieve the machine
state at the time of crash/hang
and use this information to manually glark the vmlinux image to see where you
were at the time. Although there
is limited information to understand the overall machine context at time of
crash/hang, there's generally enough
information available from PIM to find out where you were (assuming you were
even in the kernel at the time).

BTW, there is a reference in the parisc-linux archives to trap handlers in the
Utah code, Mach I presume, which
may be useful as a model upon which to base HPMC/TOC handlers in Linux for
PA-RISC. Maybe someday...

Regards,
Geoge G. Davis
Software Engineer,  Celestica Chelmsford Design Center
20 Alpha Road
Chelmsford, MA 01824

             reply	other threads:[~2000-03-28 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28 17:16 davisg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-29 17:11 [parisc-linux] Couple of questions davisg
2000-03-28 16:52 davisg
2000-03-29  5:44 ` Philippe Benard
2000-03-29  9:02 ` Corne Beerse
2000-03-29 18:52   ` willy
2000-03-29 19:10     ` Peter A. Peterson II
2000-03-29 21:58       ` willy
2000-03-27 14:43 davisg
2000-03-27 18:02 ` Philipp Rumpf
2000-03-28  9:20   ` Corne Beerse
2000-03-26 12:17 Bas Valkema
2000-03-26 18:02 ` Philipp Rumpf
2000-03-26 18:26 ` willy

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=852568B0.005EEA6A.00@tormta3.tor.cel.com \
    --to=davisg@celestica.com \
    --cc=b_valkema@hotmail.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@puffin.external.hp.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.