From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38416C433E7 for ; Sun, 11 Oct 2020 20:00:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C65BA2145D for ; Sun, 11 Oct 2020 20:00:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="bFyvD3Ha"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="yFK29wb9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726984AbgJKUAi (ORCPT ); Sun, 11 Oct 2020 16:00:38 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:40752 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726335AbgJKUAh (ORCPT ); Sun, 11 Oct 2020 16:00:37 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1602446436; 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=rpI+/VDI/eLtFN7Wtd3XRlKtugOdm7U5hjPzfzci+ZU=; b=bFyvD3HapyI/PYaFffg7m1LUySB7jFx8hxq/q+nz6LeIWotWY5CuD7K+BhrwmLVRg2J1cn Q8JRGDZGIt9NdNnIy6NjuovsqO0RTrvhTTwYPPaFgkvnGbVYlY1qrChOj5TmolYW6iRr63 /1HCej5DTjGDpo1ti4iuloYqZDkgc2aReuCGwNiv8/AlW+OLa4JPx6IhhN+VEM7+/wKZsD o/fUhLTLxmOBF4ngQb99Nk9p1S9aYRcwAnWrTcPB7tsIbdTDEA3TcXhql0IVpM7gqOul3D TeId3FEHeMkZA8KSRn8Yt3GC2WNjxjEHNZlqjZQHosuFC14hQ5KcpJS2NbObGA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1602446436; 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=rpI+/VDI/eLtFN7Wtd3XRlKtugOdm7U5hjPzfzci+ZU=; b=yFK29wb9vfiPJ5uUm+9GPidZQQazef8nMpEKmmbO1KeuBfSZUDbGXPG/5pnOoDWwes+xXx 3ZwdfiUsQMY+R0CQ== To: Linus Torvalds , Ingo Molnar Cc: Linux Kernel Mailing List , Borislav Petkov , Peter Zijlstra , Andrew Morton Subject: Re: [GIT PULL] x86 fixes In-Reply-To: References: <20201011080859.GA3598074@gmail.com> Date: Sun, 11 Oct 2020 22:00:35 +0200 Message-ID: <87k0vwr0rg.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus, On Sun, Oct 11 2020 at 11:00, Linus Torvalds wrote: > On Sun, Oct 11, 2020 at 1:09 AM Ingo Molnar wrote: >> >> - Fix a (hopefully final) IRQ state tracking bug vs. MCE handling > > Why is the nmi_enter/nmi_exit thing not a problem on non-x86 architectures? > > Put another way: x86 does extra work to track IRQ state across NMI. > What makes x86 special? It _feels_ to me like everybody should do > that? No? > > Please tell me what I've missed.. Not a lot. The nmi related tracking plus the entry/exit inconsistencies which we identified and fixed over the past couple of releases in x86 apply pretty much to all of arch/* in one way or the other and of course in different flavours. This is worked on by architecture people and will hopefully be solved at some point by moving all architectures to the generic entry code. Thanks, tglx