From: Christian Limpach <chris@pin.lu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: NetBSD port and a couple of remarks
Date: Wed, 28 Jan 2004 15:54:40 +0100 [thread overview]
Message-ID: <02fa01c3e5ae$a9352b10$070414ac@pin> (raw)
In-Reply-To: E1AlkjY-0000tp-00@wisbech.cl.cam.ac.uk
> Out of interest, how many man hours do you think it took you? I'm
> very impressed you managed to figure the Xen i/f out on your own
> without any help from Keir and the rest of us.
I think I spent 8-10 hours each day between 1/11 and 1/20 and after that it
was more sporadic, another 10 on 1/22 and about 4 each on 1/25 and 1/27.
I'd think between 95 and 120 hours total. I also noted some milestones:
- 1/11/2004: started with linux/mini-os install/experimentation
- 1/12/2004: add mini-os startup to NetBSD startup and make it load/start
- 1/12/2004: add arch/xeno tree
- 1/14/2004: add minimal console output support
- 1/17/2004: add timer event processing
- 1/17/2004: started work on xennet network driver
- 1/18/2004: pmap pd/pt/pa/ma cleanup
- 1/19/2004: hardclock call from timer event works
- 1/20/2004: boot init until cnopen over nfs
- 1/22/2004: add console device
- 1/22/2004: integrate Xen events into NetBSD interrupt system
- 1/25/2004: add npx support
- 1/27/2004: multi-user boot over nfs
I spend quite some time figuring out how some of the i386 cpu features
actually work (pagetable/GDT/LDT/TSS), how they are used in NetBSD and how
to rewrite using the Xen hypercalls.
> There's been a few fixes and improvements for the hypervisor i/f
> in the 1.2 tree, but I don't think it will take long to forward
> port NetBSD.
>
> We'll investigate your specific bug reports.
Good!
> > I hope to commit this to the NetBSD tree eventually. Or I'll make
patches
> > available after some cleaning up.
>
> Great! We'd be very pleased to put the patches in the xen
> distribution in the meantime, as soon as you're ready.
Thanks. I'll probably have a patch ready in a few days and I'll also know
if/how it gets into the NetBSD tree.
> There's a pretty recent src/binary tar ball in:
> www.cl.cam.ac.uk/netos/xen/downloads/xeno-1.2.tar.gz
>
> It's still in the form of a BK repository, but all of the files
> are checked out.
Thanks!
> BTW: I offered to buy dinner for anyone that did an OS port. I
> hope you'll take me up on that offer...
Oh, excellent! ;-)
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 prev parent reply other threads:[~2004-01-28 14:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 20:59 NetBSD port and a couple of remarks Christian Limpach
2004-01-28 7:44 ` Kip Macy
2004-01-28 8:07 ` Ian Pratt
2004-01-28 14:54 ` Christian Limpach [this message]
2004-01-28 10:49 ` Steven Hand
2004-01-28 16:23 ` Christian Limpach
2004-01-28 16:38 ` Steven Hand
2004-01-28 16:51 ` Keir Fraser
2004-01-28 17:05 ` Kip Macy
2004-01-28 18:35 ` Christian Limpach
2004-01-28 19:03 ` Ian Pratt
2004-01-28 21:28 ` Kip Macy
2004-01-28 22:59 ` Andi Kleen
2004-01-28 23:10 ` Kip Macy
2004-01-28 23:24 ` Andi Kleen
2004-01-28 23:48 ` Kip Macy
2004-01-29 0:19 ` Larry McVoy
2004-01-29 0:31 ` Kip Macy
2004-01-29 11:14 ` John Szakmeister
2004-01-28 11:24 ` Ian Pratt
2004-01-28 17:07 ` Christian Limpach
2005-03-12 20:59 ` Thorsten Glaser
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='02fa01c3e5ae$a9352b10$070414ac@pin' \
--to=chris@pin.lu \
--cc=Ian.Pratt@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.