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;
Date:   Fri, 19 May 2023 23:51:40 +0100 (BST)
From:   "Maciej W. Rozycki" <macro@orcam.me.uk>
To:     Jiaxun Yang <jiaxun.yang@flygoat.com>
cc:     "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
        linux-kernel@vger.kernel.org,
        Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH 1/3] MIPS: Introduce WAR_4KC_LLSC config option
In-Reply-To: <53043C18-7C75-4D5F-A15E-86D981D19CA8@flygoat.com>
Message-ID: <alpine.DEB.2.21.2305192342180.27887@angie.orcam.me.uk>
References: <20230519164753.72065-1-jiaxun.yang@flygoat.com> <20230519164753.72065-2-jiaxun.yang@flygoat.com> <alpine.DEB.2.21.2305192117230.50034@angie.orcam.me.uk> <53043C18-7C75-4D5F-A15E-86D981D19CA8@flygoat.com>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

On Fri, 19 May 2023, Jiaxun Yang wrote:

> > Given the circumstances I think this should be `panic'.  You don't want 
> > to continue with a system that can randomly lock up.
> 
> I just checked how other architectures handle such situation, it seems like
> TAINT_CPU_OUT_OF_SPEC is a better option.

 That can be easily missed, just as a random message in the kernel log, 
even at a high priority, and LOGLEVEL_ERR is not particularly high even.  
For a system configuration that qualifies as not usable for any practical 
purpose I find this approach leaving something to desire.

> Panic in cpu_probe can be frustrating for users as it is earlier than initialisation
> of consoles so the panic message can never be read by users.

 Is there no early console support for the systems affected?

  Maciej