From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Enable MRS emulation early
Date: Wed, 4 Oct 2017 13:48:19 +0100 [thread overview]
Message-ID: <20171004124819.GU3611@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20171004113628.t4gv7srwpvbwwbsl@armageddon.cambridge.arm.com>
On Wed, Oct 04, 2017 at 12:36:29PM +0100, Catalin Marinas wrote:
> On Wed, Oct 04, 2017 at 12:32:07PM +0100, Dave P Martin wrote:
[...]
> > I don't think the hwcaps shouldn't change after entry to userspace,
> > so it really doesn't matter whether HWCAP_CPUID is set before or
> > after registration: for userspace it should all already have happened.
>
> Good point, I forgot about this.
>
> > It looks to me like all initcalls are called in the same kernel thread
> > that execs the initramfs init process, before the exec.
> >
> > So I still don't see how a built-in late initcall can not have been
> > called before entry to userspace.
> >
> > The patch seems to demonstrate that I'm wrong though.
> > What am I missing?
>
> I also wondered about this. I think is the kernel invoking modprobe
> before the actual init/linuxrc in an initrd.
Ah, right. Could that be a bug, do you think?
I wonder whether it's even well-defined how early that can happen.
i.e., which initcall level is guaranteed early enough to prevent this?
Cheers
---Dave
next prev parent reply other threads:[~2017-10-04 12:48 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
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 [this message]
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=20171004124819.GU3611@e103592.cambridge.arm.com \
--to=dave.martin@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