| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Xen1.2 NetBSD port snapshot available and set_gdt patch
> > 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.
Would it be useful to have simnple ELF loading support in the domain
builder? This would get rid of teh need for symtab munging and the
cheesy XenoGues stuff when building NetBSD.
> > 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.
If/when upgrading to 1.3, please be aware of a couple of interface
changes (there will also likely be more, as we add device-driver
isolation and proper bidirectional console support for example):
1. The MMU_update interface takes a physical pointer to a PTE, not a
virtual address.
2. The block-device and network I/O rings are now indexed using
non-wrapping counters. e.g. rather than
i = (i + 1) % RING_SIZE;
ent = ring[i];
you do
ent = ring[++i];
There are predefined index types NET_RING_IDX and BLK_RING_IDX.
The former change was required because I stripped locking out of the
page-management code and it's hard to ensure that the virtual-address
space doesn't change under your feet without using locks.
The latter change makes I/O easier to debug, and gets rid of nasty "is
this ring empty or full?" corner cases.
-- Keir
-------------------------------------------------------
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home