linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] ARM: BCM63xx: Add SMP support for BCM63138
Date: Sat, 18 Apr 2015 00:22:01 +0100	[thread overview]
Message-ID: <20150417232201.GD12732@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1429310032-19402-8-git-send-email-f.fainelli@gmail.com>

On Fri, Apr 17, 2015 at 03:33:52PM -0700, Florian Fainelli wrote:
> +
> +extern unsigned int VFP_arch;
...
> +	/* The BCM63138 SoC has two Cortex-A9 CPUs, CPU0 features a complete
> +	 * and fully functional VFP unit that can be used, but CPU1 does not.
> +	 * Since we will not be able to trap kernel-mode NEON to force
> +	 * migration to CPU0, just do not advertise VFP support at all.
> +	 *
> +	 * This will make vfp_init bail out and do not attempt to use VFP at
> +	 * all, for kernel-mode NEON, we do not want to introduce any
> +	 * conditionals in hot-paths, so we just restrict the system to UP.
> +	 */
> +#ifdef CONFIG_VFP
> +	if (ncores > 1) {
> +		pr_warn("SMP: secondary CPUs lack VFP unit, disabling VFP\n");
> +		VFP_arch = 1;

What makes you think that doing this hack would be somehow acceptable?

Please, do the job properly.  Add a function hook into the VFP code
called "vfp_disable()" so that it's obvious that you want to disable
it - and, because that code will be localised to VFP, it then becomes
acceptable to set VFP_arch=1.  Don't rely on current VFP behaviour
through setting VFP_arch directly in from platform code - that's
nothing more than a hack and a disgusting layering violation.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2015-04-17 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 22:33 [PATCH 0/7] ARM: BCM63xx: SMP support Florian Fainelli
2015-04-17 22:33 ` [PATCH 1/7] Documentation: DT: Add Broadcom BCM63138 PMB binding Florian Fainelli
2015-04-18 19:41   ` Florian Fainelli
2015-04-17 22:33 ` [PATCH 2/7] ARM: dts: BCM63xx: Add PMB busses nodes Florian Fainelli
2015-04-17 22:33 ` [PATCH 3/7] Documentation: DT: Document SMP DT nodes and properties for BCM63138 Florian Fainelli
2015-04-17 22:33 ` [PATCH 4/7] ARM: dts: BCM63xx: Add SMP nodes and required properties Florian Fainelli
2015-04-17 22:33 ` [PATCH 5/7] ARM: BCM63xx: Add Broadcom BCM63xx PMB controller helpers Florian Fainelli
2015-04-17 22:33 ` [PATCH 6/7] ARM: BCM63xx: Add secondary CPU PMB initialization sequence Florian Fainelli
2015-04-17 22:33 ` [PATCH 7/7] ARM: BCM63xx: Add SMP support for BCM63138 Florian Fainelli
2015-04-17 23:22   ` Russell King - ARM Linux [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=20150417232201.GD12732@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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).