[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140328214703.GV7528@n2100.arm.linux.org.uk>
Date: Fri, 28 Mar 2014 21:47:04 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Alex Elder <elder@...aro.org>
Cc: linus.walleij@...aro.org, viresh.linux@...il.com,
shiraz.hashim@...il.com, catalin.marinas@....com,
spear-devel@...t.st.com, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/7] ARM: SMP: common "pen" secondary release method
On Fri, Mar 28, 2014 at 04:12:53PM -0500, Alex Elder wrote:
> This series proposes creating a single implementation of the "pen
> release" (or spin-table) mechanism for starting secondary CPUs on
> ARM SMP systems. This mechanism is currently implemented at least 5
> times in the kernel, each essentially identical to the other. There
> are other machines that use this method, but slight differences make
> it necessary to incorporate further work in order to accomodate them
> with a single set of functions.
As I've already said, I have strong objections against anything which
"officialises" this holding-pen approach to secondary CPUs and encourages
it's cargo cult programming with respect to it. I've already made my
views abundantly clear on this subject many times, and they haven't
changed. I've indicated some clear technical reasons why it should
not be encouraged.
By moving this crap it into core code, you're giving it a stronger
endorsement that it's a right way to deal with bringing CPUs online.
It isn't. It must not be encouraged.
> This work began with integrating SMP support for a Broadcom SoC.
> The code I started was another copy of the "pen release" code.
... which just goes to show how people cargo-cult program all the
time - and don't really have a clue what the hell they're doing.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists