* intercept_table
@ 2006-12-17 19:49 barbalace
0 siblings, 0 replies; only message in thread
From: barbalace @ 2006-12-17 19:49 UTC (permalink / raw)
To: linuxppc-embedded
I want to modify at run-time the linux interrupt handler, I see in
/arch/ppc/kernel/head.S a very interesting array: intercept_table. I don't
understand why there are only few references, in my kernel 2.6.14 there are:
intercept_table:
.long 0, 0, i0x200, i0x300, i0x400, 0, i0x600, i0x700
.long i0x800, 0, 0, 0, 0, i0xd00, 0, 0
.long 0, 0, 0, i0x1300, 0, 0, 0, 0
.long 0, 0, 0, 0, 0, 0, 0, 0
.long 0, 0, 0, 0, 0, 0, 0, 0
.long 0, 0, 0, 0, 0, 0, 0, 0
why 0x500 is missed? Is considered not safe to make user change it? ...so I say
that I want to change some of this pointers at run time but reading head.S I
see that the address of i0x* are in a .text segment, can I write in this
segment? Before I write must I turn off MMU or mask some traps?
Regards,
Antonio Barbalace
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-12-17 20:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-17 19:49 intercept_table barbalace
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).