All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] [PATCH] MCA recovery for TLB faults for 2.4
Date: Mon, 02 Jun 2003 18:19:05 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706110@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706058@msgid-missing>

>>>>> On Mon, 2 Jun 2003 10:00:28 -0700, "Luck, Tony" <tony.luck@intel.com> said:

  Tony> At the moment the trust level is extremely high.  Linux
  Tony> doesn't even provide a checksum for the ia64_os_mca_dispatch
  Tony> entry code when it registers it with the SAL.

That's true.

  Tony> A checksum in the list of saved translations would only be
  Tony> part of reducing the level of trust ... we'd also need to
  Tony> validate that the entire code path has the correct code (not
  Tony> just the entry point).  There are several other data items on
  Tony> which the code also relies which a truly paranoid MCA handler
  Tony> would also need to validate.

I probably just don't understand what the plan is here.  Are you
planning to fix everything in one fell swoop?  If not, I think
incrementally improving the situation makes sense (i.e., if you work
on piece X, make X as solid as possible; over time do this for more
and more pieces of the MCA subsystem).  There is no doubt that making
the entire MCA subsystem as robust as possible involves a huge amount
of rather tricky work.  Same goes for the INIT path, of course (there
are obvious ways to deadlock it right now; probably something that
could benefit from a reasonably generic lock-busting infrastructure).

	--david


  parent reply	other threads:[~2003-06-02 18:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 20:35 [Linux-ia64] [PATCH] MCA recovery for TLB faults for 2.4 Luck, Tony
2003-05-28 22:37 ` Keith Owens
2003-05-31  1:34 ` David Mosberger
2003-06-02 17:00 ` Luck, Tony
2003-06-02 18:19 ` David Mosberger [this message]
2003-06-02 18:34 ` Luck, Tony
2003-06-02 18:39 ` David Mosberger

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=marc-linux-ia64-105590723706110@msgid-missing \
    --to=davidm@napali.hpl.hp.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 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.