qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Yuquan Wang <wangyuquan1236@phytium.com.cn>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH] docs/cxl: Add serial number for persistent-memdev
Date: Fri, 14 Mar 2025 08:44:05 -0700	[thread overview]
Message-ID: <67d44ec5a79c1_12e31294ea@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250312181035.00006e32@huawei.com>

Jonathan Cameron wrote:
> On Wed, 5 Mar 2025 18:35:40 +0800
> Yuquan Wang <wangyuquan1236@phytium.com.cn> wrote:
> 
> > > 
> > > On Tue, 4 Mar 2025 14:22:48 +0800
> > > Yuquan Wang <wangyuquan1236@phytium.com.cn> wrote:
> > >   
> > > > > 
> > > > > On Thu, Feb 20, 2025 at 04:12:13PM +0000, Jonathan Cameron wrote:    
> > > > > > On Mon, 17 Feb 2025 19:20:39 +0800
> > > > > > Yuquan Wang <wangyuquan1236@phytium.com.cn> wrote:
> > > > > >     
> > > > > > > Add serial number parameter in the cxl persistent examples.
> > > > > > > 
> > > > > > > Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>    
> > > > > > Looks good.  I've queued it up on my gitlab staging tree, but
> > > > > > Michael if you want to pick this one directly that's fine as well.    
> > > > > 
> > > > > See no reason to, I was not even CC'd.    
> > > > 
> > > > Hi, Michael
> > > > 
> > > > I'm sorry, this is my fault. I used "get_maintainer.pl" to check this
> > > > patch's maintainers but it shows "No maintainers found, printing recent
> > > > contributors". 
> > > >   
> > > I usually stage up multiple series together and send on to Michael.
> > > So it was be being lazy for a minor change rather than anything much
> > > that you did wrong.
> > > 
> > > If I get time I'll post a series with this a few other patches
> > > later today.  
> > > 
> > > Jonathan
> > >   
> > Thank you!
> > 
> > BTW, I found a corner case in CXL numa node creation.
> > 
> > Condition: 
> > 1) A UMA/NUMA system without SRAT, but with CEDT.CFMWS
> > 2)Enable CONFIG_ACPI_NUMA
> > 
> > Results:
> > 1) acpi_numa_init: the fake_pxm will be 0 and send to acpi_parse_cfmws()
> > 2)If dynamically create cxl ram region, the cxl memory would be assigned
> > to node0 rather than a new node
> > 
> > Confusions:
> > 1) Is a numa system a requirement for CXL memory usage?
> 
> Obviously discussion has gone on elsewhere, but I'd say in general it
> would be a bad idea to not have an SRAT because the moment we add CXL
> it is definitely a NUMA system and we want the Generic Port entry to
> allow us to get perf information.
> 
> So I wouldn't mind if we fail CXL init in this case, but maybe
> it is worth papering over things.

I think that is too severe. If a driver has a path to advertise
resources, even in a less than ideal way, it should make every effort to
do that. There are plenty of ways for the NUMA information to fail, that
does not mean the memory needs to be prevented from coming online. Let
the end user decide if lack of performance information is fatal.


  reply	other threads:[~2025-03-14 15:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 11:20 [PATCH] docs/cxl: Add serial number for persistent-memdev Yuquan Wang
2025-02-20 16:12 ` Jonathan Cameron via
2025-02-21  2:51   ` Yuquan Wang
2025-02-21 11:24     ` Jonathan Cameron via
2025-02-21 11:55   ` Michael S. Tsirkin
2025-03-04  6:22     ` Yuquan Wang
2025-03-05  6:13       ` Jonathan Cameron via
2025-03-05 10:35         ` Yuquan Wang
2025-03-12 18:10           ` Jonathan Cameron via
2025-03-14 15:44             ` Dan Williams [this message]
2025-03-14 17:03               ` Jonathan Cameron via
2025-03-25  7:49             ` Yuquan Wang
2025-04-04 15:02               ` Jonathan Cameron via
  -- strict thread matches above, loose matches on Subject: below --
2025-03-04  6:15 Yuquan Wang

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=67d44ec5a79c1_12e31294ea@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --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;
as well as URLs for NNTP newsgroup(s).