lkml.org 
[lkml]   [1999]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [q] signal_map still needed in struct exec_domain?
Date
From

tigran@sco.COM said:
> 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.

The iBCS code uses it. Take a look at
ftp://ftp.infradead.org/pub/abi/abi-diffs-3.gz



---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.



-
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/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.036 / U:1.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site