From: Pramod Gunjikar <pramod.gunjikar-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Boris Chiu <boris.chiu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Hal Rosenstock
<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Ira Weiny <iweiny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] libibmad: To fix big endian problem for both 32-bit & 64-bit SPARC
Date: Thu, 18 Apr 2013 15:58:54 +0530 [thread overview]
Message-ID: <516FCAE6.3010403@oracle.com> (raw)
In-Reply-To: <5141FAFD.5070109-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Hello Hal / Or,
Sorry for the delay in getting back on this.
Solaris specific endian fixes were applied to OFED 1.3 in order to
fix infiniband-diag failures observed
on SPARC. Changes to OFED 1.5.3 now make these fixes redundant
consequently the patch request
is withdrawn.
Let us know if you have any queries.
Thanks
Pramod
> Hi Hal and Or,
>
> We are checking on this and will get back.
>
> Thanks,
> Boris
>
> On 03/13/13 05:58, Or Gerlitz wrote:
>> On 13/03/2013 14:48, Hal Rosenstock wrote:
>>> On 3/12/2013 3:36 PM, Boris Chiu wrote:
>>>> >--- a/src/dump.c
>>>> >+++ b/src/dump.c
>>>> >@@ -46,12 +46,24 @@
>>>> >
>>>> >void mad_dump_int(char *buf, int bufsz, void *val, int valsz)
>>>> >{
>>>> >+ /*
>>>> >+ * the val pointer passed to the dump routines are always 32 bit
>>>> >+ * integers for valsz <= 4 and 64 bit integer for the rest.
>>>> It is
>>>> >never
>>>> >+ * uint8_t or uint16_t. This is because mad_decode_field always
>>>> >returns
>>>> >+ * the values as 32 bit integer even if they are 8 bit or 16 bit
>>>> >fields.
>>>> >+ */
>>>> > switch (valsz) {
>>>> > case 1:
>>>> >- snprintf(buf, bufsz, "%d", *(uint32_t *) val & 0xff);
>>>> >+#if defined(_BIG_ENDIAN)
>>>> >+ val = ((uint8_t *)val) + 3;
>>>> >+#endif /* _BIG_ENDIAN */
>>> I don't understand what's different about SPARC and PPC in terms of
>>> this. These routines all work without this on PPC64 and PPC32.
>>
>> Yep, agree, assuming the code works on other BE archs, we 1st and
>> most need to understand the problem before going to solutions.
>>
>> Or.
>>
>>
>>
>>>
>>> At a minimum, should this be ifdef'd on something like both __sun and
>>> __SVR4 rather than _BIG_ENDIAN ?
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-04-18 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 19:36 [PATCH] libibmad: To fix big endian problem for both 32-bit & 64-bit SPARC Boris Chiu
[not found] ` <513F83BD.3050302-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-03-13 12:48 ` Hal Rosenstock
[not found] ` <5140759D.1030500-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-03-13 12:58 ` Or Gerlitz
[not found] ` <514077DB.9000703-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-03-14 16:29 ` Boris Chiu
[not found] ` <5141FAFD.5070109-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-04-18 10:28 ` Pramod Gunjikar [this message]
[not found] ` <516FCAE6.3010403-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-04-18 17:52 ` Weiny, Ira
2013-03-13 16:28 ` Weiny, Ira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516FCAE6.3010403@oracle.com \
--to=pramod.gunjikar-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=boris.chiu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=iweiny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox