From: Heiko Carstens <hca@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-s390@vger.kernel.org, virtualization@lists.linux.dev,
linux-doc@vger.kernel.org, kvm@vger.kernel.org,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v3 7/7] s390/sparsemem: provide memory_add_physaddr_to_nid() with CONFIG_NUMA
Date: Wed, 30 Oct 2024 10:30:17 +0100 [thread overview]
Message-ID: <20241030093017.6264-G-hca@linux.ibm.com> (raw)
In-Reply-To: <20241025141453.1210600-8-david@redhat.com>
On Fri, Oct 25, 2024 at 04:14:52PM +0200, David Hildenbrand wrote:
> virtio-mem uses memory_add_physaddr_to_nid() to determine the NID to use
> for memory it adds.
>
> We currently fallback to the dummy implementation in mm/numa.c with
> CONFIG_NUMA, which will end up triggering an undesired pr_info_once():
>
> Unknown online node for memory at 0x100000000, assuming node 0
>
> On s390, we map all cpus and memory to node 0, so let's add a simple
> memory_add_physaddr_to_nid() implementation that does exactly that,
> but without complaining.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> arch/s390/include/asm/sparsemem.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
...
> diff --git a/arch/s390/include/asm/sparsemem.h b/arch/s390/include/asm/sparsemem.h
> index ff628c50afac..6377b7ea8a40 100644
> --- a/arch/s390/include/asm/sparsemem.h
> +++ b/arch/s390/include/asm/sparsemem.h
> @@ -5,4 +5,12 @@
> #define SECTION_SIZE_BITS 27
> #define MAX_PHYSMEM_BITS CONFIG_MAX_PHYSMEM_BITS
>
> +#ifdef CONFIG_NUMA
> +static inline int memory_add_physaddr_to_nid(u64 addr)
> +{
> + return 0;
> +}
> +#define memory_add_physaddr_to_nid memory_add_physaddr_to_nid
> +#endif /* CONFIG_NUMA */
> +
We would need to have the same for phys_to_target_node(), even though
it looks like this won't be used on s390 currently.
Anyway, I'll add that, if I don't forget about it :)
For this patch:
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
next prev parent reply other threads:[~2024-10-30 9:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:14 [PATCH v3 0/7] virtio-mem: s390 support David Hildenbrand
2024-10-25 14:14 ` [PATCH v3 1/7] Documentation: s390-diag.rst: make diag500 a generic KVM hypercall David Hildenbrand
2024-10-30 9:18 ` Heiko Carstens
2024-10-31 14:56 ` Eric Farman
2024-10-31 21:41 ` David Hildenbrand
2024-10-25 14:14 ` [PATCH v3 2/7] Documentation: s390-diag.rst: document diag500(STORAGE LIMIT) subfunction David Hildenbrand
2024-10-30 9:18 ` Heiko Carstens
2024-10-31 14:58 ` Eric Farman
2024-10-25 14:14 ` [PATCH v3 3/7] s390/physmem_info: query diag500(STORAGE LIMIT) to support QEMU/KVM memory devices David Hildenbrand
2024-10-30 9:23 ` Heiko Carstens
2024-10-30 9:42 ` David Hildenbrand
2024-10-30 10:04 ` Heiko Carstens
2024-10-30 14:32 ` Alexander Gordeev
2024-10-30 16:43 ` David Hildenbrand
2024-10-25 14:14 ` [PATCH v3 4/7] virtio-mem: s390 support David Hildenbrand
2024-10-30 9:24 ` Heiko Carstens
2024-10-25 14:14 ` [PATCH v3 5/7] lib/Kconfig.debug: default STRICT_DEVMEM to "y" on s390 David Hildenbrand
2024-10-25 14:14 ` [PATCH v3 6/7] s390/sparsemem: reduce section size to 128 MiB David Hildenbrand
2024-10-25 14:14 ` [PATCH v3 7/7] s390/sparsemem: provide memory_add_physaddr_to_nid() with CONFIG_NUMA David Hildenbrand
2024-10-30 9:30 ` Heiko Carstens [this message]
2024-10-30 9:34 ` [PATCH v3 0/7] virtio-mem: s390 support Heiko Carstens
2024-10-30 16:49 ` Christian Borntraeger
2024-10-31 14:52 ` Eric Farman
2024-10-31 16:27 ` Sumanth Korikkar
2024-10-31 16:47 ` Sumanth Korikkar
2024-10-31 17:30 ` David Hildenbrand
2024-11-04 10:14 ` Heiko Carstens
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=20241030093017.6264-G-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=eperezma@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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