From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYvJH-0007XD-Nq for qemu-devel@nongnu.org; Tue, 21 Jun 2011 03:23:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYvJG-00077h-0G for qemu-devel@nongnu.org; Tue, 21 Jun 2011 03:23:43 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:54364) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYvJF-00077d-NM for qemu-devel@nongnu.org; Tue, 21 Jun 2011 03:23:41 -0400 Message-ID: <4E0046F7.9010805@web.de> Date: Tue, 21 Jun 2011 09:23:35 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <9e6a385a5db82c11b78f87b207fa70136f0c2855.1308637593.git.jan.kiszka@web.de> <56EF9EC1-2FA8-4579-BFDF-8E7C2895185E@suse.de> In-Reply-To: <56EF9EC1-2FA8-4579-BFDF-8E7C2895185E@suse.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7372449BBE01FFCEB4AC9E1E" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] [PATCH 1/4] xen: Clean up build system List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Anthony PERARD , xen-devel , qemu-devel@nongnu.org, Stefano Stabellini This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7372449BBE01FFCEB4AC9E1E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-06-21 09:21, Alexander Graf wrote: >=20 > On 21.06.2011, at 08:26, Jan Kiszka wrote: >=20 >> From: Jan Kiszka >> >> Introduce CONFIG_XEN_BACKEND so that this new config solely controls t= he >> target-independent backend build and CONFIG_XEN can focus on per-targe= t >> building. >=20 > What's the incentive here? I very much doubt we'll ever want to support= xen on !x86. In fact, the better solution would probably be to just move= every build component to x86 specific code. I doubt that as well. But keeping the backend centrals prevent building them twice (for i386 and x86_64). Jan --------------enig7372449BBE01FFCEB4AC9E1E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk4ARvoACgkQitSsb3rl5xRd1ACgzZJX7/+9IkYM5IJYuLdns7uQ 460An1LEePjEFWyfrpc/ZhO/XkHFIJdM =LJ5B -----END PGP SIGNATURE----- --------------enig7372449BBE01FFCEB4AC9E1E-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH 1/4] xen: Clean up build system Date: Tue, 21 Jun 2011 09:23:35 +0200 Message-ID: <4E0046F7.9010805@web.de> References: <9e6a385a5db82c11b78f87b207fa70136f0c2855.1308637593.git.jan.kiszka@web.de> <56EF9EC1-2FA8-4579-BFDF-8E7C2895185E@suse.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1050006034==" Return-path: In-Reply-To: <56EF9EC1-2FA8-4579-BFDF-8E7C2895185E@suse.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alexander Graf Cc: Anthony PERARD , xen-devel , qemu-devel@nongnu.org, Stefano Stabellini List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1050006034== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7372449BBE01FFCEB4AC9E1E" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7372449BBE01FFCEB4AC9E1E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-06-21 09:21, Alexander Graf wrote: >=20 > On 21.06.2011, at 08:26, Jan Kiszka wrote: >=20 >> From: Jan Kiszka >> >> Introduce CONFIG_XEN_BACKEND so that this new config solely controls t= he >> target-independent backend build and CONFIG_XEN can focus on per-targe= t >> building. >=20 > What's the incentive here? I very much doubt we'll ever want to support= xen on !x86. In fact, the better solution would probably be to just move= every build component to x86 specific code. I doubt that as well. But keeping the backend centrals prevent building them twice (for i386 and x86_64). Jan --------------enig7372449BBE01FFCEB4AC9E1E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk4ARvoACgkQitSsb3rl5xRd1ACgzZJX7/+9IkYM5IJYuLdns7uQ 460An1LEePjEFWyfrpc/ZhO/XkHFIJdM =LJ5B -----END PGP SIGNATURE----- --------------enig7372449BBE01FFCEB4AC9E1E-- --===============1050006034== 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 --===============1050006034==--