Flexible I/O Tester development
 help / color / mirror / Atom feed
* fio execution issue on Android device with MediaTek
@ 2014-06-19 20:39 David N
  2014-06-19 21:04 ` David Nellans
  0 siblings, 1 reply; 5+ messages in thread
From: David N @ 2014-06-19 20:39 UTC (permalink / raw)
  To: fio

Hi all,

I got fio working fine on a device with Qualcomm Snapdragon but
executing that same compiled binary gave me "sh: ./fio: not
executable: magic 7F45" on a MediaTek (MT6572) device.

I tried to recompile both for ARM and x86 but still the same issue.
The binary is executable (did chmod it), so I'm not sure what is
causing this. I'd very much appreciate any input.

Thanks much!
David

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: fio execution issue on Android device with MediaTek
  2014-06-19 20:39 fio execution issue on Android device with MediaTek David N
@ 2014-06-19 21:04 ` David Nellans
  2014-06-19 21:13   ` David Nellans
  0 siblings, 1 reply; 5+ messages in thread
From: David Nellans @ 2014-06-19 21:04 UTC (permalink / raw)
  To: David N, fio

generally speaking taking a pre-compiled binary from one machine to 
another is a dicey proposition
but in this case you're moving from a krait 400? which runs armv7 to the 
MT6572 which is a cortex A-7
which are the same ISA rev.  are you running the exact same distro 
and/or set of libs on them too?
changes there in glibc, will cause issues. cross compiling for x86 
certainly isn't going to fix your problems!

just for good measure I did just compile and run fio tip on a tegra k1 
running ubuntu 13.04 (3.10.33 kern)
and it seems to be working just fine. have you managed to get anything 
at all to work via this method?
i doubt its an issue specific to fio.

- the real David N

On 06/19/2014 03:39 PM, David N wrote:
> Hi all,
>
> I got fio working fine on a device with Qualcomm Snapdragon but
> executing that same compiled binary gave me "sh: ./fio: not
> executable: magic 7F45" on a MediaTek (MT6572) device.
>
> I tried to recompile both for ARM and x86 but still the same issue.
> The binary is executable (did chmod it), so I'm not sure what is
> causing this. I'd very much appreciate any input.
>
> Thanks much!
> David
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: fio execution issue on Android device with MediaTek
  2014-06-19 21:04 ` David Nellans
@ 2014-06-19 21:13   ` David Nellans
  2014-06-19 21:25     ` David N
  0 siblings, 1 reply; 5+ messages in thread
From: David Nellans @ 2014-06-19 21:13 UTC (permalink / raw)
  To: David N, fio

I may have actually spoken prematurely - if the krait version is running 
v7a and compiles for armeabi-v7a
but the mt6572 is only supports armeabi you could run into ABI issues.  
either way, still very unlikely its a fio issue.

On 06/19/2014 04:04 PM, David Nellans wrote:
> generally speaking taking a pre-compiled binary from one machine to 
> another is a dicey proposition
> but in this case you're moving from a krait 400? which runs armv7 to 
> the MT6572 which is a cortex A-7
> which are the same ISA rev.  are you running the exact same distro 
> and/or set of libs on them too?
> changes there in glibc, will cause issues. cross compiling for x86 
> certainly isn't going to fix your problems!
>
> just for good measure I did just compile and run fio tip on a tegra k1 
> running ubuntu 13.04 (3.10.33 kern)
> and it seems to be working just fine. have you managed to get anything 
> at all to work via this method?
> i doubt its an issue specific to fio.
>
> - the real David N
>
> On 06/19/2014 03:39 PM, David N wrote:
>> Hi all,
>>
>> I got fio working fine on a device with Qualcomm Snapdragon but
>> executing that same compiled binary gave me "sh: ./fio: not
>> executable: magic 7F45" on a MediaTek (MT6572) device.
>>
>> I tried to recompile both for ARM and x86 but still the same issue.
>> The binary is executable (did chmod it), so I'm not sure what is
>> causing this. I'd very much appreciate any input.
>>
>> Thanks much!
>> David
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe fio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: fio execution issue on Android device with MediaTek
  2014-06-19 21:13   ` David Nellans
@ 2014-06-19 21:25     ` David N
  2014-06-19 21:38       ` David Nellans
  0 siblings, 1 reply; 5+ messages in thread
From: David N @ 2014-06-19 21:25 UTC (permalink / raw)
  To: David Nellans; +Cc: fio

Hi David,

Yes, it's mt6572 with armv7 rev 3. I didn't do any changes to fio.
Just pulled the latest version, compiled, and pushed the binary to the
device. I tried the same binary on Samsung S4 with qualcomm, and it
worked fine.

Thanks,
-David Nguyen

On Thu, Jun 19, 2014 at 2:13 PM, David Nellans <david@nellans.org> wrote:
> I may have actually spoken prematurely - if the krait version is running v7a
> and compiles for armeabi-v7a
> but the mt6572 is only supports armeabi you could run into ABI issues.
> either way, still very unlikely its a fio issue.
>
>
> On 06/19/2014 04:04 PM, David Nellans wrote:
>>
>> generally speaking taking a pre-compiled binary from one machine to
>> another is a dicey proposition
>> but in this case you're moving from a krait 400? which runs armv7 to the
>> MT6572 which is a cortex A-7
>> which are the same ISA rev.  are you running the exact same distro and/or
>> set of libs on them too?
>> changes there in glibc, will cause issues. cross compiling for x86
>> certainly isn't going to fix your problems!
>>
>> just for good measure I did just compile and run fio tip on a tegra k1
>> running ubuntu 13.04 (3.10.33 kern)
>> and it seems to be working just fine. have you managed to get anything at
>> all to work via this method?
>> i doubt its an issue specific to fio.
>>
>> - the real David N
>>
>> On 06/19/2014 03:39 PM, David N wrote:
>>>
>>> Hi all,
>>>
>>> I got fio working fine on a device with Qualcomm Snapdragon but
>>> executing that same compiled binary gave me "sh: ./fio: not
>>> executable: magic 7F45" on a MediaTek (MT6572) device.
>>>
>>> I tried to recompile both for ARM and x86 but still the same issue.
>>> The binary is executable (did chmod it), so I'm not sure what is
>>> causing this. I'd very much appreciate any input.
>>>
>>> Thanks much!
>>> David
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe fio" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: fio execution issue on Android device with MediaTek
  2014-06-19 21:25     ` David N
@ 2014-06-19 21:38       ` David Nellans
  0 siblings, 0 replies; 5+ messages in thread
From: David Nellans @ 2014-06-19 21:38 UTC (permalink / raw)
  To: David N; +Cc: fio

what -march are you actually compiling for and under what distro?


On 06/19/2014 04:25 PM, David N wrote:
> Hi David,
>
> Yes, it's mt6572 with armv7 rev 3. I didn't do any changes to fio.
> Just pulled the latest version, compiled, and pushed the binary to the
> device. I tried the same binary on Samsung S4 with qualcomm, and it
> worked fine.
>
> Thanks,
> -David Nguyen
>
> On Thu, Jun 19, 2014 at 2:13 PM, David Nellans <david@nellans.org> wrote:
>> I may have actually spoken prematurely - if the krait version is running v7a
>> and compiles for armeabi-v7a
>> but the mt6572 is only supports armeabi you could run into ABI issues.
>> either way, still very unlikely its a fio issue.
>>
>>
>> On 06/19/2014 04:04 PM, David Nellans wrote:
>>> generally speaking taking a pre-compiled binary from one machine to
>>> another is a dicey proposition
>>> but in this case you're moving from a krait 400? which runs armv7 to the
>>> MT6572 which is a cortex A-7
>>> which are the same ISA rev.  are you running the exact same distro and/or
>>> set of libs on them too?
>>> changes there in glibc, will cause issues. cross compiling for x86
>>> certainly isn't going to fix your problems!
>>>
>>> just for good measure I did just compile and run fio tip on a tegra k1
>>> running ubuntu 13.04 (3.10.33 kern)
>>> and it seems to be working just fine. have you managed to get anything at
>>> all to work via this method?
>>> i doubt its an issue specific to fio.
>>>
>>> - the real David N
>>>
>>> On 06/19/2014 03:39 PM, David N wrote:
>>>> Hi all,
>>>>
>>>> I got fio working fine on a device with Qualcomm Snapdragon but
>>>> executing that same compiled binary gave me "sh: ./fio: not
>>>> executable: magic 7F45" on a MediaTek (MT6572) device.
>>>>
>>>> I tried to recompile both for ARM and x86 but still the same issue.
>>>> The binary is executable (did chmod it), so I'm not sure what is
>>>> causing this. I'd very much appreciate any input.
>>>>
>>>> Thanks much!
>>>> David
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe fio" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-06-19 21:38 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-19 20:39 fio execution issue on Android device with MediaTek David N
2014-06-19 21:04 ` David Nellans
2014-06-19 21:13   ` David Nellans
2014-06-19 21:25     ` David N
2014-06-19 21:38       ` David Nellans

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox