From: Sean Dague Subject: Re: [PATCH] build in SATA drivers to the -xen kernel for x86_64 Date: Wed, 29 Mar 2006 14:28:03 -0500 Message-ID: <20060329192803.GA19886@dargo.dague.pvt> References: <20060329180735.GA14512@dargo.dague.pvt> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0410629648==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0410629648== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 29, 2006 at 07:19:18PM +0100, Keir Fraser wrote: >=20 > On 29 Mar 2006, at 19:07, Sean Dague wrote: >=20 > >This patch adds in the SATA drivers that are supported in the -xen0=20 > >kernel. > >Because the default behavior of xen is to reboot on a dom0 crash (i.e.= =20 > >not > >finding root filesystem), and the xen0 kernel supported SATA directly,= =20 > >a > >number of people (including myself) got caught by the switch over. > > > >Long term, we probably want to modularize more of the kernel, and make > >initrd building more of the default, however this should ease people's > >transition from the -xen0 =3D> -xen kernel for testing on x86_64. >=20 > If this is done at all, it should be done for i386 as well. I think=20 > it's debatable really -- -xen is supposed to be a modular kernel build.= =20 > If people want stuff built in they should modify the config or use=20 > -xen0. Well, SATA is significantly more relevant for x86_64, as a very large percentage of x86_64 systems are SATA based. I doubt that even 1/2 of the IDE controllers that are compiled in by default for the x86_64 kernel have ever existed in an x86_64 system. If we're shooting for truely modular, we should start removing the IDE drivers from the -xen kernel. I would agree that changes here are debateable, however given that xen default behavior is to reboot on dom0 fail (i.e. no screen log unless on serial), a large number of users have been tripped up by this process on the -xen kernels, and will find it hard to debug. The approach of making the -xen0 storage drivers also on in the -xen kernel just makes it a bit more predicable. (i.e. -xen =3D=3D -xen0 + lots of other device support). Whil= e it isn't that today, I think it would make more sense if it was that way. But then again, that's just my $0.02. :) An alternate (or even in addition to any changes to the -xen kernel) would be to default xen behavior to "noreboot", which would make it a lot clearer to users *why* their system doesn't come up with Xen on the first try. -Sean --=20 Sean Dague IBM Linux Technology Center email: japh@us.ibm.com Open Hypervisor Team alt: sldague@us.ibm.com --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEKt/DSamXem9TdyYRArXMAJ0bIuuwQKaP8pxRK+QW3c0vlfnpeACcC7r1 jh27x8y9yXLEhWMm/Sh7rBw= =c7e+ -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- --===============0410629648== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0410629648==--