Date: Mon, 22 Oct 2007 12:46:52 +0200 From: Max Laier <max@love2party.net> To: freebsd-arch@freebsd.org Cc: Kip Macy <kip.macy@gmail.com> Subject: Re: Should Xen be a sub-arch or a build option? Message-ID: <200710221247.01695.max@love2party.net> In-Reply-To: <b1fa29170710212056x5649a858n5202b78fc3e55589@mail.gmail.com> References: <b1fa29170710212056x5649a858n5202b78fc3e55589@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2660110.uE77fQ4EcL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 22 October 2007, Kip Macy wrote: > 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 This is certainly the most traditional way to do it. The fact that the=20 xen ports will share (a lot of) code with their respective parent doesn't=20 change that - pc98 is the precedent here. As it would also allow us to=20 treat xen as any other architecture without having to spread hacks all=20 over the build tools. I'd like to see us moving towards a separate arch/ directory in the long=20 run, but that belongs - with the new VCS discussion - somewhere else. > 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. The existence of these drivers are also a reason - to me at least - to=20 keep xen as a platform of its own. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2660110.uE77fQ4EcL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHHH+lXyyEoT62BG0RAr2NAJ4ybjENf9PU3X8Iypg93NkRkp0uFgCfVNol 0ZDrcggQ7mH2XGGXbT+J46A= =3s1t -----END PGP SIGNATURE----- --nextPart2660110.uE77fQ4EcL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710221247.01695.max>