From: Dan Williams <dan.j.williams@intel.com>
To: Robert Richter <rrichter@amd.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, Robert Richter <rrichter@amd.com>,
Len Brown <lenb@kernel.org>
Subject: RE: [PATCH v2 2/3] ACPI/NUMA: Print CXL Early Discovery Table (CEDT)
Date: Tue, 19 Mar 2024 13:18:10 -0700 [thread overview]
Message-ID: <65f9f3027ea4e_7702a29462@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20240319120026.2246389-3-rrichter@amd.com>
Robert Richter wrote:
> The CEDT contains similar entries as the SRAT. For diagnostic reasons
> print the CEDT same style as the SRAT.
How about move this to pr_debug()? We have lived without this for a
significant amount of time and it is not clear that CXL debug scenarios
have been hampered by not having this in the log by default.
next prev parent reply other threads:[~2024-03-19 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 12:00 [PATCH v2 0/3] SRAT/CEDT fixes and updates Robert Richter
2024-03-19 12:00 ` [PATCH v2 1/3] x86/numa: Fix SRAT lookup of CFMWS ranges with numa_fill_memblks() Robert Richter
2024-03-19 20:15 ` Dan Williams
2024-03-21 8:09 ` Robert Richter
2024-03-20 17:46 ` Alison Schofield
2024-03-21 16:55 ` Robert Richter
2024-03-21 18:39 ` Alison Schofield
2024-03-21 22:17 ` Robert Richter
2024-03-19 12:00 ` [PATCH v2 2/3] ACPI/NUMA: Print CXL Early Discovery Table (CEDT) Robert Richter
2024-03-19 20:18 ` Dan Williams [this message]
2024-03-20 17:47 ` Alison Schofield
2024-03-19 12:00 ` [PATCH v2 3/3] ACPI/NUMA: Remove architecture dependent remainings Robert Richter
2024-03-19 20:44 ` Dan Williams
2024-03-22 2:12 ` kernel test robot
2024-03-28 16:49 ` Robert Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65f9f3027ea4e_7702a29462@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rrichter@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox