From: Dan Williams <dan.j.williams@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Justin He <Justin.He@arm.com>, Michal Hocko <mhocko@kernel.org>,
David Hildenbrand <david@redhat.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Chuhong Yuan <hslester96@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Kaly Xin <Kaly.Xin@arm.com>
Subject: Re: [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL
Date: Tue, 7 Jul 2020 23:44:15 -0700 [thread overview]
Message-ID: <CAPcyv4j-vs5pJhr=e3PbuydSfxiEdj_Z5TAvui+pvu28SmgiEA@mail.gmail.com> (raw)
In-Reply-To: <20200708061934.GD386073@linux.ibm.com>
On Tue, Jul 7, 2020 at 11:20 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
[..]
> > Darn, I saw ARCH_KEEP_MEMBLOCK and had delusions of grandeur that it
> > could solve my numa api woes. At least for x86 the problem is already
> > solved with reserved numa_meminfo, but now I'm trying to write generic
> > drivers that use those apis and finding these gaps on other archs.
>
> I'm not sure if x86's numa_meminfo is a part of the solution or a part
> of the problem ;-)
More the latter, but hopefully it can remain an exception and not the rule.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Justin He <Justin.He@arm.com>, Michal Hocko <mhocko@kernel.org>,
David Hildenbrand <david@redhat.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Chuhong Yuan <hslester96@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Kaly Xin <Kaly.Xin@arm.com>
Subject: Re: [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL
Date: Tue, 7 Jul 2020 23:44:15 -0700 [thread overview]
Message-ID: <CAPcyv4j-vs5pJhr=e3PbuydSfxiEdj_Z5TAvui+pvu28SmgiEA@mail.gmail.com> (raw)
In-Reply-To: <20200708061934.GD386073@linux.ibm.com>
On Tue, Jul 7, 2020 at 11:20 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
[..]
> > Darn, I saw ARCH_KEEP_MEMBLOCK and had delusions of grandeur that it
> > could solve my numa api woes. At least for x86 the problem is already
> > solved with reserved numa_meminfo, but now I'm trying to write generic
> > drivers that use those apis and finding these gaps on other archs.
>
> I'm not sure if x86's numa_meminfo is a part of the solution or a part
> of the problem ;-)
More the latter, but hopefully it can remain an exception and not the rule.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Justin He <Justin.He@arm.com>, Michal Hocko <mhocko@kernel.org>,
David Hildenbrand <david@redhat.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Chuhong Yuan <hslester96@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Kaly Xin <Kaly.Xin@arm.com>
Subject: Re: [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL
Date: Tue, 7 Jul 2020 23:44:15 -0700 [thread overview]
Message-ID: <CAPcyv4j-vs5pJhr=e3PbuydSfxiEdj_Z5TAvui+pvu28SmgiEA@mail.gmail.com> (raw)
In-Reply-To: <20200708061934.GD386073@linux.ibm.com>
On Tue, Jul 7, 2020 at 11:20 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
[..]
> > Darn, I saw ARCH_KEEP_MEMBLOCK and had delusions of grandeur that it
> > could solve my numa api woes. At least for x86 the problem is already
> > solved with reserved numa_meminfo, but now I'm trying to write generic
> > drivers that use those apis and finding these gaps on other archs.
>
> I'm not sure if x86's numa_meminfo is a part of the solution or a part
> of the problem ;-)
More the latter, but hopefully it can remain an exception and not the rule.
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Kaly Xin <Kaly.Xin@arm.com>, Justin He <Justin.He@arm.com>,
Baoquan He <bhe@redhat.com>, David Hildenbrand <david@redhat.com>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Chuhong Yuan <hslester96@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL
Date: Tue, 7 Jul 2020 23:44:15 -0700 [thread overview]
Message-ID: <CAPcyv4j-vs5pJhr=e3PbuydSfxiEdj_Z5TAvui+pvu28SmgiEA@mail.gmail.com> (raw)
In-Reply-To: <20200708061934.GD386073@linux.ibm.com>
On Tue, Jul 7, 2020 at 11:20 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
[..]
> > Darn, I saw ARCH_KEEP_MEMBLOCK and had delusions of grandeur that it
> > could solve my numa api woes. At least for x86 the problem is already
> > solved with reserved numa_meminfo, but now I'm trying to write generic
> > drivers that use those apis and finding these gaps on other archs.
>
> I'm not sure if x86's numa_meminfo is a part of the solution or a part
> of the problem ;-)
More the latter, but hopefully it can remain an exception and not the rule.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-08 6:44 UTC|newest]
Thread overview: 162+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 5:59 [PATCH v2 0/3] Fix and enable pmem as RAM device on arm64 Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 5:59 ` [PATCH v2 1/3] arm64/numa: export memory_add_physaddr_to_nid as EXPORT_SYMBOL_GPL Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 11:35 ` David Hildenbrand
2020-07-07 11:35 ` David Hildenbrand
2020-07-07 11:35 ` David Hildenbrand
2020-07-07 11:54 ` Michal Hocko
2020-07-07 11:54 ` Michal Hocko
2020-07-07 11:54 ` Michal Hocko
2020-07-07 12:13 ` Mike Rapoport
2020-07-07 12:13 ` Mike Rapoport
2020-07-07 12:13 ` Mike Rapoport
2020-07-07 12:26 ` David Hildenbrand
2020-07-07 12:26 ` David Hildenbrand
2020-07-07 12:26 ` David Hildenbrand
2020-07-07 18:00 ` Mike Rapoport
2020-07-07 18:00 ` Mike Rapoport
2020-07-07 18:00 ` Mike Rapoport
2020-07-07 22:05 ` Dan Williams
2020-07-07 22:05 ` Dan Williams
2020-07-07 22:05 ` Dan Williams
2020-07-07 22:05 ` Dan Williams
2020-07-08 5:27 ` Mike Rapoport
2020-07-08 5:27 ` Mike Rapoport
2020-07-08 5:27 ` Mike Rapoport
2020-07-08 7:21 ` David Hildenbrand
2020-07-08 7:21 ` David Hildenbrand
2020-07-08 7:21 ` David Hildenbrand
2020-07-08 7:38 ` Mike Rapoport
2020-07-08 7:38 ` Mike Rapoport
2020-07-08 7:38 ` Mike Rapoport
2020-07-08 7:40 ` David Hildenbrand
2020-07-08 7:40 ` David Hildenbrand
2020-07-08 7:40 ` David Hildenbrand
2020-07-08 7:50 ` Dan Williams
2020-07-08 7:50 ` Dan Williams
2020-07-08 7:50 ` Dan Williams
2020-07-08 7:50 ` Dan Williams
2020-07-08 8:26 ` David Hildenbrand
2020-07-08 8:26 ` David Hildenbrand
2020-07-08 8:26 ` David Hildenbrand
2020-07-08 8:39 ` Mike Rapoport
2020-07-08 8:39 ` Mike Rapoport
2020-07-08 8:39 ` Mike Rapoport
2020-07-08 8:45 ` David Hildenbrand
2020-07-08 8:45 ` David Hildenbrand
2020-07-08 8:45 ` David Hildenbrand
2020-07-08 9:15 ` Mike Rapoport
2020-07-08 9:15 ` Mike Rapoport
2020-07-08 9:15 ` Mike Rapoport
2020-07-08 9:25 ` David Hildenbrand
2020-07-08 9:25 ` David Hildenbrand
2020-07-08 9:25 ` David Hildenbrand
2020-07-08 9:45 ` Mike Rapoport
2020-07-08 9:45 ` Mike Rapoport
2020-07-08 9:45 ` Mike Rapoport
2020-07-08 10:04 ` David Hildenbrand
2020-07-08 10:04 ` David Hildenbrand
2020-07-08 10:04 ` David Hildenbrand
2020-07-08 15:50 ` Dan Williams
2020-07-08 15:50 ` Dan Williams
2020-07-08 15:50 ` Dan Williams
2020-07-08 15:50 ` Dan Williams
2020-07-08 16:10 ` David Hildenbrand
2020-07-08 16:10 ` David Hildenbrand
2020-07-08 16:10 ` David Hildenbrand
2020-07-08 16:47 ` Mike Rapoport
2020-07-08 16:47 ` Mike Rapoport
2020-07-08 16:47 ` Mike Rapoport
2020-07-08 2:20 ` Justin He
2020-07-08 2:20 ` Justin He
2020-07-08 2:20 ` Justin He
2020-07-08 2:20 ` Justin He
2020-07-08 3:56 ` Dan Williams
2020-07-08 3:56 ` Dan Williams
2020-07-08 3:56 ` Dan Williams
2020-07-08 3:56 ` Dan Williams
2020-07-08 4:08 ` Justin He
2020-07-08 4:08 ` Justin He
2020-07-08 4:08 ` Justin He
2020-07-08 4:08 ` Justin He
2020-07-08 4:27 ` Dan Williams
2020-07-08 4:27 ` Dan Williams
2020-07-08 4:27 ` Dan Williams
2020-07-08 4:27 ` Dan Williams
2020-07-08 6:22 ` Mike Rapoport
2020-07-08 6:22 ` Mike Rapoport
2020-07-08 6:22 ` Mike Rapoport
2020-07-08 6:22 ` Mike Rapoport
2020-07-08 6:53 ` Dan Williams
2020-07-08 6:53 ` Dan Williams
2020-07-08 6:53 ` Dan Williams
2020-07-08 6:53 ` Dan Williams
2020-07-08 6:59 ` David Hildenbrand
2020-07-08 6:59 ` David Hildenbrand
2020-07-08 6:59 ` David Hildenbrand
2020-07-08 6:59 ` David Hildenbrand
2020-07-08 7:04 ` Dan Williams
2020-07-08 7:04 ` Dan Williams
2020-07-08 7:04 ` Dan Williams
2020-07-08 7:04 ` Dan Williams
2020-07-08 7:16 ` David Hildenbrand
2020-07-08 7:16 ` David Hildenbrand
2020-07-08 7:16 ` David Hildenbrand
2020-07-08 7:16 ` David Hildenbrand
2020-07-08 7:43 ` Mike Rapoport
2020-07-08 7:43 ` Mike Rapoport
2020-07-08 7:43 ` Mike Rapoport
2020-07-08 7:43 ` Mike Rapoport
2020-07-08 5:32 ` Mike Rapoport
2020-07-08 5:32 ` Mike Rapoport
2020-07-08 5:32 ` Mike Rapoport
2020-07-08 5:32 ` Mike Rapoport
2020-07-08 5:48 ` Dan Williams
2020-07-08 5:48 ` Dan Williams
2020-07-08 5:48 ` Dan Williams
2020-07-08 5:48 ` Dan Williams
2020-07-08 6:19 ` Mike Rapoport
2020-07-08 6:19 ` Mike Rapoport
2020-07-08 6:19 ` Mike Rapoport
2020-07-08 6:19 ` Mike Rapoport
2020-07-08 6:44 ` Dan Williams [this message]
2020-07-08 6:44 ` Dan Williams
2020-07-08 6:44 ` Dan Williams
2020-07-08 6:44 ` Dan Williams
2020-07-08 6:56 ` Justin He
2020-07-08 6:56 ` Justin He
2020-07-08 6:56 ` Justin He
2020-07-08 6:56 ` Justin He
2020-07-08 7:00 ` David Hildenbrand
2020-07-08 7:00 ` David Hildenbrand
2020-07-08 7:00 ` David Hildenbrand
2020-07-08 7:00 ` David Hildenbrand
2020-07-07 5:59 ` [RFC PATCH v2 2/3] device-dax: use fallback nid when numa_node is invalid Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 6:08 ` Justin He
2020-07-07 6:08 ` Justin He
2020-07-07 6:08 ` Justin He
2020-07-07 6:08 ` Justin He
2020-07-07 11:34 ` David Hildenbrand
2020-07-07 11:34 ` David Hildenbrand
2020-07-07 11:34 ` David Hildenbrand
2020-07-08 1:41 ` Justin He
2020-07-08 1:41 ` Justin He
2020-07-08 1:41 ` Justin He
2020-07-08 1:41 ` Justin He
2020-07-07 13:53 ` kernel test robot
2020-07-08 7:07 ` kernel test robot
2020-07-07 5:59 ` [PATCH v2 3/3] mm/memory_hotplug: fix unpaired mem_hotplug_begin/done Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 5:59 ` Jia He
2020-07-07 10:06 ` Michal Hocko
2020-07-07 10:06 ` Michal Hocko
2020-07-07 10:06 ` Michal Hocko
2020-07-07 11:31 ` David Hildenbrand
2020-07-07 11:31 ` David Hildenbrand
2020-07-07 11:31 ` David Hildenbrand
2020-07-10 14:02 ` Sasha Levin
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='CAPcyv4j-vs5pJhr=e3PbuydSfxiEdj_Z5TAvui+pvu28SmgiEA@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=Catalin.Marinas@arm.com \
--cc=Justin.He@arm.com \
--cc=Kaly.Xin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=david@redhat.com \
--cc=hslester96@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=will@kernel.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.