public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Gregory Price <gourry@gourry.net>
Cc: Yuquan Wang <wangyuquan1236@phytium.com.cn>, <rafael@kernel.org>,
	<lenb@kernel.org>, <dave@stgolabs.net>, <dave.jiang@intel.com>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
	<rrichter@amd.com>, <bfaccini@nvidia.com>, <rppt@kernel.org>,
	<haibo1.xu@intel.com>, <chenbaozi@phytium.com.cn>,
	<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI: NUMA: debug invalid unused PXM value for CFMWs
Date: Fri, 14 Mar 2025 16:55:01 +0000	[thread overview]
Message-ID: <20250314165501.00000606@huawei.com> (raw)
In-Reply-To: <Z9QxUNP2aqTGpnMJ@gourry-fedora-PF4VCD3F>

On Fri, 14 Mar 2025 09:38:24 -0400
Gregory Price <gourry@gourry.net> wrote:

> On Fri, Mar 14, 2025 at 10:12:26AM +0000, Jonathan Cameron wrote:
> > On Thu, 13 Mar 2025 11:02:37 -0400
> > Gregory Price <gourry@gourry.net> wrote:
> >   
> > > On Thu, Mar 13, 2025 at 02:09:07PM +0800, Yuquan Wang wrote:  
> > > > @@ -441,6 +441,11 @@ static int __init acpi_parse_cfmws(union acpi_subtable_headers *header,
> > > >  	start = cfmws->base_hpa;
> > > >  	end = cfmws->base_hpa + cfmws->window_size;
> > > >  
> > > > +	if (srat_disabled()) {
> > > > +		pr_err("SRAT is missing or bad while processing CFMWS.\n");
> > > > +		return -EINVAL;
> > > > +	}
> > > > +    
> > > 
> > > I thought the srat was optional regardless of the presence of a CFMWS.
> > > Is this not the case?  
> > 
> > True in theory, but do we want to support it?
> > 
> > I'd vote no unless someone is shipping such a system and can't fix it up.
> > 
> > Jonathan
> >   
> 
> Well, this is really the patch trying to deal with that I suppose. The
> code here already states its creating 1 node per CFMWS in the absense of
> srat - but this patch just changes that and says "no nodes 4 u".  I
> don't think that's what we want either.

Under this specific set of circumstances, "no nodes 4 u" is
to me a perfectly valid answer.

Jonathan


> 
> ~Gregory


  reply	other threads:[~2025-03-14 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  6:09 [PATCH v2] ACPI: NUMA: debug invalid unused PXM value for CFMWs Yuquan Wang
2025-03-13 15:02 ` Gregory Price
2025-03-14 10:12   ` Jonathan Cameron
2025-03-14 13:38     ` Gregory Price
2025-03-14 16:55       ` Jonathan Cameron [this message]
2025-03-13 16:28 ` Alison Schofield
2025-03-14  7:55   ` Yuquan Wang
2025-03-14 16:55     ` Alison Schofield

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=20250314165501.00000606@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=bfaccini@nvidia.com \
    --cc=chenbaozi@phytium.com.cn \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=gourry@gourry.net \
    --cc=haibo1.xu@intel.com \
    --cc=ira.weiny@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=rppt@kernel.org \
    --cc=rrichter@amd.com \
    --cc=vishal.l.verma@intel.com \
    --cc=wangyuquan1236@phytium.com.cn \
    /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