On Fri, Jun 28, 2019 at 11:26:34AM +0200, Alexander Potapenko wrote:
> Am I understanding right this is already covered by Kees having sent
> his patch to -mm tree and I don't need to explicitly include it into
> my series?
Correct; Andrew added it to -mm already.
--
Kees Cook
On Thu, Jun 27, 2019 at 6:25 PM Catalin Marinas wrote:
>
> On Thu, Jun 27, 2019 at 08:58:03AM -0700, Kees Cook wrote:
> > On Thu, Jun 27, 2019 at 09:02:08AM +0100, Catalin Marinas wrote:
> > > On Wed, Jun 26, 2019 at 01:51:15PM -0700, Kees Cook wrote:
> > > > This moves arm64 jump_label_init()
On Thu, Jun 27, 2019 at 08:58:03AM -0700, Kees Cook wrote:
> On Thu, Jun 27, 2019 at 09:02:08AM +0100, Catalin Marinas wrote:
> > On Wed, Jun 26, 2019 at 01:51:15PM -0700, Kees Cook wrote:
> > > This moves arm64 jump_label_init() from smp_prepare_boot_cpu() to
> > > setup_arch(), as done already
On Thu, Jun 27, 2019 at 09:02:08AM +0100, Catalin Marinas wrote:
> On Wed, Jun 26, 2019 at 01:51:15PM -0700, Kees Cook wrote:
> > This moves arm64 jump_label_init() from smp_prepare_boot_cpu() to
> > setup_arch(), as done already on x86, in preparation from early param
> > usage in the
Hi Kees,
On Wed, Jun 26, 2019 at 01:51:15PM -0700, Kees Cook wrote:
> This moves arm64 jump_label_init() from smp_prepare_boot_cpu() to
> setup_arch(), as done already on x86, in preparation from early param
> usage in the init_on_alloc/free() series:
>
On Wed, 26 Jun 2019 at 22:51, Kees Cook wrote:
>
> While jump_label_init() was moved earlier in the boot process in commit
> efd9e03facd0 ("arm64: Use static keys for CPU features"), it wasn't
> early enough for early params to use it. The old state of things was as
> described here...
>
>
While jump_label_init() was moved earlier in the boot process in commit
efd9e03facd0 ("arm64: Use static keys for CPU features"), it wasn't
early enough for early params to use it. The old state of things was as
described here...
init/main.c calls out to arch-specific things before general jump
7 matches
Mail list logo