Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp897188img; Thu, 21 Mar 2019 11:13:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqz8KFdyMPJ+q58w61MZkkF7hAuBEmmqjntl/ZYvB05S7SMWKq1vG2HDhw1bcBULw/9v48sd X-Received: by 2002:a63:5318:: with SMTP id h24mr4623801pgb.76.1553192008158; Thu, 21 Mar 2019 11:13:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553192008; cv=none; d=google.com; s=arc-20160816; b=sJveDhy2kds9JVN1y+H2u+5GVHPxtusj98wBTv8D1fx/YXskbA634OoKfgqJromVKP 4JeWY+QACJegN9YaOeGOiZXvW7sgtTZDQkxGCwp7B1t6HuFjuseVkrg+UagWx4aEPOVO qLxEYl3PJRcBD5OfIxmYz4bg7UK36Fz0BLpiOA8wD2xIgo+67heZu3Bnm3UWiRT4Osdn u8hx8ul5luZ/2rh2UdPIFep4UGSFytmIdhzOeyp2l3agzapyLiToyPupwqGRqFegvFzs UoDUj+3NHPeCDKcv2//eZj3YxZ7Sb4LCo0LnKY/n0CGNgnHX3tDC1hx9So1RHRZMiRSi kn0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=YkNxbf0E0jbQEoMxZerDlRZDeodnnKCLIreH3PtiPq0=; b=aj3RWimK/NXl/YVWEok1h1JgV6jSMzE1CkNx7q0rke//8o9XoThBpoFeyPQsBfMA94 r+7D+ZakgBitwVV9dZj9ImfNHp16s5NnLUnzvnmb3XafxUzYtrXtLrrAOEScNf4SOWOO /7gBECAY2yEsVD85R5L6SPJcAJH+MmECLcWKUG3w/wR5b4+KtRhPzlRaBnsCt1F2+8Xo ib2eHs+4ZRGaHkpMaq1yGf9gAEuzGnPNelFwkpmWHQp1YzyQXwtf8BpHRF3UQ6+Kxr05 PYaQFM1fo5OKOPGF/f6Kc7bd0O2E6rF5d7Il5d7PNkkH8QII5fZ6PWfHLzpphmFOj/hw u5tQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h11si5235220plb.38.2019.03.21.11.13.12; Thu, 21 Mar 2019 11:13:28 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728807AbfCUSKX (ORCPT + 99 others); Thu, 21 Mar 2019 14:10:23 -0400 Received: from mail.kernel.org ([198.145.29.99]:43642 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728513AbfCUSKX (ORCPT ); Thu, 21 Mar 2019 14:10:23 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B61E7218A2; Thu, 21 Mar 2019 18:10:21 +0000 (UTC) Date: Thu, 21 Mar 2019 14:10:20 -0400 From: Steven Rostedt To: Andy Lutomirski Cc: Peter Zijlstra , Juergen Gross , LKML , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Joel Fernandes , He Zhe , Linus Torvalds , Clark Williams Subject: Re: [RFC][PATCH] tracing/x86: Save CR2 before tracing irqsoff on error_entry Message-ID: <20190321141020.641e313f@gandalf.local.home> In-Reply-To: References: <20190320221534.165ab87b@oasis.local.home> <20190321083317.GL6058@hirez.programming.kicks-ass.net> <20190321090241.GL6521@hirez.programming.kicks-ass.net> <20190321104517.GM6521@hirez.programming.kicks-ass.net> <20190321093242.4a948198@gandalf.local.home> <20190321172203.GS5996@hirez.programming.kicks-ass.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 21 Mar 2019 11:05:06 -0700 Andy Lutomirski wrote: > In the long run, I think the right solution is to rewrite even more of > this mess in C. We really ought to be able to put the IRQ flag > tracing and the context tracking into C code. And once we do that, we can work on getting the irq tracing incorporated into a jump_label type that we could possibly enable lockdep at start up, and then disable it later, even on production systems! That is, to be able to turn it off and bring the system back up to full speed. It would also allow for irq tracing too. Some inquiring minds have been asking about this ;-) -- Steve