linux-cxl.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <dan.j.williams@intel.com>
To: Dave Jiang <dave.jiang@intel.com>, <linux-cxl@vger.kernel.org>
Cc: <dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>
Subject: Re: [PATCH] cxl: Demote extended linear cache missing emissions
Date: Mon, 25 Aug 2025 12:31:18 -0700	[thread overview]
Message-ID: <68acba06c773d_75e31009@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20250825173521.2788927-1-dave.jiang@intel.com>

Dave Jiang wrote:
> Demote extended linear cache missing emissions to debug level as most
> systems do not have this feature enabled and the complaint about missing
> feature is spammy.
> 
> Suggeted-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
>  drivers/cxl/acpi.c        | 6 +++---
>  drivers/cxl/core/region.c | 6 +++---
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/cxl/acpi.c b/drivers/cxl/acpi.c
> index 712624cba2b6..e56b3d96cdef 100644
> --- a/drivers/cxl/acpi.c
> +++ b/drivers/cxl/acpi.c
> @@ -359,9 +359,9 @@ static int cxl_acpi_set_cache_size(struct cxl_root_decoder *cxlrd)
>  	 */
>  	size = size >> 1;
>  	if (cache_size && size != cache_size) {
> -		dev_warn(&cxld->dev,
> -			 "Extended Linear Cache size %pa != CXL size %pa. No Support!",
> -			 &cache_size, &size);
> +		dev_dbg(&cxld->dev,
> +			"Extended Linear Cache size %pa != CXL size %pa. No Support!",
> +			&cache_size, &size);

The log spam I was seeing was:

"cxl root0: Extended linear cache calculation failed rc:-2"

The concern is whether this mismatch should be reported or result in a
more violent fallback of disabling CXL regions altogether and fallback
to EFI_MEMORY_SP delineated dax devices. I think at any point where the
driver is confused by firmware the CXL subsystem should probably try to
fail safely into vanilla device-dax mode. This needs Smita's work, but
there is really nothing the user can do about a persistent boot warning
unless there is a chance they can get a fix from their BIOS vendor.

      reply	other threads:[~2025-08-25 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 17:35 [PATCH] cxl: Demote extended linear cache missing emissions Dave Jiang
2025-08-25 19:31 ` dan.j.williams [this message]

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=68acba06c773d_75e31009@dwillia2-mobl4.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=vishal.l.verma@intel.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;
as well as URLs for NNTP newsgroup(s).