linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Brown <davidb@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH RFC] arm: Add argument to init_machine
Date: Wed, 8 Dec 2010 14:07:22 +0000	[thread overview]
Message-ID: <20101208140722.GD9777@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1291768976-7773-1-git-send-email-davidb@codeaurora.org>

On Tue, Dec 07, 2010 at 04:42:56PM -0800, David Brown wrote:
> Some ARM SOCs are used in numerous configurations.  While much of the
> configuration is identical between these configuration, since it is
> contained within the SOC, there will often be slight differences in
> external hardware that is connected.
> 
> To reduce the number of machine_is_...() tests in the machine init
> code, pass an agrument from the machine descriptor through to the init
> function.
> 
> This adds 4-bytes to the kernel for every machine that is compiled in.
> Machines that make use of the pointer will have additional data, which
> will likely be offset by a reduction in runtime tests needed.

I guess most of the increases are within the .init sections, which get
lost because of their alignment(s).

> ---
> I wanted to see what people thought of doing this in general for ARM.
> We can get the same effect for some of our new targets by having short
> individual functions that call another function with a different
> pointer.

As far as the patch itself goes, it looks fine, but I'm not seeing
anything using this new facility in this patch.

I don't like adding things without seeing how they're going to be
used, as sometimes these things never get used.  Maybe you can give
some examples?

  reply	other threads:[~2010-12-08 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  0:42 [PATCH RFC] arm: Add argument to init_machine David Brown
2010-12-08 14:07 ` Russell King - ARM Linux [this message]
2010-12-08 17:24   ` David Brown
2010-12-08 17:27     ` Russell King - ARM Linux
2010-12-08 17:50       ` David Brown

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=20101208140722.GD9777@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=davidb@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.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 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).