Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2969316imu; Fri, 18 Jan 2019 02:27:54 -0800 (PST) X-Google-Smtp-Source: ALg8bN6XH0o2lkggupdYtuMf5CtKIBh7oFB4u0A14dVys2+K0/AQObTPDPPuUfkSmj1bE2yNN2R2 X-Received: by 2002:a63:104d:: with SMTP id 13mr17100063pgq.303.1547807274298; Fri, 18 Jan 2019 02:27:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547807274; cv=none; d=google.com; s=arc-20160816; b=pbsi5ftRsugfqeabNJxuciRMEiBzp06i6letjfPPhwdBaYRpTaxjI/pzYl7qtVmJly SEIje3LtAP4FJdIxY6wi2Hhpk7KqvFyouYXUcVQ0umfobTwD+ZQT5dXPxu5yX0a+0lnn /lSSkrVo0IOn4S8B5FAvhZPd1V/KkY5d4R+Dsv/2aOplX55XEPrU8fM5WSRKzuc9Vykt qM1i8UieHN7eedHietZlSjMhdosa2PCrdq41A4rL5tHB5qDaCkmrXPbDuL4uunwb6qVb u1/RCus2XqAlI5Jz2RpHbn/psH5DWY++QJStPlGCWlVHtdDpTdmX0lGzLZ9jZSLFOEu9 Baxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=rHjjAoPZ5WzSd01uaObMcFJeh6ALPK1Gb/WHY2w5Pz8=; b=oHMVm00inPVJliLVnwrYrvl4V1pfEH5dqsij7iH6s0WMNAV+VATNVLZpMVCUFtB4oe hCphcQrdg3x/2QIo4mwReHS8ZOE2VGs8v0+XXA9aQGL32wtbTjrWk8f1p2fnUzQQGG5l 56P+RYt4WRID5/lKQ08uJmSU5FYy2Oi0MICxaHZ27J3ozYp1UOczziFqvKiWQqdlDHVt UUxgwck5sPL3z4CsdUiA0GHr3nJHzICq5MhoiteLRi/sVvphtZLziXhyjO3jQICxArRc SbQ96pg4b3jKQDSoB/HfXOGsu525ccgP6LZ8u9fsEZUxm8h4MVpI6fUrMJcCVmZ6VDKI bPww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=YEzc1aPy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u25si3758691pgm.532.2019.01.18.02.27.38; Fri, 18 Jan 2019 02:27:54 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=YEzc1aPy; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727128AbfARKYu (ORCPT + 99 others); Fri, 18 Jan 2019 05:24:50 -0500 Received: from mail.skyhub.de ([5.9.137.197]:59672 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726880AbfARKYt (ORCPT ); Fri, 18 Jan 2019 05:24:49 -0500 Received: from zn.tnic (p200300EC2BCB1B0039C8CE17CD8BEE66.dip0.t-ipconnect.de [IPv6:2003:ec:2bcb:1b00:39c8:ce17:cd8b:ee66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 038BF1EC0242; Fri, 18 Jan 2019 11:24:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1547807088; 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: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=rHjjAoPZ5WzSd01uaObMcFJeh6ALPK1Gb/WHY2w5Pz8=; b=YEzc1aPy3mXS3qxIvYcxq0E0DAJLq2Su44Fw1dsitFo2thcK2+srOrcFwxCWb+FW9zfvGD Mp0RL3mPPcq42t6gQeBz44emTDHXFAiNCAUHtLZ9ASqvYKiynA5XIoaZfnSQU55h/J64oH /g6G2YYqbOWCKCKDI2x8qQqVzpNWh+w= Date: Fri, 18 Jan 2019 11:24:27 +0100 From: Borislav Petkov To: Peter Zijlstra Cc: James Morse , Waiman Long , Zhenzhong Duan , LKML , SRINIVAS , Steven Rostedt Subject: Re: Question about qspinlock nest Message-ID: <20190118102427.GA622@zn.tnic> References: <910e9fb6-d0df-4711-fe2b-244b3c20eb82@redhat.com> <20190110201217.GH2861@worktop.programming.kicks-ass.net> <20190114131613.GB10486@hirez.programming.kicks-ass.net> <830db851-d5cb-4081-8d72-e3f3a0a282df@arm.com> <20190118100229.GB27931@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190118100229.GB27931@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 18, 2019 at 11:02:29AM +0100, Peter Zijlstra wrote: > Well, x86 too has multiple non-maskable vectors, and afaik only the > actual NMI vector is covered in tricky. But our MCE vector is > non-maskable too (and I have vague memories of there being more). > > Boris, Rostedt, WTH happens if our MCE code goes and hits a #BP ? (not > unlikely with this proliferation of self-modifying code) > > Anyway, the idea is that they can indeed not interrupt themselves, but I > would not be surprised if the whole MCE thing is riddled with fail (on > x86). As we talked on IRC: we'll apply a mixture of "So don't do that then!" hints i.e., kprobing MCE code etc, and fix the issues like the schedule_work() invocation. In general, I'd like to make/keep the #MC handler as simple and as idiot-proof as possible. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.