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: Sat, 31 May 2003 01:34:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706101@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706058@msgid-missing>
>>>>> On Wed, 28 May 2003 13:35:53 -0700, "Luck, Tony" <tony.luck@intel.com> said:
Tony> The underlying algorithm is to save information about what
Tony> each of the ITR/DTR registers is mapping, then at MCA time we
Tony> can purge the whole TLB (TC and TR) and reload the TR
Tony> registers before jumping to virtual mode.
Are you just blindly trusting that memory is still correct after
getting a TLB error report? Wouldn't you want to have a checksum to
validate that the list of saved translations is probably correct.
Otherwise, it seems to me the TLB purge could make a bad situation
worse.
--david
next prev parent reply other threads:[~2003-05-31 1:34 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 [this message]
2003-06-02 17:00 ` Luck, Tony
2003-06-02 18:19 ` David Mosberger
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-105590723706101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox