From: barbalace@igi.cnr.it
To: linuxppc-embedded@ozlabs.org
Subject: intercept_table
Date: Sun, 17 Dec 2006 20:49:59 +0100 [thread overview]
Message-ID: <1166384999.45859f6743e9f@webmail.igi.cnr.it> (raw)
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
reply other threads:[~2006-12-17 20:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1166384999.45859f6743e9f@webmail.igi.cnr.it \
--to=barbalace@igi.cnr.it \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).