[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <663124e36ecc5_10c21294b6@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Tue, 30 Apr 2024 10:05:39 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Robert Richter <rrichter@....com>, "Rafael J. Wysocki"
<rafael@...nel.org>, Dave Hansen <dave.hansen@...ux.intel.com>, "Andy
Lutomirski" <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>, "Thomas
Gleixner" <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "Borislav
Petkov" <bp@...en8.de>, <x86@...nel.org>
CC: Dan Williams <dan.j.williams@...el.com>, Alison Schofield
<alison.schofield@...el.com>, <linux-acpi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>, Robert Richter
<rrichter@....com>, "H. Peter Anvin" <hpa@...or.com>, Len Brown
<lenb@...nel.org>
Subject: Re: [PATCH v6 5/7] ACPI/NUMA: Return memblk modification state from
numa_fill_memblks()
Robert Richter wrote:
> When registering a memory range a possibly overlapping memory block
> will be extended instead of creating a new one. If both ranges exactly
> overlap, the blocks remain unchanged and are just reused. The
> information if a memblock was extended is useful for diagnostics.
What diagnostic flow is this useful for?
I feel like this post-hoc debug prints for problems we never expect to
have again, or is there an enduring need for this?
Powered by blists - more mailing lists