home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!Sirius.dfn.de!chx400!bernina!almesber
- From: almesber@nessie.cs.id.ethz.ch (Werner Almesberger)
- Subject: Re: shared libs - can everyone be happy with this?
- Message-ID: <1992Aug17.201501.2128@bernina.ethz.ch>
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
- References: <1992Aug17.144719.1961@crd.ge.com> <1992Aug17.151311.29507@ods.com> <LILJEBER.92Aug17203359@klaava.Helsinki.FI>
- Date: Mon, 17 Aug 1992 20:15:01 GMT
- Lines: 24
-
- In article <LILJEBER.92Aug17203359@klaava.Helsinki.FI> liljeber@klaava.Helsinki.FI (Mika Pekka Liljeberg) writes:
- > Would this break demand loading, then? I think not. A text page could still
- > be freed and reloaded on demand. Any library references on it would simply
- > get relinked, when the path of execution intercepted them.
-
- ... unless that address reference happens to cross a page boundary. Then
- you have five choices:
-
- - define this case as illegal. (Not that bad, but probbaly unpopular.)
- - provide a mechanism to fault in both pages at the same time.
- (Might be difficult.)
- - lock both pages in memory. (Very ugly.)
- - make both pages part of the process' data space. (Ugly.)
- - don't patch the call. (Now you're possibly incurring a huge performance
- penalty (at least compared to what you gain by modifying jumps),
- because you're going through the patching code whenever that call is
- performed.)
-
- - Werner
- --
- _________________________________________________________________________
- / Werner Almesberger, ETH Zuerich, CH almesber@nessie.cs.id.ethz.ch /
- / IFW A44 Tel. +41 1 254 7213 almesberger@rzvax.ethz.ch /
- /_BITNET:_ALMESBER@CZHETH5A__HEPNET/CHADNET:_[20579::]57414::ALMESBERGER_/
-