From: Christian Limpach <chris@pin.lu>
To: xen-devel@lists.sourceforge.net
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Subject: NetBSD port updated
Date: Sat, 7 Feb 2004 17:31:32 +0100 [thread overview]
Message-ID: <10d401c3ed97$d9cf9350$070414ac@pin> (raw)
Hello!
I've updated the NetBSD port:
- use pagetable pinning (requires Xen1.2 with ChangeSet 1.705 applied).
- fix PG_ZERO page not empty failure
- fix memory leak in network driver
- boot regular/unmangled kernel from NetBSD specific domain builder
NetBSD seems quite stable with these changes now...
See http://lola.pin.lu/netbsd/xen/readme-040207 for details on how to get
started...
Ian/Keir: the patches for the domain builder are at
http://lola.pin.lu/netbsd/xen/xen12-netbsd_domaintools.diff
I had to modify xc_dom_create.py (and called it xc_dom_create_nb.py for now)
because I don't ((feel like I) want to) know how to call function references
in python ;-) If you make the builder call indirect through builder_fn,
xc_dom_create.py should work for both NetBSD and Linux. There could
probably be some more code sharing between xc_linux_build.c and
xc_netbsd_build.c, maybe even auto-detection...
christian
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-02-07 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 16:31 Christian Limpach [this message]
2004-02-07 17:38 ` NetBSD port updated Keir Fraser
2004-02-07 17:44 ` Ian Pratt
2004-02-07 17:54 ` Keir Fraser
2004-02-07 21:06 ` Christian Limpach
2004-02-08 9:19 ` Ian Pratt
2004-02-08 9:24 ` Keir Fraser
2004-02-08 9:21 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='10d401c3ed97$d9cf9350$070414ac@pin' \
--to=chris@pin.lu \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.