* [Q] MMU & VM
@ 1998-09-04 7:20 Graffiti
1998-09-04 9:53 ` Rik van Riel
1998-09-18 20:05 ` estafford
0 siblings, 2 replies; 4+ messages in thread
From: Graffiti @ 1998-09-04 7:20 UTC (permalink / raw
To: linux-mm
Hi all,
Before I ask my question, just to let you know, yes, I did look
for information on the web and various books to see if I could answer
this myself. Alas, no luck. Anyways, here goes:
Just how does an MMU work, and why do we need it to implement
virtual memory instead of handling it all in the kernel?
I've found quite a few texts on how VM works, but never why we
need an MMU or what an MMU does.
Can anyone recommend a good book on this?
-- DN (Learning 68000 asm as we speak. Now, for the Mac SE specs...)
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Q] MMU & VM
1998-09-04 7:20 [Q] MMU & VM Graffiti
@ 1998-09-04 9:53 ` Rik van Riel
1998-09-18 20:05 ` estafford
1 sibling, 0 replies; 4+ messages in thread
From: Rik van Riel @ 1998-09-04 9:53 UTC (permalink / raw
To: Graffiti; +Cc: linux-mm
On Fri, 4 Sep 1998, Graffiti wrote:
> Just how does an MMU work, and why do we need it to implement
> virtual memory instead of handling it all in the kernel?
> I've found quite a few texts on how VM works, but never why we
> need an MMU or what an MMU does.
>
> Can anyone recommend a good book on this?
Well, there's Tanenbaum's "Modern Operating Systems".
There's also a nice VM tutorial from CNE/CMU(?), which
is linked to from the Linux-MM homepage, VM Links.
http://www.phys.uu.nl/~riel/mm-patch/
Rik.
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: [Q] MMU & VM
1998-09-04 7:20 [Q] MMU & VM Graffiti
1998-09-04 9:53 ` Rik van Riel
@ 1998-09-18 20:05 ` estafford
1998-09-18 22:00 ` Zlatko Calusic
1 sibling, 1 reply; 4+ messages in thread
From: estafford @ 1998-09-18 20:05 UTC (permalink / raw
To: linux-mm
I was compiling the 2.1.122 kernel on an Alpha box (LX164) and had this error
pop up. Sounds like something you guys might recognize:
page_alloc.c: In function `__free_page':
page_alloc.c:169: internal error--unrecognizable insn:
(jump_insn 274 270 275 (return) -1 (nil)
(nil))
gcc: Internal compiler error: program cc1 got fatal signal 6
make[2]: *** [page_alloc.o] Error 1
make[1]: *** [first_rule] Error 2
make: *** [_dir_mm] Error 2
{standard input}: Assembler messages:
{standard input}:178: Warning: Missing .end or .bend at end of file
cpp: output pipe has been closed
If you need more info, please just say the word. Thanks!
----------------------------------
Ed Stafford
iXL Hosting Programming Engineer
E-Mail: estafford@ixl.com
----------------------------------
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Q] MMU & VM
1998-09-18 20:05 ` estafford
@ 1998-09-18 22:00 ` Zlatko Calusic
0 siblings, 0 replies; 4+ messages in thread
From: Zlatko Calusic @ 1998-09-18 22:00 UTC (permalink / raw
To: estafford; +Cc: linux-mm
estafford@ixl.com writes:
> I was compiling the 2.1.122 kernel on an Alpha box (LX164) and had this error
> pop up. Sounds like something you guys might recognize:
>
> page_alloc.c: In function `__free_page':
> page_alloc.c:169: internal error--unrecognizable insn:
> (jump_insn 274 270 275 (return) -1 (nil)
> (nil))
> gcc: Internal compiler error: program cc1 got fatal signal 6
> make[2]: *** [page_alloc.o] Error 1
> make[1]: *** [first_rule] Error 2
> make: *** [_dir_mm] Error 2
> {standard input}: Assembler messages:
> {standard input}:178: Warning: Missing .end or .bend at end of file
> cpp: output pipe has been closed
>
> If you need more info, please just say the word. Thanks!
>
Something like that has already been reported and it looks like older
egcs compilers have trouble with __builtin_return_address construct.
Either update your egcs, or #define __builtin_return_address(x) (0)
Hope it helps.
--
Posted by Zlatko Calusic E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
Unix Wizard: Someone who can type `cat > /vmunix` and get away with it!
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1998-09-18 22:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1998-09-04 7:20 [Q] MMU & VM Graffiti
1998-09-04 9:53 ` Rik van Riel
1998-09-18 20:05 ` estafford
1998-09-18 22:00 ` Zlatko Calusic
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 read-only IMAP folder(s) and NNTP newsgroup(s).