From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Enable MRS emulation early
Date: Wed, 4 Oct 2017 11:14:26 +0100 [thread overview]
Message-ID: <20171004101425.GB23092@leverpostej> (raw)
In-Reply-To: <20171004094805.24009-1-suzuki.poulose@arm.com>
On Wed, Oct 04, 2017 at 10:48:05AM +0100, Suzuki K Poulose wrote:
> Make sure the MRS emulation is enabled early enough, such that the
> early userspace applications (e.g, those run from initrd) could
> use the facility without crashing them.
>
> Fixes: commit 77c97b4ee2129 ("arm64: cpufeature: Expose CPUID registers by emulation")
> Reported-by: Matwey V. Kornilov <matwey.kornilov@gmail.com>
> Cc: James Morse <james.morse@arm.com>
> Cc: Dave Martin <Dave.martin@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: stable at vger.kernel.org
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
This looks sensible, but shouldn't we do the same for other
late_inicalls can affect initrd userspace?
e.g. armv8_deprecated_init, fpsimd_init, sys_reg_genericv8_init?
Thanks,
Mark.
> ---
> arch/arm64/kernel/cpufeature.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index 9f9e0064c8c1..276eecab6cea 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -1294,4 +1294,4 @@ static int __init enable_mrs_emulation(void)
> return 0;
> }
>
> -late_initcall(enable_mrs_emulation);
> +core_initcall(enable_mrs_emulation);
> --
> 2.13.5
>
next prev parent reply other threads:[~2017-10-04 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 9:48 [PATCH] arm64: Enable MRS emulation early Suzuki K Poulose
2017-10-04 10:14 ` Mark Rutland [this message]
2017-10-04 11:10 ` Catalin Marinas
2017-10-04 11:32 ` Dave Martin
2017-10-04 11:36 ` Catalin Marinas
2017-10-04 12:48 ` Dave Martin
2017-10-04 13:24 ` Catalin Marinas
2017-10-04 11:32 ` Mark Rutland
2017-10-04 13:00 ` 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=20171004101425.GB23092@leverpostej \
--to=mark.rutland@arm.com \
--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