From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C3B8036214C for ; Mon, 30 Mar 2026 18:26:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=216.40.44.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774895204; cv=none; b=swI8sN1uX4v/Y6wbWPsU/zXgxyT2ZM39TsT0AehmDUCbWcLS6w7lGKLFnj/rImYTL/+/8+GARtDFT5yWQ2+sAq+ZHPC+SrDCTeEJaq9G56dDPHouxSOvdIwltkNsX2ZmDGKe7K8/dbGuOWKxM5grT/BS0vzpAJjyykhLfjG0j3s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774895204; c=relaxed/simple; bh=EELBDBYINL4AwI5yae66UELPxPNXIid6tGan6xmefMQ=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=hce7hB95WfkWrUinPeybg4Jv2ebqoT5IlLhRTaLCyZFoW+sJp4HcKTeEaWj/YUwEpL3M9H0y3cedF1UPdj3dEfVHDZVGqwDpyTsoExcZREQEiJFBgYZaqcYphMWezRG9AcsLu3BKdv12P9oAI9ygc40RearWHsQA30Hh7VYAl6k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org; spf=pass smtp.mailfrom=goodmis.org; arc=none smtp.client-ip=216.40.44.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=goodmis.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=goodmis.org Received: from omf15.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 803B0BA5C1; Mon, 30 Mar 2026 18:26:40 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: rostedt@goodmis.org) by omf15.hostedemail.com (Postfix) with ESMTPA id 6E35617; Mon, 30 Mar 2026 18:26:37 +0000 (UTC) Date: Mon, 30 Mar 2026 14:27:33 -0400 From: Steven Rostedt To: John Stultz Cc: Peter Zijlstra , mingo@kernel.org, juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, bsegall@google.com, mgorman@suse.de, vschneid@redhat.com, linux-kernel@vger.kernel.org, wangtao554@huawei.com, quzicheng@huawei.com, kprateek.nayak@amd.com, dsmythies@telus.net, shubhang@os.amperecomputing.com, Suleiman Souhlal Subject: Re: [PATCH v2 1/7] sched/fair: Fix zero_vruntime tracking Message-ID: <20260330142733.7539ac21@gandalf.local.home> In-Reply-To: References: <20260219075840.162631716@infradead.org> <20260219080624.438854780@infradead.org> <20260328130442.5e51cf9e@gandalf.local.home> X-Mailer: Claws Mail 3.20.0git84 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 6E35617 X-Stat-Signature: 1nf4wfgks736xekchu8k9kw7gar1bmzr X-Rspamd-Server: rspamout03 X-Session-Marker: 726F737465647440676F6F646D69732E6F7267 X-Session-ID: U2FsdGVkX18efUzX1LvLhuelHkaz0idObIGS5hV654Y= X-HE-Tag: 1774895197-60433 X-HE-Meta: U2FsdGVkX19WtZR/FxS3pe2yuQ0FNVLkcPRJa/NdyP8Iz8ZS3NoouTx54ZFzsLqRklQhqkdykwLGR7vIWe8G0hvCNvYtr6TvvRUYjyz2JP5HmaSFhgkxwl7/QfEL2t/FKtXpYKt7aswduqDuc8Ukj22zylm6QEMEyLlLmduPeoM3+G+GTy4QcjEZMjv+8Sn5RS8MHwGnS9EupW0LJVrfXYxc6WPGCNWL30ArOmj5JyGcAxBaEtp1dnTTi18KsMVzWGSJDOLsgQ8kFly9qqaQB1zE9/BE5Lc4abWYU+csSKb3yD/E+oJor19VQTuYcyNK4sZ1+7NOVIrBMjKK1k092HzeUElhUxoq On Mon, 30 Mar 2026 10:58:54 -0700 John Stultz wrote: > Nice. I've actually been using ftrace_dump_on_oops as I log the VM > serial console to a file and don't have to remember to go fetch it out > the next time. But this is helpful when its on real hardware (dumping > the trace over serial console can take awhile and I've had cases where > the hardware watchdogs reboot the device midway when the trace is too > large). > I use it on VMs all the time. It works nicely with qemu. In the near future we will have a backup buffer implementation too, where you don't need to remember to start it! reserve_mem=100M:12M:trace trace_instance=boot_mapped^traceprintk^@trace trace_instance=backup=boot_mapped Where on early boot up, a "backup" instance is created and copies the persistent ring buffer to a read-only temporary buffer that doesn't get overwritten. Then you can keep the persistent ring buffer always on, and if there's a crash, just look at the "backup" instance to see what happened. -- Steve