Received: by 2002:a05:6602:18e:0:0:0:0 with SMTP id m14csp7660769ioo; Fri, 3 Jun 2022 10:48:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzmoKyDwFvyR85e8+PycYP06L587qglykJRRZyBQBoXUnbWWYKgqZdr4orPHIzrWEP7cuxH X-Received: by 2002:a17:902:c951:b0:163:efad:406d with SMTP id i17-20020a170902c95100b00163efad406dmr11287874pla.55.1654278521697; Fri, 03 Jun 2022 10:48:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654278521; cv=none; d=google.com; s=arc-20160816; b=oXF3n/qZ2i1b7fjUi8TXZGVbJU/stQiGQCQ9MpLWKykjT34ovfs7rxAXTx1rXGjwun Vci8yZoYIvsSNEXimr9eH7AKs86eHp7aBy6Hn7XocZFNlQTgwvJvWO7sz6C/mGU5U0e8 k+HZKJ2yrLmXkorfZ+C2qqONjGAbhPZbCzs/MBW8QIKWbD1q9iMI6tnfb91KQKKOvYa1 6DL6+A4EH7i+0l0Fzs39nN3kZYZFq5TEBummTOe5OEziLBtdcdHchP5DKcu7Z4tOYT0n O5Mgpy59mEwT3yrG325Pjp8xcMJL5UHd8gky2SgB/kPA6qR5XuQlK4UlKeoxK0PKb0w2 G6DA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:references :in-reply-to:mime-version:dkim-signature; bh=Cp+q50RJ/J+jLT5bCGZYImfbQiAwy6ER+VrGCgIzXt4=; b=D1g0ChHgEwGraMq3iJAtH9jMWlZbYHGE+35xX8gqlxGKW8d421JdPn7ciyIZbeVXsb 7bUYiG/n4rQSRvBVwxFJtovBZn2cTMDJi9o0lqQ+osN8UibcrlXyMhnbMmHa+H4J+64D DuwqzqwPvS/LgzLk3NrpEwisBIdtW53foSi6KIsK/uASy1DqHH1gngmKKUvL480hzIdw yQCu+BH/bbbk89BKEHx0z0lkKxg71ypGwpaOrC+xrEuumgE7iGkfIHj33mR/60xTJSk7 kAUszW6/osguG8qA9iMU0Qs5skKA3K4AEppg2G61i7HRV3r+dZgHSDGX8gCyrp0BjCpU fZZw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=BvS+UY8S; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s17-20020a63ff51000000b003fadb07ee46si10728237pgk.442.2022.06.03.10.48.28; Fri, 03 Jun 2022 10:48:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=BvS+UY8S; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242749AbiFCINA (ORCPT + 99 others); Fri, 3 Jun 2022 04:13:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229685AbiFCIM4 (ORCPT ); Fri, 3 Jun 2022 04:12:56 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 14B1E20F50; Fri, 3 Jun 2022 01:12:54 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id CADA9B8222E; Fri, 3 Jun 2022 08:12:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C474C3411E; Fri, 3 Jun 2022 08:12:51 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="BvS+UY8S" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1654243967; 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=Cp+q50RJ/J+jLT5bCGZYImfbQiAwy6ER+VrGCgIzXt4=; b=BvS+UY8SsHnwMpRt/Q8qSLybCqZSXLVnUYSNkC8VbJE629AsVMNQJhZA/tVmzZYef30DZr rpbtUYqbf/dSjGC/Zqyfi0617q7TeaxzYGgbtaHuQzvLSNWyfXz11CNZdIUshYTukfNk/r vzXCk8tBITSiophTSQ4EREVcy7Osz4s= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id d9895c2e (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Fri, 3 Jun 2022 08:12:47 +0000 (UTC) Received: by mail-yb1-f180.google.com with SMTP id i11so12442461ybq.9; Fri, 03 Jun 2022 01:12:46 -0700 (PDT) X-Gm-Message-State: AOAM533qRLSD7e8tZXzO8fDllkjhIIfLd/OTnUYOcVrjcFCE3Iqwp0Ja wcjCOoVBwu1+anXPTMLmp3PqMz7o15YkHDowY7Q= X-Received: by 2002:a5b:dcf:0:b0:64a:6923:bbba with SMTP id t15-20020a5b0dcf000000b0064a6923bbbamr10037670ybr.398.1654243965027; Fri, 03 Jun 2022 01:12:45 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:7110:6407:b0:181:6914:78f6 with HTTP; Fri, 3 Jun 2022 01:12:44 -0700 (PDT) In-Reply-To: References: <20220602212234.344394-1-Jason@zx2c4.com> From: "Jason A. Donenfeld" Date: Fri, 3 Jun 2022 10:12:44 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] ARM: initialize jump labels before setup_machine_fdt() To: Ard Biesheuvel Cc: Greg Kroah-Hartman , Russell King , Russell King , Linux ARM , Linux Kernel Mailing List , Catalin Marinas , Stephen Boyd , "# 3.4.x" Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ard, On 6/3/22, Ard Biesheuvel wrote: > The problem is that your original patch You remain extremely unpleasant to communicate with. Can we keep things on topic please? > As far as I can tell, the early patching code on ARM does not rely on > the early fixmap code. Did you try just moving jump_label_init() > earlier in the function? > > Also, how did you test this change? Just booting a few configs in QEMU. I don't have access to real hardware right now unfortunately. Let me give a try to just moving the jump_label_init() function alone. That'd certainly make this patch a lot more basic, which would be a good thing, and might assuage your well justified concerns that too much boot order churn will break something subtle. I was just afraid of complicated intermingling with the other stuff after I saw that arm64 did things in the other order. But maybe that's silly. I'll send a v2 if that works, and send an update here if it doesn't. Thanks for the suggestion. Jason