vkernel & GSoC, some questions

Matthew Dillon dillon at apollo.backplane.com
Mon Mar 17 20:40:07 UTC 2008

:I don't think there's an issue that needs solving, GCC has -nostdlib and 
:-fno-builtin for precisely this reason.

    You are missing the point entirely.  The point is to allow the vkernel
    to use libc, aka allow it to be compiled, linked, and run as a normal
    user process.  What is your rationale for trying to bypass libc?  Why
    is it so important to you that the kernel retain all those conflicting
    symbols when it takes literally just an hour of work to fix all the

:Anyway, I agree that this is the least of someone's worries during a 
:hypothetical port of the dragonfly vkernel code.  Just so everyone is 
:clear, the scope of such an effort would not be "port the code", it 
:would be "port the code and also finish it".

    Jeeze, you make it sound like it is some incomplete mess when it is 
    far, far from that.  The vkernel is complete, the APIs are complete.
    It isn't finished in the sense that certain aspects of it, primarily
    the 'disk' emulation, is not very well optimized, but you are doing
    the work an extreme disservice by belittling it with undeserving
    labels.  Do you think that hypervisors are magically more efficient?
    Do you honestly believe that having to spend thousands of man hours
    writing one hack after another to make windows run well on VMWare is
    the proper development path?  Do you really want to load opaque black
    boxes into FreeBSD's kernel which you have no control over?

    If you have some disagreement about the APIs used to implement the
    emulation then I am all ears.  Is there something you don't like
    about the new mmap() feature?  Is there something you don't like
    about the new vmspace_*() system calls?

    I'm a perfectionist but my work output is also limited.  You are quite
    welcome to help improve our projects, but if you are expecting me to
    dedicate my entire life to 'improving' one single aspect of our project,
    the vkernel in this case, just to satisfy some twisted idea of
    completeness, it isn't going to happen.  Code submissions are always
    welcome in our corner of the woods.

					Matthew Dillon 
					<dillon at backplane.com>

More information about the freebsd-hackers mailing list