From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 E876E405C51 for ; Fri, 15 May 2026 23:09:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778886573; cv=none; b=kLLk81HtIbc8LgB2eIkzrGWyoVjOnqobpQ4w7paj1M4IkurwduLHsrz5Rg/nE6hmTXMqR1znSy77/mjcS1HaudU0HSe0L1QwHWBBXntkH34RfFoT/vER6EAgVumNGrJlMlMCcCvf6OjSMf0mW4a6PwTl6v6Z4L2mrH0z+0DPLWk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778886573; c=relaxed/simple; bh=0SQFxeklXsBm407juMMPotTGjTmrK5iQKqBZ4MDhUtc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=sylcHtRZdF6i/Yd3wyJYeDEGQP1CoSRdVa4J01SYZKx6yA7e9DC8LMfnJDs4wQugGaeH+7xTS+fkG19wUSgjnehE3JoAbmenxb3+8GonlP6k/4kIkwkimPJggnpsqSrAELl9VRkG3ti7neh9DTv6IWeCluCB5xys2WpheHL4qlo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=0ygiuZAz; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=t15tP/Gl; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="0ygiuZAz"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="t15tP/Gl" Date: Sat, 16 May 2026 01:09:27 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1778886569; 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=CEC/ihQwqZu2FtRLiBB5/IopFdK1s9+yhr4u+5BDLQI=; b=0ygiuZAzRRhnaTzBWtUALIifL6wGdkggSjudk7/hQd/Rc9cAUPPJtGEjkW70waPXoFoelS 4lRnqO6QTEe7tw0dCx0APbZ8d31bxw9Hne+8rCJv2NBwdm3uoaIv8yoJH6B2rImoMH00nL dNWW+fn6jci22cdRIVagVaDz+IvrXEIKLfmoZKnWStNuNXHJ6KUJuA1NXYmOZRqfxw5Bof f8AEr+Ki2uuh5Tnqd8kcTVIEviKeg+tqq77vSOhR+Qc3lRBtJSBnmi5O3cM4yo6ysyMURK 3Fs4QxYE6zobTyG1bAXQbK2oB8R0Yz1JHH9OWER0D9+4NZJDc4I9FwfZqWSunA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1778886569; 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=CEC/ihQwqZu2FtRLiBB5/IopFdK1s9+yhr4u+5BDLQI=; b=t15tP/GliRFLmLGSxjLZgFPfsSslUvaPt9w/WIPQdfz2sRH2UUA61lveo59jmPqnhyQkkf xiz2zlLMRLr7EBDw== From: "Ahmed S. Darwish" To: Sohil Mehta Cc: Dave Hansen , Borislav Petkov , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Josh Poimboeuf , Richard Weinberger , Andrew Cooper , Tony Luck , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/3] x86/cpu/intel: Simplify F00F bug notice using pr_notice_once() Message-ID: References: <20260515002500.2463393-1-sohil.mehta@intel.com> <20260515002500.2463393-3-sohil.mehta@intel.com> 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=us-ascii Content-Disposition: inline In-Reply-To: On Fri, 15 May 2026, Sohil Mehta wrote: > > On 5/15/2026 12:14 PM, Ahmed S. Darwish wrote: > > > > > > + pr_notice_once("Intel Pentium with F0 0F bug - workaround enabled.\n"); > > > > I think you can go further and just remove the whole dmesg line. > > > > It's a long-standing user-visible boot message. It doesn't feel worth > removing to save a single line of code. My intention with this series > was to avoid any visible change because of the rarity of these machines. > AFAIK this F00F thing just kills the machine, so I don't know why would a legacy user-space program scan dmesg for that "wourkaround enabled" string. I'd vote to remove it, and restore the message only if user-space /really/ breaks, which I highly doubt. It's not a deal breaker, so I'll leave it here. All the best, Ahmed