Skip to contentSkip to conversation

Mapping addresses 0xe000... and 0xc000...

DISCUSSION Zoltan MENYHART 3 participants 3 messages Jan 15, 2004 – Jan 16, 2004

lore
Share & tools
lore
#0 lore raw

I guess most of my problems with "IA64_LOG_NEXT_BUFFER()", "salinfo_log_wakeup()", the KDB, unwinding the interrupted CPU's stack, etc. are related to the mapping of the addresses 0xe000... and 0xc000...

As far as I can see, when I touch such an address that is not mapped by any TR or TC entry (the walker is off for these address ranges), then the low level translation fault handler automatically inserts a new TC entry that maps the address in the usual way.

Yet an alternate translation fault vector is used if the PSR.ic is off (interrupts are disabled), and this handler does not map automatically the addresses 0xe000... and 0xc000...

We are obliged to take locks and to disable interrupts, see e.g. "IA64_LOG_NEXT_BUFFER()", the KDB.

Is it a VMM design issue not to allow automatic address mapping if the PSR.ic is off ? Should not we revise it :-) ?

Zoltan Menyhart

#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Zoltan MENYHART

Zoltan> Is it a VMM design issue not to allow automatic address Zoltan> mapping if the PSR.ic is off ? Should not we revise it :-) ?

In general, you can't take a fault while PSR.ic is off. Please see the Itanium system architecture for details (or any good kernel book on ia64... ;-)

	--david
#2 lore raw
In reply to Zoltan MENYHART
Quoted 5 lines · Zoltan MENYHART

I guess most of my problems with "IA64_LOG_NEXT_BUFFER()", "salinfo_log_wakeup()", the KDB, unwinding the interrupted CPU's stack, etc. are related to the mapping of the addresses 0xe000... and 0xc000...

Quoted 8 lines

As far as I can see, when I touch such an address that is not mapped by any TR or TC entry (the walker is off for these address ranges), then the low level translation fault handler automatically inserts a new TC entry that maps the address in the usual way.

Yet an alternate translation fault vector is used if the PSR.ic is off (interrupts are disabled), and this handler does not map automatically the addresses 0xe000... and 0xc000...

It is the "data nested TLB vector" that comes into play if PSR.ic is off and a TLB miss occurs. This fault is intentionally introduced to enable software (OSes) to handle nested faults if they ran into a TLB miss while doing low level fault handling. However when receiving that fault you do not get any information about it like the faulting address, the instruction address, ... . So software has to meet some conventions to be able to handle that kind of nested faults.

Quoted 2 lines

We are obliged to take locks and to disable interrupts, see e.g. "IA64_LOG_NEXT_BUFFER()", the KDB.

A solution might be the usage of some (free) TRs together with superpages up to 256MB that will be installed before accessing that memory locations. But be very carefully when doing that.

Quoted 3 lines

Is it a VMM design issue not to allow automatic address mapping if the PSR.ic is off ? Should not we revise it :-) ?

I think it is just a strict RISC design.

Quoted 1 line

Zoltan Menyhart

Christian