From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Goldstein Subject: Kbuild and Kconfig Date: Wed, 2 Sep 2015 12:50:00 -0500 Message-ID: <55E736C8.3050302@cardoe.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0728851016027284531==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============0728851016027284531== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RaqaCpL4vLKEuGl18RJAs1B6Lfn5a5Mkj" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RaqaCpL4vLKEuGl18RJAs1B6Lfn5a5Mkj Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I just wanted to bring this to a top level post since Jonathan Creekmore and myself have talked with a few maintainers in different threads and on IRC about potentially using Kconfig and/or Kbuild for Xen. Basically I would like to get a rough idea on what the Xen community wants the system to look like before starting work on it to both save myself time and save maintainers review cycles. So that being said rough proposal as follows: * target only the xen/ directory tree (i.e. not the toolstack, stubdoms or docs) * split top level config bits to not affect xen/ tree (currently only XSM_ENABLE / FLASK_ENABLE do) * convert xen/ to Kbuild first and merge this in (since Kconfig relies on Kbuild-y bits which can be undone but if we're going to go to Kbuild in the end why undo it and then redo it) * convert existing xen/ config bits into Kconfig and merge that in Jonathan and I, in a former life, converted a project to Kbuild and Kconfig successfully. I have looked at starting with https://github.com/masahir0y/kbuild_skeleton while the tree is fairly old it does separate out the build bits from the Linux specific bits pretty nicely while removing module support which arguably is the most complicated part. Alternatively we could start with Linux 4.2 if that's more desirable. Thanks. --=20 Doug Goldstein --RaqaCpL4vLKEuGl18RJAs1B6Lfn5a5Mkj 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 iQJ8BAEBCgBmBQJV5zbLXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNTM5MEQ2RTNFMTkyNzlCNzVDMzIwOTVB MkJDMDNEQzg3RUQxQkQ0AAoJEKK8A9yH7RvUfmEP/jel1ljudZKVaoY81/Pkw4QL HMzYcUD4/oehfXno2xTZtwNQ660FeE+DgzbgB7wU8NLesk6pv4LRvRUJpwVz3dhJ YJANu+9VoSQTvdjsdPP7eKbZ6nDbtPc1qC2KlE/m8W1cYVO0mc7CuMqyPRwrPa2p +860GyTAx9C1yzIwguXT0NGXlkvihaLHMgunpNpFXDf+0bFvKZj//jNhTZ4qUhFU f4ZKn/SL2ty+lQzJV5/6OfbqmO40RMXznihEZ7l2XiEcY0otozueK+HIn61AeGy2 o7K26DWwTmrKT2WKQrxJlAkkN1FDjYTvqI/PNoAE9Brure7J7kP4cdKvOukPsd07 M45G4//8/930QJUrzs+KYr8SsZrwcqjjYXXgsc1YpwDASHs6dsjxsQGw8pjkjA3O n5oXReLqebGwB+wi1ZT7aK0Kr/SUNZK9kYzFHRMMUzLmMQNtQ7JT6ak9oYHu/Q8J kcEOAWEnvITDtmguIrArzL+FqwyB8LfYrLCgqKUdBDtgSlCAs+nbEk5yUZerTQQs 2cEjqlygdJU5jD4ucHBQy0zrX7uKmkHYZA06ZoScS/M0Py6qj+BlRfEO7nFrx5VI 0I2YpHtT5IMWfcpm4nvDcD7wKjLFRhvjHqPz9YXihbE/IauhnrXPW5k9vuPg6Uri adjOacK+b+kwlQZVE8vw =caUK -----END PGP SIGNATURE----- --RaqaCpL4vLKEuGl18RJAs1B6Lfn5a5Mkj-- --===============0728851016027284531== 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 --===============0728851016027284531==--