Date: Wed, 6 Apr 2016 08:40:02 +0200 From: Baptiste Daroussin <bapt@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r297597 - in head/sys: amd64/linux amd64/linux32 i386/linux Message-ID: <20160406064002.GJ49864@ivaldir.etoilebsd.net> In-Reply-To: <2270129.DEqYKEiVDZ@ralph.baldwin.cx> References: <201604052236.u35ManwQ076790@repo.freebsd.org> <2270129.DEqYKEiVDZ@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
--P6YfpwaDcfcOCJkJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 05, 2016 at 06:32:16PM -0700, John Baldwin wrote: > On Tuesday, April 05, 2016 10:36:49 PM Baptiste Daroussin wrote: > > Author: bapt > > Date: Tue Apr 5 22:36:48 2016 > > New Revision: 297597 > > URL: https://svnweb.freebsd.org/changeset/base/297597 > >=20 > > Log: > > Add kern.features flags for linux and linux64 modules > > =20 > > kern.features.linux: 1 meaning linux 32 bits binaries are supported > > kern.features.linux64: 1 meaning linux 64 bits binaries are supported > > =20 > > The goal here is to help 3rd party applications (including ports) to = determine > > if the host do support linux emulation > > =20 > > Reviewed by: dchagin > > MFC after: 1 week > > Relnotes: yes > > Differential Revision: D5830 >=20 > Other parts of the system (e.g. libsysdecode, the various symbols exporte= d by > the modules, etc.) use "linux" to mean supporting Linux binaries of the s= ame > ABI as the host (so x86-64 on amd64 and i386 on i386) and "linux32" to me= an > supporting 32-bit Linux binaries on a 64-bit host. Note that we used to > have linux.ko on Alpha which was a 64-bit ABI, not 32-bit. It is unfortu= nate > that we called linux32.ko linux.ko, but we shouldn't perpetuate that mist= ake > further IMO. For example, I think if we grow Linux/aarch64 ABI support on > FreeBSD/arm64, that should be called 'linux.ko', not 'linux64.ko'. > Similarly, Linux/armv6 on FreeBSD/armv6 would also be 'linux.ko'. >=20 > I would also list the names in the feature description (so Linux/i386, not > Linux 32-bit, since Linux/armv6 is a 32-bit binary, but linux.ko on > FreeBSD/i386 can't run it). >=20 Well I tried to be consistent with the other example we have which is cloud= abi. I considered the x86 case and tried to generalize: linux =3D> my arch (x86) in 32bit linux64 =3D> my arch (x86) in 64bit Let's consider aarch64 which is supposed to also have support for 32bits (o= ne would be happy to run linux armv6 on top of it ,no?) linux =3D> my arm in 32bits linux64 =3D> my arch in 64bits That said, I have no strong feelings about it Bapt --P6YfpwaDcfcOCJkJ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXBK9CAAoJEGOJi9zxtz5arTQQANADUN8mLAMDD/4cgoHyrMK+ e5NAFSbJTaixYkr944YQkVYTWgalCzN3c3J5WdRdWRU+2R3xQAZq8emVPHUSSEN6 mk7eCvjbCCW14ufUEUSx7z+IKeGXBjhYFlI/tRcf2WLtAry31/iTwJ9uvOHcvp/k PRrqmtQPafAj7OdBpz1cay/JnjwlS8q2/V7EHE1H7ty0cgPFUA6M3C2h7oRTGaPA 0vTF/Zwsoa8xUVBdX5MDe75ldBroz6cExB5PXUJAft9Cmhx3u7UnLvdwDIl1EfOc QRPlCm3rhPEsOKTrKFhIPURWtso014U7GDHkUIgq2Inpo3de3Po2ScKWBjMHjG7v No9R98JwGM2AfLPJR9bfsmvI5o8WZCXmlp/iwt7Sjf9sVqz5n6WtW3mivsQQ2qLR WfvAZPRwHhEhsirbUXlfhg6EQ85ORJ7wtIYxKpeUut7XzyAHLN+SH7jvkza81I2Q BFxqYJ9WXB8kjKhzmYndGcXWDLeI6jH0cRMwKAriVAdVuFGeU/tW48ldFcec7uor 9vHbPJDZRUCp4kNgBuLqz1rQM0Jd+1ZJUigmq+OT+BYHzaF8R4MfY0wy+dIrH68j Cc0MyTkMC69WiISF4C4jJI20QiQptjL57SjaYMu7aXu97cWWGScmiu1qu4KFOGg+ TJH4jWdexCYmOkAR3K99 =hksm -----END PGP SIGNATURE----- --P6YfpwaDcfcOCJkJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160406064002.GJ49864>