From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Roel Kluin <roel.kluin@gmail.com>,
"linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Richard Purdie <rpurdie@rpsys.net>,
Anton Blanchard <anton@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH]: powerpc: Fix build breakage due to incorrect location of autoconf.h
Date: Thu, 14 Jan 2010 19:57:11 +1100 [thread overview]
Message-ID: <1263459431.724.352.camel@pasglop> (raw)
In-Reply-To: <OF20873087.ECC43BEB-ONC12576AB.0029EA9A-C12576AB.002AC5CA@transmode.se>
> Seen it now as it is in Linus tree:
>
> 1) IMHO it would have been nicer to use #ifdef __KERNEL__
> instead of CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
> as then arches that don't define CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS
> at all will never use the new optimization or was that what you intended?
No, that was on purpose. If an arch doesn't have efficient unaligned
accesses, then they should not use the optimization since it will result
in a lot of unaligned accesses :-) In which case they are better off
falling back to the old byte-by-byte method.
The advantage also of doing it this way is that x86 will benefit from
the optimisation at boot time since it does include autoconf.h in its
boot wrapper (and deals with unaligned accesses just fine at any time)
though something tells me that it won't make much of a difference in
performances on any recent x86 (it might on some of the newer low power
embedded ones, I don't know for sure).
> 2) You really should add an comment in the Makefile about not using
> autoconf.h/-D__KERNEL__
That's true :-)
Cheers,
Ben.
next prev parent reply other threads:[~2010-01-14 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 2:21 [PATCH]: powerpc: Fix build breakage due to incorrect location of autoconf.h Anton Blanchard
2010-01-12 3:01 ` Stephen Rothwell
2010-01-12 11:59 ` Joakim Tjernlund
2010-01-13 18:54 ` Kumar Gala
2010-01-13 20:02 ` Benjamin Herrenschmidt
2010-01-14 7:47 ` Joakim Tjernlund
2010-01-14 8:57 ` Benjamin Herrenschmidt [this message]
2010-01-14 9:12 ` Joakim Tjernlund
2010-01-14 9:43 ` Benjamin Herrenschmidt
2010-01-14 10:22 ` Joakim Tjernlund
2010-01-14 13:27 ` Joakim Tjernlund
2010-01-14 19:59 ` Benjamin Herrenschmidt
2010-01-25 8:19 ` Joakim Tjernlund
2010-01-27 12:16 ` Joakim Tjernlund
2010-01-28 1:05 ` Andrew Morton
2010-01-28 8:52 ` Joakim Tjernlund
2010-01-29 23:49 ` Andrew Morton
2010-01-30 10:47 ` Joakim Tjernlund
2010-01-12 7:11 ` Joakim Tjernlund
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=1263459431.724.352.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.org \
--cc=roel.kluin@gmail.com \
--cc=rpurdie@rpsys.net \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).