Hi, OK, the issue was related to the alignment issue between the thread_options structure and its "packed" version : The lexxx_to_cpu macros are incorrectly casting the pointers and that causes an bus error. I have fixed the issue by avoid casting the pointers and calling directly the "swap" method. I have also included a fixed on the thread_options structure regarding the ddir_seq_add variable : Its length was incorrect. Attached, you will find a patch that's fixed both. The 32 bit version is still not working on json but since the 64 bit version is working fine, I will not probably work on it. Seb -----Original Message----- From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Sébastien Bouchex Bellomié Sent: vendredi 7 mars 2014 08:51 To: Jens Axboe; fio@xxxxxxxxxxxxxxx Subject: RE: json output issue on solaris sparc Hi, I'm using a 32 bit binary. The 64 bit binary is just crashing at startup (bus error) Seb -----Original Message----- From: Jens Axboe [mailto:axboe@xxxxxxxxx] Sent: jeudi 6 mars 2014 22:47 To: Sébastien Bouchex Bellomié; fio@xxxxxxxxxxxxxxx Subject: Re: json output issue on solaris sparc On 03/04/2014 03:19 AM, Sébastien Bouchex Bellomié wrote: > Hello, > > I'm trying fio on solaris sparc and I'm having an strange issue : io_bytes, bw, iops, runtime values are 0 when json output is enabled but contains valid values when using text (or terse) output format. > I have tested on solaris x64 and everything is fine. That's pretty weird... I lost my last SPARC box about 4 years ago, so I have nothing to test on. I wonder if it's an alignment thing. Is fio a 32-bit or 64-bit application? -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
Fixed-Solaric-sparc-alignement-issue.patch
Description: Fixed-Solaric-sparc-alignement-issue.patch
