Messages in this thread | | | Date | Wed, 15 Sep 1999 16:46:17 +0100 (BST) | From | Tigran Aivazian <> | Subject | [q] signal_map still needed in struct exec_domain? |
| |
Hi brethren,
I noticed that setup_frame() (on all archs) is quite happy with signal_invmap[] field of struct exec_domain and does not need the direct map (signal_map). But all existing exec_domains (riscos, solaris etc) still prepare both direct and inverse map arrays.
Why do they? Or should they not? Maybe some assembler routine does access signal_map by hardcoded offset (like it is done e.g. for ENTRY(lcall7) accessing exec_domain of the current's task_struct) in which case, I would appreciate someone to point it out to me.
Thanks, Tigran.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |