From: David Miller <davem@davemloft.net>
To: holt@sgi.com
Cc: chuck.lever@oracle.com, tony.luck@intel.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kernel unaligned accesses on 2.6.29.
Date: Wed, 25 Mar 2009 02:04:14 +0000 [thread overview]
Message-ID: <20090324.190414.59071734.davem@davemloft.net> (raw)
In-Reply-To: <20090325011418.GB8908@sgi.com>
From: Robin Holt <holt@sgi.com>
Date: Tue, 24 Mar 2009 20:14:18 -0500
> You either need to use memcpy, or not define it as an unsigned char.
> Tony, any suggestions?
memcpy() might not work in this scenerio.
GCC can still emit an inline 64-bit memory access if it
deems that the objects involved should be sufficiently
aligned.
It might not be able to in this specific case, but it is
something to be aware of. Don't be convinced of any fix
for this until the assembler is inspected by hand :-)
prev parent reply other threads:[~2009-03-25 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:28 kernel unaligned accesses on 2.6.29 Robin Holt
2009-03-25 1:14 ` Robin Holt
2009-03-25 1:21 ` Robin Holt
2009-03-25 2:04 ` David Miller [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=20090324.190414.59071734.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chuck.lever@oracle.com \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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