RE: [patch] per cpu MCA/INIT save areas (take 2)

Luck, Tony
2004-11-14T20:07:10Z

>Can you remind me why k3? Are you worried about the TR mapping the
>per-CPU region getting corrupted?

This isn't for correctness, or even efficiency (since this is a
very low frequency execution path). It is just to make the code
easier to read and maintain. The current code in the MCA path that
loops through the array of tlb info structures looking for the
one that matches the current cpus cr.lid is quite ugly. Replicating
it in the INIT code to find the per-cpu save+stack area will add
to the ugliness. Having the phys address of the per-cpu area in
ar.k3 would clean things up.

For the INIT case it would be safe to just "tpa" a per-cpu address,
but in the MCA case we shouldn't trust the TR mapping.

-Tony