movitz-cvs March 2004

movitz-cvs@common-lisp.net

1 participants
131 discussions

[movitz-cvs] CVS update: movitz/losp/muerte/run-time-context.lisp
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/movitz/losp/muerte In directory common-lisp.net:/tmp/cvs-serv7228 Modified Files: run-time-context.lisp Log Message: Write %run-time-context-slot in terms of %word-offset. Date: Tue Mar 30 04:12:35 2004 Author: ffjeld Index: movitz/losp/muerte/run-time-context.lisp diff -u movitz/losp/muerte/run-time-context.lisp:1.2 movitz/losp/muerte/run-time-context.lisp:1.3 --- movitz/losp/muerte/run-time-context.lisp:1.2 Thu Mar 18 04:23:01 2004 +++ movitz/losp/muerte/run-time-context.lisp Tue Mar 30 04:12:35 2004 @@ -10,7 +10,7 @@ ;;;; Author: Frode Vatvedt Fjeld <frodef(a)acm.org> ;;;; Created at: Wed Nov 12 18:33:02 2003 ;;;; -;;;; $Id: run-time-context.lisp,v 1.2 2004/03/18 09:23:01 ffjeld Exp $ +;;;; $Id: run-time-context.lisp,v 1.3 2004/03/30 09:12:35 ffjeld Exp $ ;;;; ;;;;------------------------------------------------------------------ @@ -56,7 +56,7 @@ (word (memref context -6 (third slot) :lisp)) (code-vector-word - (memref context -6 (third slot) :lisp-code-vector)) + (%word-offset (memref context -6 (third slot) :lisp) -2)) (lu32 (memref context -6 (third slot) :unsigned-byte32)))))

1 0

