public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch] Per CPU MCA/INIT data save areas
Date: Wed, 15 Sep 2004 01:32:38 +0000	[thread overview]
Message-ID: <6738.1095211958@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <200408312112.i7VLCPc9002392@ben.americas.sgi.com>

On Tue, 14 Sep 2004 10:30:44 -0500 (CDT), 
Russ Anderson <rja@sgi.com> wrote:
>Thanks for the response.  Some comments below...
>Takao Indoh wrote:
>> BTW, I used tpa to get physical address, but I am not sure TLB is valid 
>> in the OS_INIT. tpa is available?
>
>There may not be a valid TLB.  That's why DATA_VA_TO_PA() cannot be used
>in the OS_MCA path.  LOAD_PHYSICAL() is used instead (in the original MCA code).  
>I'm not sure if LOAD_PHYSICAL() is sufficient either in this context (but that 
>may just be my lack of understanding).

LOAD_PHYSICAL() only works for physically unique addresses (one to one
mapping from virtual to physical address at load time), it does not
work for replicated areas like the per cpu data area.  As Russ has
said, tpa is not reliable in MCA/INIT paths, one of the possible
reasons for taking an MCA is an invalid tlb load :(.  Which means that
we need a second data area which contains the physical addresses of
each of the per cpu data areas.  MCA/INIT can do a LOAD_PHYSICAL() on
the start of that table, then index by cpu to get the physical address
of the local per cpu table.


  parent reply	other threads:[~2004-09-15  1:32 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 [this message]
2004-09-15 15:43 ` Russ Anderson
2004-09-15 16:28 ` Luck, Tony
2004-09-16 11:44 ` Keith Owens
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=6738.1095211958@kao2.melbourne.sgi.com \
    --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