From: Gregory Price <gourry@gourry.net>
To: fanhuang <FangSheng.Huang@amd.com>
Cc: qemu-devel@nongnu.org, david@redhat.com, imammedo@redhat.com,
jonathan.cameron@huawei.com, Zhigang.Luo@amd.com,
Lianjie.Shi@amd.com
Subject: Re: [PATCH v4 0/1] numa: add 'spm' option for Specific Purpose Memory
Date: Fri, 2 Jan 2026 11:30:15 -0500 [thread overview]
Message-ID: <aVfyl8sylMICO4mc@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20251209093841.2250527-1-FangSheng.Huang@amd.com>
On Tue, Dec 09, 2025 at 05:38:40PM +0800, fanhuang wrote:
> -numa node,nodeid=0,memdev=m0
> -numa node,nodeid=1,memdev=m1,spm=on
>
Should discussion with Jonathan - whatever form this ends up taking, can
we change this from [on,off] to [normal,spm,reserved] and apply the
appropriate types accordingly?
don't know what to name the tag in that case, something like..
memmap_type=[normal,spm,reserved] ?
(not married to this, open to suggestions)
~Gregory
next prev parent reply other threads:[~2026-01-02 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 9:38 [PATCH v4 0/1] numa: add 'spm' option for Specific Purpose Memory fanhuang
2025-12-09 9:38 ` [PATCH v4 1/1] " fanhuang
2025-12-23 9:56 ` Jonathan Cameron via
2025-12-23 10:01 ` David Hildenbrand (Red Hat)
2025-12-26 7:15 ` Huang, FangSheng (Jerry)
2025-12-26 22:46 ` Alistair Popple
2025-12-30 20:09 ` David Hildenbrand (Red Hat)
2026-01-04 10:43 ` Huang, FangSheng (Jerry)
2025-12-29 18:26 ` [PATCH v4 0/1] " Gregory Price
2025-12-30 2:55 ` Huang, FangSheng (Jerry)
2025-12-30 14:06 ` Gregory Price
2025-12-30 20:15 ` David Hildenbrand (Red Hat)
2025-12-30 23:03 ` Gregory Price
2026-01-02 13:09 ` Igor Mammedov
2026-01-02 16:28 ` Gregory Price
2026-01-02 16:30 ` Gregory Price [this message]
2026-01-05 15:29 ` David Hildenbrand (Red Hat)
2026-01-07 9:03 ` Huang, FangSheng (Jerry)
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=aVfyl8sylMICO4mc@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=FangSheng.Huang@amd.com \
--cc=Lianjie.Shi@amd.com \
--cc=Zhigang.Luo@amd.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=qemu-devel@nongnu.org \
/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.