From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from stravinsky.debian.org (stravinsky.debian.org [82.195.75.108]) (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 9E4FA3FCB20 for ; Tue, 24 Mar 2026 13:44:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=82.195.75.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774359843; cv=none; b=p1T/p+VpL9vgSiDGW9uKzVAp8eAyjpd/BKjhF/wQYTq4kyPHp0ZUpqeEwDYTv6glHlvcadmGjCuFIiOHn8XXCZA00SEu0k2CVXG3/D8lrRleAu6VB1PF1wPeod/zsdKtvke7w8QWz/5Ne/nPKa2f9tu65qDzRrhDY1yZ9NJW+Pk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774359843; c=relaxed/simple; bh=1nsFdToyntePBoXlyyG2xfzskpRJisEXojHx4jRWnz8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=a8Fi5jR1pK8qdcp69CHByiXad6LBRpnoDcRuStN4uGwwgxtR5f89AFlTF8qi4FNRsORkxOnVt4FgPKbL/CgHdHCfBfzstHw2cbTb8rN3xz6Kffh0u9zDwwWkGibnZrSXuJ6/Dn6XGTOXbXT71SM8AMzp0kNeIWiLgp7lBZKXn3c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org; spf=none smtp.mailfrom=debian.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b=Oakj5iUi; arc=none smtp.client-ip=82.195.75.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=debian.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b="Oakj5iUi" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-ID:Content-Description; bh=1nsFdToyntePBoXlyyG2xfzskpRJisEXojHx4jRWnz8=; b=Oakj5iUiFGgUpGZSd1N2SKIy/K wzJiSQ3bG4jSK+eV2+AeFtdAFAzGoq50NK28ur8yKcNO5ore/HfN80CisAppeWv0r30CDvEGyub5o Ps+fa0qlXRZ8nhuIwgrvAQoKsI7SpKNF5RhjupJFjZX9x1kzqsqy+x7LsiEXSezD4Wj6hvObsy4a5 xC+0LKhtXzXq2+qcvSzWo7pc0ydJN4hCx7ddB1QQ8vpzDO5JY48PTpp2JodnaFQ3QFq7iM4a+Dri6 8rvYUZVwkyx9K7egysaT7BfqM1vsseAnzHdYVeZqqk1m9q4GFvnUuNlPu2THed+HhU4JSLktpk6vI NRoaVmUQ==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from ) id 1w5231-008LNb-4V; Tue, 24 Mar 2026 13:43:54 +0000 Date: Tue, 24 Mar 2026 06:43:48 -0700 From: Breno Leitao To: Masami Hiramatsu Cc: oss@malat.biz, catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com, paulmck@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kernel-team@meta.com Subject: Re: arm64: pseudo NMI bootconfig question Message-ID: References: <20251113133403.308046d2df1c97ba7dcd2388@kernel.org> <20260320130316.5be6fc45f7860d5ac44c4de1@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260320130316.5be6fc45f7860d5ac44c4de1@kernel.org> X-Debian-User: leitao Hello Masami, On Fri, Mar 20, 2026 at 01:03:16PM +0900, Masami Hiramatsu wrote: > On Thu, 19 Mar 2026 08:20:27 -0700> Breno Leitao wrote: > > On Thu, Nov 13, 2025 at 02:37:22AM -0800, Breno Leitao wrote: > > > On Thu, Nov 13, 2025 at 01:34:03PM +0900, Masami Hiramatsu wrote: > > > > > > Another possible solution would be to load bootconfig earlier in the > > > boot process so that early parameters can be defined within bootconfig. > > > Petr suggested this approach some time back, but it doesn't appear to > > > have made it upstream. > > > > > > https://lore.kernel.org/all/20231123194106.08f5832f558fe806b1fd8098@kernel.org/ > > > > > > I'm not fully up to speed on the details of this change, so I want to > > > ask directly: Would Petr's approach—allowing early parameters to be set > > > via bootconfig make sense from a bootconfig design perspective? > > > > Would it be worthwhile for me to take Petr's patch, update it to the > > current codebase, address any issues, and verify that it resolves the > > problem described above? If so, would you be open to reviewing and > > potentially accepting such a patch? > > Hmm, let me recheck it. But the thread seems suspended. > Can you or Petr continue to work on this? Thank you for the feedback. I reviewed Petr's patch and decided to take a more focused approach that specifically addresses the early parameter issue, which is currently biting me. I'd appreciate your thoughts on whether this direction properly solves the problem, and we can continue the discussion there. https://lore.kernel.org/all/20260324-early_bootconfig-v1-1-1c0e625aff06@debian.org/