From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Goldstein Subject: Re: Kbuild and Kconfig Date: Thu, 3 Sep 2015 09:13:04 -0500 Message-ID: <55E85570.8010308@cardoe.com> References: <55E736C8.3050302@cardoe.com> <20150903095620.GA96995@deinos.phlegethon.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0141921464742868113==" Return-path: In-Reply-To: <20150903095620.GA96995@deinos.phlegethon.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0141921464742868113== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7EikEO1Nu2oU7OEBkDQoi3dhFjv4pI9ag" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --7EikEO1Nu2oU7OEBkDQoi3dhFjv4pI9ag Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/3/15 4:56 AM, Tim Deegan wrote: > Hi, >=20 > At 12:50 -0500 on 02 Sep (1441198200), Doug Goldstein wrote: >> I just wanted to bring this to a top level post since Jonathan Creekmo= re >> and myself have talked with a few maintainers in different threads and= >> on IRC about potentially using Kconfig and/or Kbuild for Xen. >=20 > If we're going to need a configure step before building the > hypervisor, maybe we should consider using the autoconf runes instead. >=20 > I'm one of the people who objected to requiring ./configure before > building the hypervisor, but I think it would be better than having > _two_ config systems which are not synced with each other, esp. if > we'll want to enable/disable features with matching tools-side code. >=20 > If we do go this way, I think we'd need a ./configure --hypervisor-only= , > or similar, that _only_ makes the various CONFIG_ flags, and doesn't > do the tedious library & compiler checks that are needed for the > user-space code. >=20 > Cheers, >=20 > Tim. >=20 I'd only be concerned about the fact that different config switches would do different things and you would end up with a lot of configure switches. e.g. ./configure --with-kexec --without-xenlinux --with-xsm Currently there is a top level XSM_ENABLE and FLASK_ENABLE and they do different things in the tools/ and the xen/ directories. For the tools directory all it does is disable the Flask policy being built (e.g. XSM_ENABLE=3Dn does that) while XSM bits in the tools appear to always be= built. Then for the xen/ directory XSM_ENABLE=3Dn will actually turn off XSM support and Flask support while FLASK_ENABLE=3Dn will keep XSM on and= just build the dummy XSM module. You may also have cases where you want to build functionality into the tools but not into the hypervisor to ensure that the hypervisor returns an error and the tools gracefully handle that case which having a top level configure script would make more difficult. --=20 Doug Goldstein --7EikEO1Nu2oU7OEBkDQoi3dhFjv4pI9ag Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0 iQJ8BAEBCgBmBQJV6FVxXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNTM5MEQ2RTNFMTkyNzlCNzVDMzIwOTVB MkJDMDNEQzg3RUQxQkQ0AAoJEKK8A9yH7RvUHjIP/A7Y/nYEfuwJo+zu40x3UYaO uUWYJqsyUwD8FxUuk7GzmB9ZiuIIDWSWba7U03l/dPkyPY/k0BMFj9lWoCZ/hZFb i07kUcaiyKKMbkQd7Zrf+jIw3upZueKkeNbrskCsRDxALlDujij8eLO8Lj4qSUgC yzW6fuPHmhH+rI6lKlwwcs71ByxQCydNlbae+IzDpiN+pyPL6PZIviUF3eca2Hcd RQb06quNJyf3g8mm9lOHHHWkK0JmAGokWoKXRWebn1hJymU+bRr1C6+1RPEeg2qh kVLzT8iKbEGXh/iS2juGAkKf8CjDEpIJ85YZgwBqh9XiRYw/c0KQu0S2USK75FHx O9vxJTpbcXRT2KhtSCA81LLeO9B4M264KHyJ7NQcGPE28FyLw9cYpDC/AIk1v2Hf SlSdkf2dpAcZytFklbooe6uoLoVL3gXsLmvwfCpjdrAB1MfSv+VvLQ11oSPUjwg8 bwHRqL0N8rtqcnkYM2p3ePBXIGvy0U6UD30wxNanc6L33vH36//XC+kqnL70mCNP mN7//KA6VaGm7il2QNgIzZLuRjaZ5ZCT6Hd0vS8DfHs8U/ZsZ6pIUT6jaVL2JpY9 OjfAlB+bN0iFRFqV++kSysVnfo3HV9n1ciF0//5emJ57MiDXH5wXpfYGIZyQXIPf RzmNCL2tmGAak1JYV7sL =tYfm -----END PGP SIGNATURE----- --7EikEO1Nu2oU7OEBkDQoi3dhFjv4pI9ag-- --===============0141921464742868113== 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.xen.org http://lists.xen.org/xen-devel --===============0141921464742868113==--