From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933044AbbJALhA (ORCPT ); Thu, 1 Oct 2015 07:37:00 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34197 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932872AbbJALg4 (ORCPT ); Thu, 1 Oct 2015 07:36:56 -0400 Date: Thu, 1 Oct 2015 12:36:42 +0100 From: Mark Brown To: Catalin Marinas Cc: arnd@arndb.de, yury.norov@gmail.com, agraf@suse.de, linux-kernel@vger.kernel.org, klimov.linux@gmail.com, Yury Norov , bamvor.zhangjian@huawei.com, apinski@cavium.com, philipp.tomsich@theobroma-systems.com, linux-arm-kernel@lists.infradead.org, christoph.muellner@theobroma-systems.com Message-ID: <20151001113642.GI12635@sirena.org.uk> References: <1443564860-31208-1-git-send-email-ynorov@caviumnetworks.com> <20150930101918.GA9753@e104818-lin.cambridge.arm.com> <20150930164103.GC15635@sirena.org.uk> <20151001111931.GD6963@e104818-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cf0hFtnykp6aONGL" Content-Disposition: inline In-Reply-To: <20151001111931.GD6963@e104818-lin.cambridge.arm.com> X-Cookie: Walk softly and carry a megawatt laser. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 2a01:348:6:8808:7e7a:91ff:fede:4a45 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v5 00/23] ILP32 for ARM64 X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --cf0hFtnykp6aONGL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Oct 01, 2015 at 12:19:31PM +0100, Catalin Marinas wrote: > On Wed, Sep 30, 2015 at 05:41:03PM +0100, Mark Brown wrote: > > Indeed. On that subject there was some discussion at Linaro Connect > > last week about work (being done outside Linaro, not sure how public it > > is at this point) to pull together the current state of the art into a > > Docker container image which people can use for benchmarking and as a > > reference for how to pull things together. That should help with the > > analysis, it'll at least make it easier for other people to reproduce > > any benchmarking results. > That's fine and I would welcome it. However, I'm definitely against > using non-agreed ABI and further spreading such toolchains (or kernel You might want to speak to some of your colleagues about that... in any case I'll reply off list later today with information on the third party working on this so you can get in touch, like I say I'm not sure how public that work is at this point. > patches; Linaro's tracking kernel has kept these patches for a long > time, even though the ABI has been NAK'ed). I know, I'm not thrilled about that either. :/ --cf0hFtnykp6aONGL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWDRrKAAoJECTWi3JdVIfQ8nEH/iLDl4yIDRTx6UB3rSw0Z4WL 8uuk+0QXuv2507LnMLtLbDLAD8y4pqtybNrvwO6DwaLN+Hvd3VfaK3KJ5coASyPw F7JbItJ6kSlI6DquyYhQWD+j58V4oQA6L60NoyzzReawY7zjKUPs8gHlbAVXAgfg wFWvdh8wZ9ZUU3mvGWhOtZy7fi0Fj1vwrQK1F45Qo+RlUn2eUBPJBrBfMn0Z69El 5VYSocJBPIl1itswxI30zHwlfjZErAbpvz7V/bMbIJxUfQkiINxC0rl3mm8yDQ/Z O8GWbAy5IggIwIrOroO9XZUqKmS3oSibRpNmcgXvXjYe1uz+a+3ewHSReOuIREM= =i5Fa -----END PGP SIGNATURE----- --cf0hFtnykp6aONGL--