From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Oscar Salvador <osalvador@suse.com>,
Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Dan Williams <dan.j.williams@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-s390@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Michael Ellerman <mpe@ellerman.id.au>,
x86@kernel.org, Matthew Wilcox <willy@infradead.org>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
xen-devel@lists.xenproject.org, Rob Herring <robh@kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH RFCv2 2/4] mm/memory_hotplug: Replace "bool want_memblock" by "int type"
Date: Mon, 3 Dec 2018 11:33:12 +0100 [thread overview]
Message-ID: <5ecbff41-fc41-79fc-696e-4ca1f066f9aa__39723.1789342642$1543833130$gmane$org@redhat.com> (raw)
In-Reply-To: <20181201015024.3o334nk2fe5mlasj@master>
On 01.12.18 02:50, Wei Yang wrote:
> On Fri, Nov 30, 2018 at 06:59:20PM +0100, David Hildenbrand wrote:
>> Let's pass a memory block type instead. Pass "MEMORY_BLOCK_NONE" for device
>> memory and for now "MEMORY_BLOCK_UNSPECIFIED" for anything else. No
>> functional change.
>
> I would suggest to put more words to this.
Sure, makes sense, I'll add more details. Thanks!
>
> "
> Function arch_add_memory()'s last parameter *want_memblock* is used to
> determin whether it is necessary to create a corresponding memory block
> device. After introducing the memory block type, this patch replaces the
> bool type *want_memblock* with memory block type with following rules
> for now:
>
> * Pass "MEMORY_BLOCK_NONE" for device memory
> * Pass "MEMORY_BLOCK_UNSPECIFIED" for anything else
>
> Since this parameter is passed deep to __add_section(), all its
> descendents are effected. Below lists those descendents.
>
> arch_add_memory()
> add_pages()
> __add_pages()
> __add_section()
>
> "
[...]
--
Thanks,
David / dhildenb
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-03 10:33 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:59 [PATCH RFCv2 0/4] mm/memory_hotplug: Introduce memory block types David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` [PATCH RFCv2 1/4] " David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-12-01 1:25 ` Wei Yang
2018-12-01 1:25 ` Wei Yang
2018-12-01 1:25 ` Wei Yang
2018-12-01 1:25 ` Wei Yang
2018-12-01 1:25 ` Wei Yang
2018-12-03 10:32 ` David Hildenbrand
2018-12-03 10:32 ` David Hildenbrand
2018-12-03 10:32 ` David Hildenbrand
2018-12-03 10:32 ` David Hildenbrand
2018-12-03 10:32 ` David Hildenbrand
2018-12-03 20:58 ` Wei Yang
2018-12-03 20:58 ` Wei Yang
2018-12-03 20:58 ` Wei Yang
2018-12-03 20:58 ` Wei Yang
2018-12-03 20:58 ` Wei Yang
2018-12-03 20:58 ` Wei Yang
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` [PATCH RFCv2 2/4] mm/memory_hotplug: Replace "bool want_memblock" by "int type" David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-12-01 1:50 ` Wei Yang
2018-12-01 1:50 ` Wei Yang
2018-12-01 1:50 ` Wei Yang
2018-12-01 1:50 ` Wei Yang
2018-12-03 10:33 ` David Hildenbrand
2018-12-03 10:33 ` David Hildenbrand
2018-12-03 10:33 ` David Hildenbrand
2018-12-03 10:33 ` David Hildenbrand [this message]
2018-11-30 17:59 ` [PATCH RFCv2 3/4] mm/memory_hotplug: Introduce and use more memory types David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-12-04 9:44 ` Michal Suchánek
2018-12-04 9:44 ` Michal Suchánek
2018-12-04 9:44 ` Michal Suchánek
2018-12-04 9:44 ` Michal Suchánek
2018-12-04 9:44 ` Michal Suchánek
2018-12-04 9:47 ` David Hildenbrand
2018-12-04 9:47 ` David Hildenbrand
2018-12-04 9:47 ` David Hildenbrand
2018-12-04 9:47 ` David Hildenbrand
2018-12-04 9:47 ` David Hildenbrand
2018-11-30 17:59 ` [PATCH RFCv2 4/4] mm/memory_hotplug: Drop MEMORY_TYPE_UNSPECIFIED David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-11-30 17:59 ` David Hildenbrand
2018-12-01 0:48 ` [PATCH RFCv2 0/4] mm/memory_hotplug: Introduce memory block types Wei Yang
2018-12-01 0:48 ` Wei Yang
2018-12-01 0:48 ` Wei Yang
2018-12-01 0:48 ` Wei Yang
2018-12-20 12:58 ` David Hildenbrand
2018-12-20 12:58 ` David Hildenbrand
2018-12-20 12:58 ` David Hildenbrand
2018-12-20 13:08 ` Michal Hocko
2018-12-20 13:08 ` Michal Hocko
2018-12-20 13:08 ` Michal Hocko
2018-12-20 13:08 ` Michal Hocko
2018-12-20 13:16 ` David Hildenbrand
2018-12-20 13:16 ` David Hildenbrand
2018-12-20 13:16 ` David Hildenbrand
2018-12-20 13:16 ` David Hildenbrand
2019-03-27 16:03 ` David Hildenbrand
2019-03-27 16:03 ` David Hildenbrand
2019-03-27 16:03 ` David Hildenbrand
2019-03-27 16:03 ` David Hildenbrand
2018-12-20 12:58 ` David Hildenbrand
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='5ecbff41-fc41-79fc-696e-4ca1f066f9aa__39723.1789342642$1543833130$gmane$org@redhat.com' \
--to=david@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=dalias@libc.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=fenghua.yu@intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=osalvador@suse.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=robh@kernel.org \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=ysato@users.sourceforge.jp \
/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.