summaryrefslogtreecommitdiff
path: root/.gitignore
AgeCommit message (Expand)AuthorFilesLines
2006-07-07Update .gitignoreTobias Klauser1-1/+2
2006-03-13Initial importTobias Klauser1-0/+1
td colspan='2'/>context:space:mode:
authorshamir rabinovitch <shamir.rabinovitch@oracle.com>2016-05-18 06:18:10 -0400
committerDoug Ledford <dledford@redhat.com>2016-05-18 10:25:56 -0400
commit04ef0f1a0169a14b8e653af1178524ab4390133f (patch)
treea608e8ec300977e0fdb43871020380d44a4ac54b /Documentation/media/uapi
parent0651ec932afffce6547efb3e0352e5d229273962 (diff)
IB/mlx4: Fix unaligned access in send_reply_to_slave
The problem is that the function 'send_reply_to_slave' gets the 'req_sa_mad' as a pointer whose address is only aliged to 4 bytes but is 8 bytes in size. This can result in unaligned access faults on certain architectures. Sowmini Varadhan pointed to this reply from Dave Miller that say that memcpy should not be used to solve alignment issues: https://lkml.org/lkml/2015/10/21/352 Optimization of memcpy to 'ldx' instruction can only happen if the compiler knows that the size of the data we are copying is 8 bytes and it assumes it is aligned to 8 bytes. If the compiler know the type is not aligned to 8 it must not optimize the 8 byte copy. Defining the data type as aligned to 4 forces the compiler to treat all accesses as though they aren't aligned and avoids the 'ldx' optimization. Full credit for the idea goes to Jason Gunthorpe <jgunthorpe@obsidianresearch.com>. Signed-off-by: Shamir Rabinovitch <shamir.rabinovitch@oracle.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'Documentation/media/uapi')