From: Christian Limpach <chris@pin.lu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen1.2 NetBSD port snapshot available and set_gdt patch for Xen1.2
Date: Tue, 3 Feb 2004 04:43:15 +0100 [thread overview]
Message-ID: <0a5901c3ea07$dc85c210$070414ac@pin> (raw)
In-Reply-To: E1AnqRg-000199-00@wisbech.cl.cam.ac.uk
> I see that the linux domain building routine was close enough to
> what you needed, so you didn't need a NetBSD specific routine.
yes, that was neat. I'm not happy with the hack of passing the symbol table
in as an initrd but I can fix that by embedding the symbol table into the
kernel image's data section. That would also remove the dumpsym program
from the build step and then I can include the mangling of the kernel into a
XenoGues image into the regular build. That would also make NetBSD/xen
cross-buildable, i.e. you can build it on a Linux host.
> How do you think it best to distribute this stuff? We'd be
> happy to put whatever you think appropriate in to the Xen tree.
I think there should be a netbsd config file for the domain creation tools,
once I've made the above changes.
I don't think you'd want the whole kernel tree in the Xen tree?
You could put the sys/arch/xen files into the Xen tree and also the 5
additional files which need changes, but it's not really stable/useable yet.
Also, I'm waiting for the OK to commit all this to the NetBSD tree and then
it won't make much sense to have it in the Xen tree anymore.
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-02-03 3:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 1:57 Xen1.2 NetBSD port snapshot available and set_gdt patch for Xen1.2 Christian Limpach
2004-02-03 2:37 ` Ian Pratt
2004-02-03 3:43 ` Christian Limpach [this message]
2004-02-03 8:42 ` Ian Pratt
2004-02-03 11:51 ` Rolf Neugebauer
2004-02-03 15:18 ` Xen1.2 NetBSD port snapshot available and set_gdtpatch " Christian Limpach
2004-02-03 21:49 ` A query I RATTAN
2004-02-05 13:24 ` Yan-Ching CHU
2004-02-05 13:58 ` Bin Ren
2004-02-03 23:27 ` Xen1.2 NetBSD port snapshot available and set_gdtpatch for Xen1.2 Keir Fraser
2004-02-03 8:44 ` Xen1.2 NetBSD port snapshot available and set_gdt patch " Keir Fraser
2004-02-03 14:54 ` Christian Limpach
2004-02-03 15:36 ` 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='0a5901c3ea07$dc85c210$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.