Skip to contentSkip to conversation

load-store emulation with SIGSEGV (gate.S bug?)

DISCUSSION Jeffrey William Lake 3 participants 3 messages Oct 17, 2003

lore
Share & tools
lore
#0 lore raw

After some investigation I discovered that a "flushrs" at the start of my signal handler cured the problem.

Looking at "arch/ia64/kernel/gate.S" revealed that a "cover" is used to get the registers onto the backing store (commented as such several times), but by my understanding there is enough scope from the instruction description that they may be cached. Therefore, should gate.S include a "flushrs" as well or, for performance reasons be left for the user to decide?

#1 lore raw
Quoted 7 lines · Jeffrey William Lake

After some investigation I discovered that a "flushrs" at the start of my signal handler cured the problem.

Looking at "arch/ia64/kernel/gate.S" revealed that a "cover" is used to get the registers onto the backing store (commented as such several times), but by my understanding there is enough scope from the instruction description that they may be cached.

cover only marks the current frame (r32+) as dirty. It does not write the dirty registers out to backing store, that is left to RSE to do at its leisure. flushrs forces RSE to write the dirty registers out to memory.

Quoted 3 lines

Therefore, should gate.S include a
"flushrs" as well or, for performance reasons be left for the user to decide?

Probably best left for the user to decide. The majority of signal handlers will not require the registers to be flushed.

#2 lore raw
In reply to Jeffrey William Lake
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Jeffrey William Lake

Jeffrey> After some investigation I discovered that a "flushrs" at Jeffrey> the start of my signal handler cured the problem.

Jeffrey> Looking at "arch/ia64/kernel/gate.S" revealed that a Jeffrey> "cover" is used to get the registers onto the backing store Jeffrey> (commented as such several times), but by my understanding Jeffrey> there is enough scope from the instruction description that Jeffrey> they may be cached. Therefore, should gate.S include a Jeffrey> "flushrs" as well or, for performance reasons be left for Jeffrey> the user to decide?

There is no need to have a flushrs in gate.S. If you want to access the register-backing store in memory, you'll need to do a flushrs anyhow. BTW: you could use libunwind to access the registers, as that would save you from having to know such details. But of course it may be a bit overkill (probably not too bad, though).

	--david