From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from stravinsky.debian.org (stravinsky.debian.org [82.195.75.108]) (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 B568C369997 for ; Fri, 30 Jan 2026 11:08:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=82.195.75.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769771293; cv=none; b=l6qq15SY1F++DGgujxbFhk3dwKZdb/fEyMmGRXQ9KkfHNyfgNxp6yRLiI7xDSyZbYFcyApw71qI8s5ab1Nc/Mxik+kLRmUBfOcwxM7a9CYL5vEm8nIqWlF6Ndj6QGw6uA8jF1+s8JeNACX8ZiPRE41BTdAndnduTFHkgwcXNjhw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769771293; c=relaxed/simple; bh=RWrHjYgZgg+KSNMmeqGnhJJifZmxh3jh3m1lxZ6fpOk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=HPyISkc/NsoYlpbgq+alZbYnvBOmdB80YxkXs2ChGtuBGEuUjLv5RH7Icjhf4tJkXJfHomjQnLSBIch+qJL5eLGDuqhU6XgAheVIgbN4GiqSpDi9Obf/+iHrpSIWSUDa987YUF54zmTmbgd+twJP6DIv5BzJqbxxZoA6ZgKROv0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org; spf=none smtp.mailfrom=debian.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b=Dn10uzU8; arc=none smtp.client-ip=82.195.75.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=debian.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b="Dn10uzU8" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=RWrHjYgZgg+KSNMmeqGnhJJifZmxh3jh3m1lxZ6fpOk=; b=Dn10uzU8MbHOCG9+efqNiLQwpI KxN6uS/lHev3RV0mXNRHRWpBzdwR851sKMQ+M8w1R+/Rkac/c9kseeDYEQh0mQD0QXQhuX2E18kyO C3/OhTYf+36LyCtIjevNIK4qahd4AT//uTyezbgGynPz8bqsNh1oHuJRQSnmOQML/kd0V7VE3RuEA pjzZf4Ho2ebtGP2Xt6h7EK0asm+sUJ8t9M9X7hA5DMrEdMt+bUePmtwKl8sFEz3dqmj604tm+EoCJ avWXVknQOILA0isw8XZO8SwyfqZHw4UJbHCO5EWz8cDWDpMoWBD4IqSV0+apMcjcChYr4rmB4xOQR AZhFtwpA==; Received: from authenticated user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from ) id 1vlmM1-001fbJ-Tc; Fri, 30 Jan 2026 11:07:58 +0000 Date: Fri, 30 Jan 2026 03:07:52 -0800 From: Breno Leitao To: Baoquan He Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, kernel-team@meta.com, kexec@lists.infradead.org, dyoung@redhat.com, tony.luck@intel.com, xueshuai@linux.alibaba.com, vgoyal@redhat.com, zhiquan1.li@intel.com, olja@meta.com Subject: Re: [PATCH] vmcore_info: expose hardware error recovery statistics via sysfs Message-ID: References: <20260129-vmcoreinfo_sysfs-v1-1-164c1fe1fe07@debian.org> 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-Disposition: inline In-Reply-To: X-Debian-User: leitao On Fri, Jan 30, 2026 at 09:59:58AM +0800, Baoquan He wrote: > On 01/29/26 at 05:34am, Breno Leitao wrote: > > Add a sysfs file at /sys/kernel/vmcore_stats and expose hardware error > > recovery statistics that are already tracked by the kernel. This allows > > userspace monitoring tools to track recovered hardware errors without > > requiring kernel crashes. > > I don't understand. If w/o requring kernel crashes, why do you call it > vmcore_stats? It's a normal showing of hardware error recovery > statistics tracked by kernel, can we name it /sys/kernel/hwerr_stats? Agreed, /sys/kernel/hwerr_stats is a much better name. Thank you for the suggestion! > It's obviously having nothiing to do with vmcore, isn't it? You're correct. The only connection is that this functionality currently resides in kernel/vmcore_info.c. I initially thought it would make sense to create a generic sysfs entry for vmcore, but I can see now that this caused more confusion than clarification. I'll update the patch accordingly. Thanks, --breno