All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@puffin.external.hp.com>
To: davisg@Celestica.com
Cc: Bas Valkema <b_valkema@hotmail.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Couple of questions
Date: Mon, 27 Mar 2000 11:02:01 -0700	[thread overview]
Message-ID: <20000327110201.A10222@puffin.external.hp.com> (raw)
In-Reply-To: <852568AF.00513999.00@tormta3.tor.cel.com>; from davisg@Celestica.com on Mon, Mar 27, 2000 at 09:43:28AM -0500

> Just a slight clarification on what TOC does. Although on the surface the
> 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 ?

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

	Philipp Rumpf

  reply	other threads:[~2000-03-27 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-27 14:43 [parisc-linux] Couple of questions davisg
2000-03-27 18:02 ` Philipp Rumpf [this message]
2000-03-28  9:20   ` Corne Beerse
  -- strict thread matches above, loose matches on Subject: below --
2000-03-29 17:11 davisg
2000-03-28 17:16 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-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=20000327110201.A10222@puffin.external.hp.com \
    --to=prumpf@puffin.external.hp.com \
    --cc=b_valkema@hotmail.com \
    --cc=davisg@Celestica.com \
    --cc=parisc-linux@thepuffingroup.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.