RE: RFC - freeing up ar.k5

From: Luck, Tony <>
Date: 2004-10-02 08:46:34
>> Still not sure where to take this.  One suggestion I did get 
>> was to use this as a proof of concept that ar.k5 could be freed
>> up if some super wonderful application for a ar.k register comes
>> along, so it's ok to use our last completely free register
>> (ar.k3) for the INIT/MCA code.
>So which way should I go?
>I could build on the current ia64_mca_tlb_info structure and avoid
>the cpu reg issue, or use ar.k3 for the INIT/MCA code.
>At this point I'm just interested in make some forward progress, so
>either way is fine.

Luckily Linus just added "Documentation/ManagementStyle" to the source
tree to help me through this.  Read it, it's pretty funny.

This looks like a decision that could be undone without too much
pain later ... so I'll say "yes", let's use ar.k3 for the physical
address of the percpu area as a "preliminary decision" ... if it turns
out to be bad, then I'll admit to being a "nincompoop", and we'll add
more loops looking for cr.lid in the ia64_mca_tlb_list[] to get ar.k3
free again.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Fri Oct 1 18:51:31 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:31 EST