All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: fanhuang <FangSheng.Huang@amd.com>
Cc: <qemu-devel@nongnu.org>, <david@redhat.com>,
	<imammedo@redhat.com>, <gourry@gourry.net>, <apopple@nvidia.com>,
	<dan.j.williams@intel.com>, <Zhigang.Luo@amd.com>,
	<Lianjie.Shi@amd.com>
Subject: Re: [PATCH v6 0/1] numa: add 'memmap-type' option for memory type configuration
Date: Thu, 5 Mar 2026 12:32:05 +0000	[thread overview]
Message-ID: <20260305123205.00006ac0@huawei.com> (raw)
In-Reply-To: <20260226105023.256568-1-FangSheng.Huang@amd.com>

On Thu, 26 Feb 2026 18:50:22 +0800
fanhuang <FangSheng.Huang@amd.com> wrote:

> Hi all,
> 
> This is v6 of the SPM (Specific Purpose Memory) patch. Thank you for
> the feedback on v5, especially Gregory's review.
> 
> Changes in v6:
> - Added validation: memmap-type now requires memdev to be specified,
>   to avoid misconfiguration on memory-less NUMA nodes
> - Simplified pc_update_numa_memory_types() by replacing switch/goto
>   with a direct conditional expression
> - Reserved memory nodes are now excluded from SRAT memory affinity
>   entries, since E820 already marks them as reserved and SRAT should
>   not report them as enabled memory affinity
> 
> Use case:
> This feature allows marking NUMA node memory as Specific Purpose Memory
> (SPM) or reserved in the E820 table. SPM serves as a hint to the guest
> that this memory might be managed by device drivers based on guest policy
> 
> Example usage:
>   -object memory-backend-ram,size=8G,id=m0
>   -object memory-backend-memfd,size=8G,id=m1
>   -numa node,nodeid=0,memdev=m0
>   -numa node,nodeid=1,memdev=m1,memmap-type=spm
> 
> Supported memmap-type values:
>   - normal:   Regular system RAM (E820 type 1, default)
>   - spm:      Specific Purpose Memory (E820 type 0xEFFFFFFF), a hint
>               that this memory might be managed by device drivers
>   - reserved: Reserved memory (E820 type 2), not usable as RAM
Interface looks good to me.  I'm not familiar enough to confirm the
x86 specific elements without more time than I have today though so
no tags from me.

Thanks for doing this! 

Jonathan


      parent reply	other threads:[~2026-03-05 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 10:50 [PATCH v6 0/1] numa: add 'memmap-type' option for memory type configuration fanhuang
2026-02-26 10:50 ` [PATCH v6 1/1] " fanhuang
2026-02-27 20:34   ` David Hildenbrand
2026-03-02  9:01     ` Huang, FangSheng (Jerry)
2026-03-04 17:16       ` David Hildenbrand
2026-03-04 17:19   ` Gregory Price
2026-03-05 10:39     ` Huang, FangSheng (Jerry)
2026-03-05 21:06   ` Gregory Price
2026-03-06  5:48     ` Huang, FangSheng (Jerry)
2026-03-05 12:32 ` Jonathan Cameron via qemu development [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=20260305123205.00006ac0@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=FangSheng.Huang@amd.com \
    --cc=Lianjie.Shi@amd.com \
    --cc=Zhigang.Luo@amd.com \
    --cc=apopple@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=gourry@gourry.net \
    --cc=imammedo@redhat.com \
    --cc=jonathan.cameron@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.