From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 08FD63D65 for ; Thu, 2 Jun 2022 19:43:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8D324C34115 for ; Thu, 2 Jun 2022 19:43:04 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="a1Esxugg" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1654198982; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=83SdYmk3U61Aj+CbfcRuFsqRAJiVBcI1MBf6jt14hV4=; b=a1EsxuggogeBBcOkOPsSyXOkxEpbqRYHoK1osBYXagFMgswEII3gfkU16CQ7gsPuSC0Sck WW0wwaKta8m3dEfXr/sYmJB74PZEuQLjrkVAebQRhoyu/gXrEgDfBL82lmZ2kRHdHV0oqh X5Y6ObzLALVlsoxxSqqXIoB2e5hmQ50= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id fc73121f (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for ; Thu, 2 Jun 2022 19:43:01 +0000 (UTC) Received: by mail-yb1-f180.google.com with SMTP id t31so10112268ybi.2 for ; Thu, 02 Jun 2022 12:43:01 -0700 (PDT) X-Gm-Message-State: AOAM532ZPIQt4FwuAeHuO26cEFCLo60dNiV0SMrb31BRxay1BH4tc7X6 yLvxt+7Sr1bhJ3T6YZKpExGA9fsQUFA4PB8Gv4g= X-Google-Smtp-Source: ABdhPJw5Cq823Cb32SVFmeD53s1eU3Rhxhl1GctOd4kRnWxPpJtExToAx55KKweaEe/OxLwDh4VDKrpwbHW+BMCC/hY= X-Received: by 2002:a25:83c2:0:b0:65c:bc75:800b with SMTP id v2-20020a2583c2000000b0065cbc75800bmr7224464ybm.373.1654198979830; Thu, 02 Jun 2022 12:42:59 -0700 (PDT) Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20220602022109.780348-1-swboyd@chromium.org> <165419885870.2681883.10934677413962491141.b4-ty@arm.com> In-Reply-To: <165419885870.2681883.10934677413962491141.b4-ty@arm.com> From: "Jason A. Donenfeld" Date: Thu, 2 Jun 2022 21:42:49 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] arm64: Initialize jump labels before setup_machine_fdt() To: Catalin Marinas Cc: Stephen Boyd , Will Deacon , Dominik Brodowski , Ard Biesheuvel , linux-arm-kernel , LKML , Douglas Anderson , Hsin-Yi Wang , Steven Rostedt , patches@lists.linux.dev Content-Type: text/plain; charset="UTF-8" Hi Catalin, On Thu, Jun 2, 2022 at 9:41 PM Catalin Marinas wrote: > > On Wed, 1 Jun 2022 19:21:09 -0700, Stephen Boyd wrote: > > A static key warning splat appears during early boot on arm64 systems > > that credit randomness from devicetrees that contain an "rng-seed" > > property. This is because setup_machine_fdt() is called before > > jump_label_init() during setup_arch(). Let's swap the order of these two > > calls so that jump labels are initialized before the devicetree is > > unflattened and the rng seed is credited. > > > > [...] > > Applied to arm64 (for-next/core), thanks! > > [1/1] arm64: Initialize jump labels before setup_machine_fdt() > https://git.kernel.org/arm64/c/73e2d827a501 I'm not sure precisely what your for-next tag corresponds to, but just FYI, this should probably go into 5.19 asap and be marked for stable@. Jason