Date: Mon, 22 Oct 2007 13:50:26 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Kip Macy" <kip.macy@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: Should Xen be a sub-arch or a build option? Message-ID: <86lk9ve5bx.fsf@ds4.des.no> In-Reply-To: <b1fa29170710212056x5649a858n5202b78fc3e55589@mail.gmail.com> (Kip Macy's message of "Sun\, 21 Oct 2007 20\:56\:35 -0700") References: <b1fa29170710212056x5649a858n5202b78fc3e55589@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kip Macy" <kip.macy@gmail.com> writes: > Let me say in advance that this is not an invitation to discuss the > technical merits of xen. This is purely a request to discuss how one > would structure the tree were one to import it into CVS. > > Hypothetically speaking, if one were to import Xen support into CVS > what would be the best way to go about it? > > There are a number of choices when doing it as a sub-arch: > - A separate directory for i386 and amd64 > - sys/xen-i386 > - sys/xen-amd64 > - A shared directory as most of the bits will be shared: > - sys/xen - common bits > - sys/xen/i386 - i386 specific bits > - sys/xen/amd64 - amd64 specific bits > > It could, in principle, also be done as a build option. I'm not sure > how well it would mesh with the existing build tools as there are a > number of files that I would not want to compile in (e.g. code that > talked directly to the BIOS) that is normally built by default. In > that case I would structure it: > > - sys/i386/xen - xen specific bits for i386 > - sys/amd64/xen - xen specific bits for amd64 I'd say a kernel option would be the best choice; code that isn't relevant for Xen but is otherwise compiled by default can be bracketed with #ifndef XEN. > There is also a question of where the drivers should be put. I propose > that they would be put under sys/dev/xen, so you would have e.g. > sys/dev/xen/xennet, sys/dev/xen/xenblk etc. Sounds reasonable. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86lk9ve5bx.fsf>