Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!think.com!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.unix.internals Subject: Re: Interfaces for accessing kernel memory Message-ID: Date: 11 Dec 90 20:42:22 GMT References: <109449@convex.convex.com> Sender: news@OSF.ORG Organization: Open Software Foundation Lines: 18 In-reply-to: mike@wang.com's message of 11 Dec 90 13:31:54 GMT In article mike@wang.com (Mike Sullivan) writes: | When I worked at Alliant our arrangement was very simple, we mapped the | kernel memory into the process (typically read only ;-) which needed | access. Since my only interest was in the proc table, and a few other | structures which didn't have much call to change, it was immune to | OS changes. The direct mapping of kernel memory made linked lists very | easy to follow. This suffers from the same problem that diving into /vmunix and reading /dev/kmem does, namely that things can change from under you if you take a page fault or lose your time slice to another process at the wrong time...... -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142 Considering the flames and intolerance, shouldn't USENET be spelled ABUSENET?