Re: FreeBSD/xen structure

In message: <20070528130101.GD48357@xxxxxxx>
Rink Springer <rink@xxxxxxxxxxx> writes:
: Hi everyone,
:
: As I've just mailed to current@, work is well underway on the Xen
: porting effort. However, as not only I but a lot of people will want to
: see this work integrated into CURRENT at some point, I'd like to raise a
: discussion on the directory layout I'm using. It has not changed from
: Kip Macy's perforce tree, but I want to ensure that this will be
: suitable for inclusion in the tree.
:
: Basically, i386-xen (it's i386 only for now) is a sub-architecture just
: like pc98. The layout is the following:
:
: i386-xen/ Xen main tree
: compile/ Compile tree
: conf/ Kernel configs
: i386-xen/ Low-level code, comparable to i386/i386/
: include/ Include files - most include their i386/include/
: version, but some are different or extended.
:
: This is basically the machine-dependant stuff. Should a port of amd64-xen
: happen in the future, it would go using a simular directory layout.
:
: Xen-dependant but architecture-independant drivers (such as the Xen
: block device drivers) are put in the dev/xen directory. It should be
: possible to use these drivers in a amd64-xen version as well.
:
: I'd prefer to keep Xen in a i386-xen tree, as there are quite a lot of
: changes, comparable to the amd64 <-> i386 split. And I am sure we are
: not really in favour for douzens of #ifdef XEN's in the tree.

How pervasive are these diffs? And to what extent are you able to
reuse the i386 stuff? Can you characterize, say, the number of lines
and/or files that would be affected if you went the ifdef route? It
sounds like the tree is right, but that has its own cost and shouldn't
be undertaken lightly.

: Are there any questions, comments, remarks etc. on this layout? You can
: inspect the work in perforce (//projects/xen3); currently, none of my
: changes have been committed, but the layout is the same.

I like the layout, assuming it is needed.

Warner
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Industry db benchmark result on recent 2.6 kernels
    ... case is a representation of the actual hardware layout, ... where separate hardware component types have different IDs. ... this is tree walking and vector building/matching. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Private genealogical websites
    ... The layout is nice... ... the Descendant Tree was a big let down from the first ... able to move up and down the generations in the tree view. ... the layout of the Family Tree Database page... ...
    (soc.genealogy.britain)
  • Re: FreeBSD/xen structure
    ... discussion on the directory layout I'm using. ... Kip Macy's perforce tree, but I want to ensure that this will be ... it would go using a simular directory layout. ... Xen-dependant but architecture-independant drivers (such as the Xen ...
    (freebsd-arch)
  • FreeBSD/xen structure
    ... discussion on the directory layout I'm using. ... Kip Macy's perforce tree, but I want to ensure that this will be ... it would go using a simular directory layout. ... Xen-dependant but architecture-independant drivers (such as the Xen ...
    (freebsd-arch)
  • Re: In Regards to Swift Slamming
    ... > I am going into training to drive with Swift. ... Every company, every one, has drivers that think, at least on some days, the ... complaints and their duration over time. ... layout you couldn't get across the pasture. ...
    (misc.transport.trucking)