All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS and bcm2835_defconfig
Date: Wed, 12 Mar 2014 09:44:04 -0600	[thread overview]
Message-ID: <532080C4.2000801@wwwdotorg.org> (raw)
In-Reply-To: <20140312110315.GG21483@n2100.arm.linux.org.uk>

On 03/12/2014 05:03 AM, Russell King - ARM Linux wrote:
> On Tue, Mar 11, 2014 at 10:35:24PM -0600, Stephen Warren wrote:
>> Hmm. I thought that ARMv6 didn't have efficient unaligned accesses, but
>> I suppose it must; ARM selects HAVE_EFFICIENT_UNALIGNED_ACCESS for
>> v6/v6k/v7. BUILTIN_BSWAP seems innocuous. Can you verify which of those
>> two options actually causes problems for you?
> 
> What do you think is different between v6 and v7 for unaligned accesses?

I don't know the details of unaligned accesses; I'm just remembering
(probably incorrectly and/or misinterpreting) some discussion in U-Boot
about ARMv7 being able to do unaligned accesses OK, yet earlier
generations not being able to (although I don't recall which), and hence
the toolchain options are set up to disallow them, and the ARMv7(?)
config bit that enables them is left disabled, so such accesses cause an
exception, so it's easy to catch the problems that must happen on older
HW even when running on newer HW, even though such access could be
allows on ARMv7.

  reply	other threads:[~2014-03-12 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.10.1403101717050.31525@vincent-weaver-1.um.maine.edu>
2014-03-12  4:35 ` CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS and bcm2835_defconfig Stephen Warren
2014-03-12 11:03   ` Russell King - ARM Linux
2014-03-12 15:44     ` Stephen Warren [this message]
2014-03-12 16:05       ` Russell King - ARM Linux
2014-03-12 16:29       ` Måns Rullgård
2014-03-12 11:33   ` Will Deacon
2014-03-12 11:41     ` Vince Weaver
2014-03-12 19:20       ` Vince Weaver
2014-03-17 21:16         ` Vince Weaver

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=532080C4.2000801@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.