From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:36051 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753144Ab3DLGjR (ORCPT ); Fri, 12 Apr 2013 02:39:17 -0400 Date: Fri, 12 Apr 2013 08:38:51 +0200 From: Jens Axboe Subject: Re: Make FIO for Android Message-ID: <20130412063851.GH12244@kernel.dk> References: <1C4A98C0-A6F6-4E57-8A97-C4E8D253D819@intel.com> <20130412055808.GE12244@kernel.dk> <20130412061806.GF12244@kernel.dk> <20130412063005.GG12244@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: Aaron Carroll Cc: "Krishnamurthy, Anush" , "fio@vger.kernel.org" On Fri, Apr 12 2013, Aaron Carroll wrote: > On 12 April 2013 16:30, Jens Axboe wrote: > > Great, thanks! Will see if I can't get that asm android happy too. > > Thanks. Does it make sense to use the GCC builtin __get_cpuid() ? > That seems to build fine both native x86 and Android/x86 here. Depends on when that was introduced. You'd be surprised to find the ancient distros that some people build it on... But the cpuid stuff should be basic enough that it isn't a lot of trouble to carry it. At least when we figure out why the Android NDK doesn't like the current restraints :-) -- Jens Axboe