From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Hal Rosenstock
<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core] redhat/spec: can't build ibumad on 32-bit arm
Date: Tue, 10 Jan 2017 10:54:14 -0700 [thread overview]
Message-ID: <20170110175414.GA11593@obsidianresearch.com> (raw)
In-Reply-To: <1484069764.2149.18.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, Jan 10, 2017 at 12:36:04PM -0500, Doug Ledford wrote:
> file that needs the memory barriers defined in the headers, and when
> you include the header, the compile error returns. ??The proper fix is
> just to get 32bit arm defines in place.
It is a little worse than that, 32 bit ARM is not DMA coherent at all
so it simply cannot work. The fix is to not compile providers that
require DMA coherence on arches that cannot provide it.
Bit tricky, but almost done..
Jason
--
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
prev parent reply other threads:[~2017-01-10 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 21:39 [PATCH rdma-core] redhat/spec: can't build ibumad on 32-bit arm Jarod Wilson
[not found] ` <20170109213944.31970-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-09 22:31 ` Jason Gunthorpe
[not found] ` <20170109223108.GA10850-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-10 3:27 ` Jarod Wilson
[not found] ` <0e01bfc8-333d-99dd-f7d1-024422923021-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-10 16:10 ` Jason Gunthorpe
[not found] ` <20170110161031.GB15493-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-12 12:32 ` Amrani, Ram
[not found] ` <SN1PR07MB220756D06EA23CE46DEC11A2F8790-mikhvbZlbf8TSoR2DauN2+FPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-01-12 13:06 ` Leon Romanovsky
[not found] ` <20170112130640.GG20392-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-12 13:15 ` Amrani, Ram
[not found] ` <SN1PR07MB2207AAD33488239E59339881F8790-mikhvbZlbf8TSoR2DauN2+FPX92sqiQdvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-01-12 17:14 ` Jason Gunthorpe
2017-01-10 16:30 ` Hal Rosenstock
[not found] ` <a1b3f6cc-2de0-8a19-18dd-182f2cb7d3e1-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-01-10 17:36 ` Doug Ledford
[not found] ` <1484069764.2149.18.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-10 17:54 ` Jason Gunthorpe [this message]
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=20170110175414.GA11593@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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