All of lore.kernel.org
 help / color / mirror / Atom feed
From: osalvador <osalvador@suse.com>
To: David Hildenbrand <david@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: Linux MM <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Linux-sh <linux-sh@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>, Qian Cai <cai@lca.pw>,
	Arun KS <arunks@codeaurora.org>,
	Mathieu Malaterre <malat@debian.org>
Subject: Re: [PATCH v2 5/8] mm/memory_hotplug: Drop MHP_MEMBLOCK_API
Date: Wed, 08 May 2019 23:08:58 +0000	[thread overview]
Message-ID: <1557356938.3028.35.camel@suse.com> (raw)
In-Reply-To: <edd762a1-c012-fe05-a72e-2505cd98188a@redhat.com>

On Wed, 2019-05-08 at 09:39 +0200, David Hildenbrand wrote:
> However I haven't really thought it through yet, smalles like that
> could
> as well just be handled by the caller of
> arch_add_memory()/arch_remove_memory() eventually, passing it via
> something like the altmap parameter.
> 
> Let's leave it in place for now, we can talk about that once we have
> new
> patches from Oscar.
Hi David,

I plan to send a new patchset once this is and Dan's are merged,
otherwise I will have a mayhem with the conflicts.

I also plan/want to review this patchset, but time is tight this week.

WARNING: multiple messages have this Message-ID (diff)
From: osalvador <osalvador@suse.com>
To: David Hildenbrand <david@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: Linux MM <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ia64@vger.kernel.org,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-s390 <linux-s390@vger.kernel.org>,
	Linux-sh <linux-sh@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>, Qian Cai <cai@lca.pw>,
	Arun KS <arunks@codeaurora.org>,
	Mathieu Malaterre <malat@debian.org>
Subject: Re: [PATCH v2 5/8] mm/memory_hotplug: Drop MHP_MEMBLOCK_API
Date: Thu, 09 May 2019 01:08:58 +0200	[thread overview]
Message-ID: <1557356938.3028.35.camel@suse.com> (raw)
In-Reply-To: <edd762a1-c012-fe05-a72e-2505cd98188a@redhat.com>

On Wed, 2019-05-08 at 09:39 +0200, David Hildenbrand wrote:
> However I haven't really thought it through yet, smalles like that
> could
> as well just be handled by the caller of
> arch_add_memory()/arch_remove_memory() eventually, passing it via
> something like the altmap parameter.
> 
> Let's leave it in place for now, we can talk about that once we have
> new
> patches from Oscar.
Hi David,

I plan to send a new patchset once this is and Dan's are merged,
otherwise I will have a mayhem with the conflicts.

I also plan/want to review this patchset, but time is tight this week.

WARNING: multiple messages have this Message-ID (diff)
From: osalvador <osalvador@suse.com>
To: David Hildenbrand <david@redhat.com>,
	Dan Williams <dan.j.williams@intel.com>
Cc: linux-s390 <linux-s390@vger.kernel.org>,
	Michal Hocko <mhocko@suse.com>,
	linux-ia64@vger.kernel.org,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Linux-sh <linux-sh@vger.kernel.org>,
	Mathieu Malaterre <malat@debian.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Wei Yang <richard.weiyang@gmail.com>,
	Linux MM <linux-mm@kvack.org>, Qian Cai <cai@lca.pw>,
	Arun KS <arunks@codeaurora.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH v2 5/8] mm/memory_hotplug: Drop MHP_MEMBLOCK_API
Date: Thu, 09 May 2019 01:08:58 +0200	[thread overview]
Message-ID: <1557356938.3028.35.camel@suse.com> (raw)
In-Reply-To: <edd762a1-c012-fe05-a72e-2505cd98188a@redhat.com>

On Wed, 2019-05-08 at 09:39 +0200, David Hildenbrand wrote:
> However I haven't really thought it through yet, smalles like that
> could
> as well just be handled by the caller of
> arch_add_memory()/arch_remove_memory() eventually, passing it via
> something like the altmap parameter.
> 
> Let's leave it in place for now, we can talk about that once we have
> new
> patches from Oscar.
Hi David,

I plan to send a new patchset once this is and Dan's are merged,
otherwise I will have a mayhem with the conflicts.

I also plan/want to review this patchset, but time is tight this week.


  reply	other threads:[~2019-05-08 23:08 UTC|newest]

Thread overview: 125+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 18:37 [PATCH v2 0/8] mm/memory_hotplug: Factor out memory block device handling David Hildenbrand
2019-05-07 18:37 ` David Hildenbrand
2019-05-07 18:37 ` [PATCH v2 1/8] mm/memory_hotplug: Simplify and fix check_hotplug_memory_range() David Hildenbrand
2019-05-07 18:37   ` David Hildenbrand
2019-05-07 18:37   ` David Hildenbrand
2019-05-07 20:38   ` Dan Williams
2019-05-07 20:38     ` Dan Williams
2019-05-07 20:38     ` Dan Williams
2019-05-09 12:23   ` Wei Yang
2019-05-09 12:23     ` Wei Yang
2019-05-09 12:23     ` Wei Yang
2019-05-07 18:37 ` [PATCH v2 2/8] s390x/mm: Implement arch_remove_memory() David Hildenbrand
2019-05-07 18:37   ` David Hildenbrand
2019-05-07 18:37   ` David Hildenbrand
2019-05-07 20:46   ` Dan Williams
2019-05-07 20:46     ` Dan Williams
2019-05-07 20:46     ` Dan Williams
2019-05-07 20:47     ` David Hildenbrand
2019-05-07 20:47       ` David Hildenbrand
2019-05-07 20:47       ` David Hildenbrand
2019-05-07 20:57       ` Dan Williams
2019-05-07 20:57         ` Dan Williams
2019-05-07 20:57         ` Dan Williams
2019-05-07 21:13         ` David Hildenbrand
2019-05-07 21:13           ` David Hildenbrand
2019-05-07 21:13           ` David Hildenbrand
2019-05-07 18:37 ` [PATCH v2 3/8] mm/memory_hotplug: arch_remove_memory() and __remove_pages() with CONFIG_MEMORY_HOTPLUG David Hildenbrand
2019-05-07 18:37   ` David Hildenbrand
2019-05-07 21:02   ` Dan Williams
2019-05-07 21:02     ` Dan Williams
2019-05-07 21:06     ` David Hildenbrand
2019-05-07 21:06       ` David Hildenbrand
2019-05-13  7:48     ` David Hildenbrand
2019-05-13  7:48       ` David Hildenbrand
2019-05-13  8:20       ` David Hildenbrand
2019-05-13  8:20         ` David Hildenbrand
2019-05-07 18:38 ` [PATCH v2 4/8] mm/memory_hotplug: Create memory block devices after arch_add_memory() David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 21:17   ` Dan Williams
2019-05-07 21:17     ` Dan Williams
2019-05-07 21:17     ` Dan Williams
2019-05-07 21:27     ` David Hildenbrand
2019-05-07 21:27       ` David Hildenbrand
2019-05-07 21:27       ` David Hildenbrand
2019-05-08  8:35   ` David Hildenbrand
2019-05-08  8:35     ` David Hildenbrand
2019-05-08  8:35     ` David Hildenbrand
2019-05-09 12:43   ` Wei Yang
2019-05-09 12:43     ` Wei Yang
2019-05-09 12:43     ` Wei Yang
2019-05-09 12:50     ` David Hildenbrand
2019-05-09 12:50       ` David Hildenbrand
2019-05-09 12:50       ` David Hildenbrand
2019-05-09 13:55   ` Wei Yang
2019-05-09 13:55     ` Wei Yang
2019-05-09 13:55     ` Wei Yang
2019-05-09 14:05     ` David Hildenbrand
2019-05-09 14:05       ` David Hildenbrand
2019-05-09 14:05       ` David Hildenbrand
2019-05-09 14:31   ` Wei Yang
2019-05-09 14:31     ` Wei Yang
2019-05-09 14:31     ` Wei Yang
2019-05-09 14:58     ` David Hildenbrand
2019-05-09 14:58       ` David Hildenbrand
2019-05-09 14:58       ` David Hildenbrand
2019-05-09 21:50       ` Wei Yang
2019-05-09 21:50         ` Wei Yang
2019-05-09 21:50         ` Wei Yang
2019-05-09 22:18         ` David Hildenbrand
2019-05-09 22:18           ` David Hildenbrand
2019-05-09 22:18           ` David Hildenbrand
2019-05-07 18:38 ` [PATCH v2 5/8] mm/memory_hotplug: Drop MHP_MEMBLOCK_API David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 21:19   ` Dan Williams
2019-05-07 21:19     ` Dan Williams
2019-05-07 21:19     ` Dan Williams
2019-05-07 21:24     ` David Hildenbrand
2019-05-07 21:24       ` David Hildenbrand
2019-05-07 21:24       ` David Hildenbrand
2019-05-07 21:25       ` Dan Williams
2019-05-07 21:25         ` Dan Williams
2019-05-07 21:25         ` Dan Williams
2019-05-08  7:39         ` David Hildenbrand
2019-05-08  7:39           ` David Hildenbrand
2019-05-08  7:39           ` David Hildenbrand
2019-05-08 23:08           ` osalvador [this message]
2019-05-08 23:08             ` osalvador
2019-05-08 23:08             ` osalvador
2019-05-09  7:05             ` David Hildenbrand
2019-05-09  7:05               ` David Hildenbrand
2019-05-09  7:05               ` David Hildenbrand
2019-05-07 18:38 ` [PATCH v2 6/8] mm/memory_hotplug: Remove memory block devices before arch_remove_memory() David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 21:27   ` Dan Williams
2019-05-07 21:27     ` Dan Williams
2019-05-07 21:27     ` Dan Williams
2019-05-07 18:38 ` [PATCH v2 7/8] mm/memory_hotplug: Make unregister_memory_block_under_nodes() never fail David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-08  0:15   ` Dan Williams
2019-05-08  0:15     ` Dan Williams
2019-05-08  0:15     ` Dan Williams
2019-05-08  7:21     ` David Hildenbrand
2019-05-08  7:21       ` David Hildenbrand
2019-05-08  7:21       ` David Hildenbrand
2019-05-08 13:50       ` Dan Williams
2019-05-08 13:50         ` Dan Williams
2019-05-08 13:50         ` Dan Williams
2019-05-07 18:38 ` [PATCH v2 8/8] mm/memory_hotplug: Remove "zone" parameter from sparse_remove_one_section David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-07 18:38   ` David Hildenbrand
2019-05-08  0:30   ` Dan Williams
2019-05-08  0:30     ` Dan Williams
2019-05-08  0:30     ` Dan Williams
2019-05-07 19:04 ` [PATCH v2 0/8] mm/memory_hotplug: Factor out memory block device handling Dan Williams
2019-05-07 19:04   ` Dan Williams
2019-05-07 19:21   ` David Hildenbrand
2019-05-07 19:21     ` David Hildenbrand
2019-05-07 19:37     ` David Hildenbrand
2019-05-07 19:37       ` David Hildenbrand
2019-05-07 20:36       ` Dan Williams
2019-05-07 20:36         ` Dan Williams

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=1557356938.3028.35.camel@suse.com \
    --to=osalvador@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=arunks@codeaurora.org \
    --cc=cai@lca.pw \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=malat@debian.org \
    --cc=mhocko@suse.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=richard.weiyang@gmail.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.