linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <suzuki.poulose@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: marc.zyngier@arm.com, linux-kernel@vger.kernel.org,
	mark.rutland@arm.com, will.deacon@arm.com,
	catalin.marinas@arm.com,
	"Suzuki K. Poulose" <suzuki.poulose@arm.com>
Subject: [PATCH v2 4/6] arm64: Add hook for checking early CPU features
Date: Tue,  1 Dec 2015 15:12:09 +0000	[thread overview]
Message-ID: <1448982731-17182-5-git-send-email-suzuki.poulose@arm.com> (raw)
In-Reply-To: <1448982731-17182-1-git-send-email-suzuki.poulose@arm.com>

Adds a hook for checking whether a secondary CPU has the
features used already by the kernel during early boot, based
on the boot CPU.

Cc: Will Deacon <will.deacon@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>
---
 arch/arm64/kernel/cpufeature.c |   10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
index dde1f56..8dd05283 100644
--- a/arch/arm64/kernel/cpufeature.c
+++ b/arch/arm64/kernel/cpufeature.c
@@ -824,6 +824,14 @@ static u64 __raw_read_system_reg(u32 sys_id)
 }
 
 /*
+ * Check for CPU features that are used in early boot
+ * based on the Boot CPU value.
+ */
+static void check_early_cpu_features(void)
+{
+}
+
+/*
  * Run through the enabled system capabilities and enable() it on this CPU.
  * The capabilities were decided based on the available CPUs at the boot time.
  * Any new CPU should match the system wide status of the capability. If the
@@ -836,6 +844,8 @@ void verify_local_cpu_capabilities(void)
 	int i;
 	const struct arm64_cpu_capabilities *caps;
 
+	check_early_cpu_features();
+
 	/*
 	 * If we haven't computed the system capabilities, there is nothing
 	 * to verify.
-- 
1.7.9.5


  parent reply	other threads:[~2015-12-01 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 15:12 [PATCH v2 0/6] arm64: cpufeature: Add sanity check for ASIDBits Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 1/6] arm64: Introduce kill_cpu_early Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 2/6] arm64: Move kill_cpu_early to smp.c Suzuki K. Poulose
2015-12-01 15:28   ` Mark Rutland
2015-12-01 16:07     ` Suzuki K. Poulose
2015-12-01 16:31       ` Mark Rutland
2015-12-01 17:38         ` Suzuki K. Poulose
2015-12-01 17:52           ` Mark Rutland
2015-12-01 18:10             ` Suzuki K. Poulose
2015-12-01 18:50               ` Mark Rutland
2015-12-03 16:36                 ` Suzuki K. Poulose
2015-12-03 17:08                   ` Mark Rutland
2015-12-01 15:12 ` [PATCH v2 3/6] arm64: Enable CPU capability verification for !CONFIG_HOTPLUG_CPU Suzuki K. Poulose
2015-12-01 15:12 ` Suzuki K. Poulose [this message]
2015-12-01 15:12 ` [PATCH v2 5/6] arm64: Add helper for extracting ASIDBits Suzuki K. Poulose
2015-12-01 15:12 ` [PATCH v2 6/6] arm64: Ensure the secondary CPUs have safe ASIDBits size Suzuki K. Poulose
2015-12-01 15:15 ` [PATCH v2 0/6] arm64: cpufeature: Add sanity check for ASIDBits Suzuki K. Poulose

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=1448982731-17182-5-git-send-email-suzuki.poulose@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.com \
    /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).