[movitz-cvs] CVS update: movitz/losp/muerte/scavenge.lisp
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/movitz/losp/muerte In directory common-lisp.net:/tmp/cvs-serv13258 Modified Files: scavenge.lisp Log Message: In map-heap-words, only write back the new word if the function changes it. Seems like an obvious way to reduce pressure on the memory subsystem, and increased speed by about 5% on my test HW. Date: Tue Mar 30 03:50:12 2004 Author: ffjeld Index: movitz/losp/muerte/scavenge.lisp diff -u movitz/losp/muerte/scavenge.lisp:1.1 movitz/losp/muerte/scavenge.lisp:1.2 --- movitz/losp/muerte/scavenge.lisp:1.1 Mon Mar 29 09:30:22 2004 +++ movitz/losp/muerte/scavenge.lisp Tue Mar 30 03:50:12 2004 @@ -10,7 +10,7 @@ ;;;; Author: Frode Vatvedt Fjeld <frodef(a)acm.org> ;;;; Created at: Mon Mar 29 14:54:08 2004 ;;;; -;;;; $Id: scavenge.lisp,v 1.1 2004/03/29 14:30:22 ffjeld Exp $ +;;;; $Id: scavenge.lisp,v 1.2 2004/03/30 08:50:12 ffjeld Exp $ ;;;; ;;;;------------------------------------------------------------------ @@ -87,7 +87,8 @@ ((typep x 'pointer) (let ((new (funcall function x))) (check-type new pointer) - (setf (memref i 0 0 :lisp) new))))))) + (unless (eq x new) + (setf (memref i 0 0 :lisp) new)))))))) (values)) (defun map-stack-words (function start-stack-frame)

1 0

[movitz-cvs] CVS update: public_html/movitz.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv12770 Modified Files: movitz.html Log Message: dumdidum. Date: Tue Mar 30 03:35:32 2004 Author: ffjeld Index: public_html/movitz.html diff -u public_html/movitz.html:1.5 public_html/movitz.html:1.6 --- public_html/movitz.html:1.5 Tue Mar 30 03:31:10 2004 +++ public_html/movitz.html Tue Mar 30 03:35:32 2004 @@ -10,7 +10,7 @@ Author: Frode Vatvedt Fjeld <frodef(a)acm.org> Created at: Wed Nov 5 09:55:54 2003 - $Id: movitz.html,v 1.5 2004/03/30 08:31:10 ffjeld Exp $ + $Id: movitz.html,v 1.6 2004/03/30 08:35:32 ffjeld Exp $ --> @@ -20,7 +20,7 @@ </head> <body> <h1>Movitz: A Common Lisp OS development platform</h1> -<tt>$Id: movitz.html,v 1.5 2004/03/30 08:31:10 ffjeld Exp $</tt> +<tt>$Id: movitz.html,v 1.6 2004/03/30 08:35:32 ffjeld Exp $</tt> <h2><a href="files/">Files</a></h2> <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its @@ -178,9 +178,9 @@ los0. Note that under this simple scheme there is no way for objects to be promoted from the two 256 KB buffers, so you cannot have more than this amount of live, dynamically allocated data. You may trigger -the GC process explicitly with <tt>(init::stop-and-copy)</tt>. Note -that there are still several rough edges remaining this GC -implementation, e.g. it will not behave across any kind of interrupt. +the GC process explicitly with <tt>(stop-and-copy)</tt>. Note that +there are still several rough edges remaining this GC implementation, +e.g. it will not behave across any kind of interrupt. <h2>About OS design in Common Lisp</h2>

1 0

[movitz-cvs] CVS update: public_html/movitz.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv18848 Modified Files: movitz.html Log Message: ..and a bit more. Date: Tue Mar 30 03:31:10 2004 Author: ffjeld Index: public_html/movitz.html diff -u public_html/movitz.html:1.4 public_html/movitz.html:1.5 --- public_html/movitz.html:1.4 Tue Mar 30 03:27:57 2004 +++ public_html/movitz.html Tue Mar 30 03:31:10 2004 @@ -10,7 +10,7 @@ Author: Frode Vatvedt Fjeld <frodef(a)acm.org> Created at: Wed Nov 5 09:55:54 2003 - $Id: movitz.html,v 1.4 2004/03/30 08:27:57 ffjeld Exp $ + $Id: movitz.html,v 1.5 2004/03/30 08:31:10 ffjeld Exp $ --> @@ -20,7 +20,7 @@ </head> <body> <h1>Movitz: A Common Lisp OS development platform</h1> -<tt>$Id: movitz.html,v 1.4 2004/03/30 08:27:57 ffjeld Exp $</tt> +<tt>$Id: movitz.html,v 1.5 2004/03/30 08:31:10 ffjeld Exp $</tt> <h2><a href="files/">Files</a></h2> <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its @@ -177,9 +177,10 @@ heap, which tends to be somewhere between one and two megabytes in los0. Note that under this simple scheme there is no way for objects to be promoted from the two 256 KB buffers, so you cannot have more -than this amount of live, dynamically allocated data. Note that there -are still several rough edges remaining this GC implementation, -e.g. it will not behave across e.g. any kind of interrupt. +than this amount of live, dynamically allocated data. You may trigger +the GC process explicitly with <tt>(init::stop-and-copy)</tt>. Note +that there are still several rough edges remaining this GC +implementation, e.g. it will not behave across any kind of interrupt. <h2>About OS design in Common Lisp</h2>

1 0

[movitz-cvs] CVS update: public_html/movitz.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv19780 Modified Files: movitz.html Log Message: Added a bit more about map-stack-words. Date: Tue Mar 30 03:27:57 2004 Author: ffjeld Index: public_html/movitz.html diff -u public_html/movitz.html:1.3 public_html/movitz.html:1.4 --- public_html/movitz.html:1.3 Tue Mar 30 03:21:18 2004 +++ public_html/movitz.html Tue Mar 30 03:27:57 2004 @@ -10,7 +10,7 @@ Author: Frode Vatvedt Fjeld <frodef(a)acm.org> Created at: Wed Nov 5 09:55:54 2003 - $Id: movitz.html,v 1.3 2004/03/30 08:21:18 ffjeld Exp $ + $Id: movitz.html,v 1.4 2004/03/30 08:27:57 ffjeld Exp $ --> @@ -20,7 +20,7 @@ </head> <body> <h1>Movitz: A Common Lisp OS development platform</h1> -<tt>$Id: movitz.html,v 1.3 2004/03/30 08:21:18 ffjeld Exp $</tt> +<tt>$Id: movitz.html,v 1.4 2004/03/30 08:27:57 ffjeld Exp $</tt> <h2><a href="files/">Files</a></h2> <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its @@ -160,7 +160,9 @@ 32)</tt> in memory, so it will not recognized as pointers by e.g. <tt>map-heap-words</tt>. Hence, this function must be used explicitly over each live control stack in order to capture all -pointers in the system.</li> +pointers in the system. Another reason why stacks are special, is that +they contain untagged pointers to code-vectors, and this requires +special treatment. </li> </ul>

1 0

[movitz-cvs] CVS update: public_html/index.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv19120 Modified Files: index.html Log Message: Add link to GC info in movitz.html. Date: Tue Mar 30 03:22:10 2004 Author: ffjeld Index: public_html/index.html diff -u public_html/index.html:1.15 public_html/index.html:1.16 --- public_html/index.html:1.15 Tue Mar 30 03:09:20 2004 +++ public_html/index.html Tue Mar 30 03:22:10 2004 @@ -16,7 +16,8 @@ <h3>Recent news</h3> <p> <i>March 30, 2004:</i> There is now GC support in Muerte, and an - almost functional GC architecture included in the los0 image. + almost functional GC architecture included in the los0 image. Some + info is also added <a href="movitz.html#GC">here</a>. <p> For more news, see the <a href="files/ChangeLog"><tt>ChangeLog</tt></a>.

1 0

[movitz-cvs] CVS update: public_html/movitz.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv15200 Modified Files: movitz.html Log Message: Some re-wording. Date: Tue Mar 30 03:21:19 2004 Author: ffjeld Index: public_html/movitz.html diff -u public_html/movitz.html:1.2 public_html/movitz.html:1.3 --- public_html/movitz.html:1.2 Tue Mar 30 03:04:00 2004 +++ public_html/movitz.html Tue Mar 30 03:21:18 2004 @@ -10,7 +10,7 @@ Author: Frode Vatvedt Fjeld <frodef(a)acm.org> Created at: Wed Nov 5 09:55:54 2003 - $Id: movitz.html,v 1.2 2004/03/30 08:04:00 ffjeld Exp $ + $Id: movitz.html,v 1.3 2004/03/30 08:21:18 ffjeld Exp $ --> @@ -20,7 +20,7 @@ </head> <body> <h1>Movitz: A Common Lisp OS development platform</h1> -<tt>$Id: movitz.html,v 1.2 2004/03/30 08:04:00 ffjeld Exp $</tt> +<tt>$Id: movitz.html,v 1.3 2004/03/30 08:21:18 ffjeld Exp $</tt> <h2><a href="files/">Files</a></h2> <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its @@ -139,38 +139,45 @@ required to interface any hardware without resorting to inline assembly is either in place or can easily be added. -<h3>Garbage Collection</h3> +<h3>Garbage Collection</h3> <a name="GC"> There is now preliminary support for GC in Muerte. This support is two things. Firstly, the object layouts, stack discipline, etc. are such that the system as such is amenable to scanning for GC purposes. Secondly, there are two functions in Muerte that are -expectedly very useful for implementing many kinds of GC: +expectedly useful for implementing GC architectures: <ul> <li> <tt>map-heap-words</tt> maps a function over every potential -pointer in a specified memory region. This can be used both to -implement GC as such (if the function migrates objects according to -some GC scheme), and as a help for GC debugging (if the function -merely checks some invariant or prints information). </li> <li> -<tt>map-stack-words</tt> works similarly for a control stack. A stack -is wrapped as a vector specialized to <tt>(unsigned-byte 32)</tt> in -memory, so it will not recognized as pointers by +pointer in a specified memory region, denoted by start and end memory +locations. This can be used both to implement GC as such (if the +function migrates objects according to some GC scheme), and as a help +for GC debugging (if the function merely checks some invariant or +prints information). </li> + +<li> <tt>map-stack-words</tt> works similarly for a control stack. A +stack is wrapped as a vector specialized to <tt>(unsigned-byte +32)</tt> in memory, so it will not recognized as pointers by e.g. <tt>map-heap-words</tt>. Hence, this function must be used -explicitly in order to capture all pointers in the system.</li> +explicitly over each live control stack in order to capture all +pointers in the system.</li> + </ul> The los0 image currently uses these two functions to implement a rather simple Cheney-style stop-and-copy GC architecture. In short, two 256 KB buffers are set up, and the memory allocation primitives -are changed to allocate from one of these buffers designated +are changed to allocate from one of these buffers designated as "newspace". When newspace goes full, the roles of oldspace and -newspace are switched, and the (newly demoted) oldspace is -evacuated. This evacuation is performed rather naively, namely by -scanning the entire heap, which tends to be somewhere between one and -two megabytes in los0. Note that under this simple scheme there is no -way for objects to be promoted from the two 256 KB buffers, so you -cannot have more than this amount of live, dynamically allocated data. +newspace are switched, and the live objects in the (newly become) +oldspace are evacuated into the (newly become) newspace. This +evacuation is performed rather naively, namely by scanning the entire +heap, which tends to be somewhere between one and two megabytes in +los0. Note that under this simple scheme there is no way for objects +to be promoted from the two 256 KB buffers, so you cannot have more +than this amount of live, dynamically allocated data. Note that there +are still several rough edges remaining this GC implementation, +e.g. it will not behave across e.g. any kind of interrupt. <h2>About OS design in Common Lisp</h2>

1 0

[movitz-cvs] CVS update: public_html/index.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv31490 Modified Files: index.html Log Message: Typo fixes. Date: Tue Mar 30 03:09:21 2004 Author: ffjeld Index: public_html/index.html diff -u public_html/index.html:1.14 public_html/index.html:1.15 --- public_html/index.html:1.14 Tue Mar 30 03:07:42 2004 +++ public_html/index.html Tue Mar 30 03:09:20 2004 @@ -15,11 +15,11 @@ <h3>Recent news</h3> - <p> <i>March 30. 2004</i> There is now GC support in Muerte, and an + <p> <i>March 30, 2004:</i> There is now GC support in Muerte, and an almost functional GC architecture included in the los0 image. <p> For more news, see the <a - href="files/ChangeLog"><tt>ChageLog</tt></a>. + href="files/ChangeLog"><tt>ChangeLog</tt></a>. <h3>Introduction</h3>

1 0

[movitz-cvs] CVS update: public_html/index.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv10882 Modified Files: index.html Log Message: Added a "Recent news" section. Date: Tue Mar 30 03:07:42 2004 Author: ffjeld Index: public_html/index.html diff -u public_html/index.html:1.13 public_html/index.html:1.14 --- public_html/index.html:1.13 Tue Feb 10 06:42:30 2004 +++ public_html/index.html Tue Mar 30 03:07:42 2004 @@ -13,6 +13,14 @@ <h1>Movitz: a Common Lisp x86 development platform</h1> </div> + <h3>Recent news</h3> + + <p> <i>March 30. 2004</i> There is now GC support in Muerte, and an + almost functional GC architecture included in the los0 image. + + <p> For more news, see the <a + href="files/ChangeLog"><tt>ChageLog</tt></a>. + <h3>Introduction</h3> <p> The Movitz system aspires to be an implementation of ANSI Common

1 0

[movitz-cvs] CVS update: public_html/movitz.html
by Frode Vatvedt Fjeld 30 Mar '04

30 Mar '04

Update of /project/movitz/cvsroot/public_html In directory common-lisp.net:/tmp/cvs-serv15538 Modified Files: movitz.html Log Message: Added info about the new GC stuff. Date: Tue Mar 30 03:04:00 2004 Author: ffjeld Index: public_html/movitz.html diff -u public_html/movitz.html:1.1 public_html/movitz.html:1.2 --- public_html/movitz.html:1.1 Tue Jan 13 08:31:59 2004 +++ public_html/movitz.html Tue Mar 30 03:04:00 2004 @@ -10,7 +10,7 @@ Author: Frode Vatvedt Fjeld <frodef(a)acm.org> Created at: Wed Nov 5 09:55:54 2003 - $Id: movitz.html,v 1.1 2004/01/13 13:31:59 ffjeld Exp $ + $Id: movitz.html,v 1.2 2004/03/30 08:04:00 ffjeld Exp $ --> @@ -20,7 +20,7 @@ </head> <body> <h1>Movitz: A Common Lisp OS development platform</h1> -<tt>$Id: movitz.html,v 1.1 2004/01/13 13:31:59 ffjeld Exp $</tt> +<tt>$Id: movitz.html,v 1.2 2004/03/30 08:04:00 ffjeld Exp $</tt> <h2><a href="files/">Files</a></h2> <p> The latest <a href="files/los0.img"> los0 kernel image</a> and its @@ -141,17 +141,36 @@ <h3>Garbage Collection</h3> -There is no garbage collection scheme implemented yet. Whether a fully -operational GC <em>can</em> be part of Muerte, or whether it requires -extensive support from the particular MoKA run-time, remains to be -seen. - -I expect that it turns out that some middle ground must be found: The -basic mechanisms and hooks needed to perform GC will be provided by -Muerte, and the MoKA uses this to provide full GC service (if it will -provide GC at all). In this spirit, I hope to add something like a -simple stop-and-copy GC to los0 soon. +There is now preliminary support for GC in Muerte. This support is two +things. Firstly, the object layouts, stack discipline, etc. are such +that the system as such is amenable to scanning for GC +purposes. Secondly, there are two functions in Muerte that are +expectedly very useful for implementing many kinds of GC: +<ul> + +<li> <tt>map-heap-words</tt> maps a function over every potential +pointer in a specified memory region. This can be used both to +implement GC as such (if the function migrates objects according to +some GC scheme), and as a help for GC debugging (if the function +merely checks some invariant or prints information). </li> <li> +<tt>map-stack-words</tt> works similarly for a control stack. A stack +is wrapped as a vector specialized to <tt>(unsigned-byte 32)</tt> in +memory, so it will not recognized as pointers by +e.g. <tt>map-heap-words</tt>. Hence, this function must be used +explicitly in order to capture all pointers in the system.</li> +</ul> +The los0 image currently uses these two functions to implement a +rather simple Cheney-style stop-and-copy GC architecture. In short, +two 256 KB buffers are set up, and the memory allocation primitives +are changed to allocate from one of these buffers designated +"newspace". When newspace goes full, the roles of oldspace and +newspace are switched, and the (newly demoted) oldspace is +evacuated. This evacuation is performed rather naively, namely by +scanning the entire heap, which tends to be somewhere between one and +two megabytes in los0. Note that under this simple scheme there is no +way for objects to be promoted from the two 256 KB buffers, so you +cannot have more than this amount of live, dynamically allocated data. <h2>About OS design in Common Lisp</h2>

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

movitz-cvs March 2004