From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch] Per CPU MCA/INIT data save areas
Date: Thu, 16 Sep 2004 11:44:33 +0000 [thread overview]
Message-ID: <2828.1095335073@ocs3.ocs.com.au> (raw)
In-Reply-To: <200408312112.i7VLCPc9002392@ben.americas.sgi.com>
On Wed, 15 Sep 2004 09:28:58 -0700,
"Luck, Tony" <tony.luck@intel.com> wrote:
>>Unless anyone has a better solution, I think Keith's suggestion is the
>>next best alternative. It is no worse than the current code
>>(in terms of off-node access) and allows forward progress on the rest
>>of the code.
>
>Take a look at the MCA-TLB recovery code. It saves per-cpu
>information in the "ia64_mca_tlb_list[]" array, and searches
>through it for an entry that matches cr.lid at fault time.
>
>You could add extra element(s) to this structure for the percpu
>areas.
What about storing the physical address of the per-cpu data area in
ar.k3?
AFAICT we can also reclaim ar.k5 (FPU_OWNER), that field is rarely used
and can be moved to the per_cpu data area.
next prev parent reply other threads:[~2004-09-16 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 21:12 [Patch] Per CPU MCA/INIT data save areas Russ Anderson
2004-09-01 5:25 ` Luck, Tony
2004-09-14 11:43 ` Takao Indoh
2004-09-14 15:30 ` Russ Anderson
2004-09-15 1:32 ` Keith Owens
2004-09-15 15:43 ` Russ Anderson
2004-09-15 16:28 ` Luck, Tony
2004-09-16 11:44 ` Keith Owens [this message]
2004-09-16 18:33 ` Russ Anderson
2004-09-16 19:51 ` Luck, Tony
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=2828.1095335073@ocs3.ocs.com.au \
--to=kaos@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