Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1075422ybl; Tue, 13 Aug 2019 07:04:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqw+jkew8RVrLbCS+wPOhH62+CQTRjnIrCIawaAns1dHCNdtTSnnVtwW7fUFdMrVDX+K1a1v X-Received: by 2002:a63:e62:: with SMTP id 34mr34213479pgo.331.1565705052064; Tue, 13 Aug 2019 07:04:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565705052; cv=none; d=google.com; s=arc-20160816; b=nCW1SwIKEDgrogojG9wDjT3hGN5VorNwsod1CM51XH6GRXp9oHp9sXJjM4v8aCUMvG tm/E06A/Ak/CqYXKNsJvfwOEDRZ5o16cAOqSzENbBjbLMPvtIFGKLhcjLvocqS7VPtl7 8GycEvgbhHuKP3BU++P4rFB9o+tOQr+a8LQ4Q+KFKyK4NCKBwKIkDs5K0/r3qb+NM8Jp gEGzhvF/BryTw50IpQNBVJrLbeWoltF0zyfgHsEy4BcKN8HRxXEx2asYFoYQ0eyfnv/i ee0+6kTNN21tihF8xynLBLN1lLSk+XRTLMKxJpiufiDq/5yflXXfVpZrkAez09GdBO3T dK8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=2pU4nkENhjLyIa30KrgmsalHxeSqjkh3gphz3a4Mc7U=; b=F3w81nA6afpTiDReeVae67unNx3kn98Q1FZu6BK5RURb6kZhqcgHJJGJlu6jHrbzyM 4s6BO7kqgt4JnzfSI8qMTH5y3Vd9F/Ch7tPbk4VLB5r/GoDnnhIQuk2p2hdRCcxt95oL 89DSLKSQk/gB0VQdShqeK6RHS6HZgh/a8anm6HlP2NiLrfcLtW3fJn8b/d2aSiQFPC9e kn/tHnqbcinIw25kRSsS0DNzM8YLgafvOMllFNkPkLpfpSIvA2X3MTIRW26e8wHSM42v SwdOzeft9T2LjdUjv+DUcBcxsrfGzO1n/sUBDwQh227A6wDLVO51+AvIbKjQyinJdf5W EBCA== 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 b74si65339364pfb.281.2019.08.13.07.03.54; Tue, 13 Aug 2019 07:04:12 -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 S1729465AbfHMOCY (ORCPT + 99 others); Tue, 13 Aug 2019 10:02:24 -0400 Received: from mx2.suse.de ([195.135.220.15]:36028 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728095AbfHMOCY (ORCPT ); Tue, 13 Aug 2019 10:02:24 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id E0524AD95; Tue, 13 Aug 2019 14:02:22 +0000 (UTC) Date: Tue, 13 Aug 2019 16:02:17 +0200 (CEST) From: Miroslav Benes To: Josh Poimboeuf cc: Joe Lawrence , heiko.carstens@de.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, jikos@kernel.org, pmladek@suse.com, nstange@suse.de, live-patching@vger.kernel.org Subject: Re: [PATCH] s390/livepatch: Implement reliable stack tracing for the consistency model In-Reply-To: <20190728203053.q3pafkwnzm5j3ccs@treble> Message-ID: References: <20190710105918.22487-1-mbenes@suse.cz> <20190716184549.GA26084@redhat.com> <20190728203053.q3pafkwnzm5j3ccs@treble> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 28 Jul 2019, Josh Poimboeuf wrote: > On Wed, Jul 17, 2019 at 01:01:27PM +0200, Miroslav Benes wrote: > > > On a related note, do you think it would be feasible to extend (in > > > another patchset) the reliable stack unwinding code a bit so that we > > > could feed it pre-baked stacks ... then we could verify that the code > > > was finding interesting scenarios. That was a passing thought I had > > > back when Nicolai and I were debugging the ppc64le exception frame > > > marker bug, but didn't think it worth the time/effort at the time. > > > > That is an interesting thought. It would help the testing a lot. I will > > make a note in my todo list. > > Another idea I had for reliable unwinder testing: add a > CONFIG_RELIABLE_STACKTRACE_DEBUG option which does a periodic stack > trace and warns if it doesn't reach the end. It could triggered from a > periodic NMI, or from schedule(). Noted as well. Miroslav