From: Pasha Tatashin <Pavel.Tatashin@microsoft.com>
To: David Hildenbrand <david@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Michal Hocko <mhocko@suse.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH RFCv2 6/6] memory-hotplug.txt: Add some details about locking internals
Date: Thu, 30 Aug 2018 19:38:43 +0000 [thread overview]
Message-ID: <b46f358b-8fea-b380-1978-5f3e772130d4@microsoft.com> (raw)
In-Reply-To: <20180821104418.12710-7-david@redhat.com>
Reviewed-by: Pavel Tatashin <pavel.tatashin@microsoft.com>
On 8/21/18 6:44 AM, David Hildenbrand wrote:
> Let's document the magic a bit, especially why device_hotplug_lock is
> required when adding/removing memory and how it all play together with
> requests to online/offline memory from user space.
>
WARNING: multiple messages have this Message-ID (diff)
From: Pasha Tatashin <Pavel.Tatashin@microsoft.com>
To: David Hildenbrand <david@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Jonathan Corbet <corbet@lwn.net>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFCv2 6/6] memory-hotplug.txt: Add some details about locking internals
Date: Thu, 30 Aug 2018 19:38:43 +0000 [thread overview]
Message-ID: <b46f358b-8fea-b380-1978-5f3e772130d4@microsoft.com> (raw)
In-Reply-To: <20180821104418.12710-7-david@redhat.com>
Reviewed-by: Pavel Tatashin <pavel.tatashin@microsoft.com>
On 8/21/18 6:44 AM, David Hildenbrand wrote:
> Let's document the magic a bit, especially why device_hotplug_lock is
> required when adding/removing memory and how it all play together with
> requests to online/offline memory from user space.
>
WARNING: multiple messages have this Message-ID (diff)
From: Pasha Tatashin <Pavel.Tatashin@microsoft.com>
To: David Hildenbrand <david@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Jonathan Corbet <corbet@lwn.net>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFCv2 6/6] memory-hotplug.txt: Add some details about locking internals
Date: Thu, 30 Aug 2018 19:38:43 +0000 [thread overview]
Message-ID: <b46f358b-8fea-b380-1978-5f3e772130d4@microsoft.com> (raw)
In-Reply-To: <20180821104418.12710-7-david@redhat.com>
DQpSZXZpZXdlZC1ieTogUGF2ZWwgVGF0YXNoaW4gPHBhdmVsLnRhdGFzaGluQG1pY3Jvc29mdC5j
b20+DQoNCk9uIDgvMjEvMTggNjo0NCBBTSwgRGF2aWQgSGlsZGVuYnJhbmQgd3JvdGU6DQo+IExl
dCdzIGRvY3VtZW50IHRoZSBtYWdpYyBhIGJpdCwgZXNwZWNpYWxseSB3aHkgZGV2aWNlX2hvdHBs
dWdfbG9jayBpcw0KPiByZXF1aXJlZCB3aGVuIGFkZGluZy9yZW1vdmluZyBtZW1vcnkgYW5kIGhv
dyBpdCBhbGwgcGxheSB0b2dldGhlciB3aXRoDQo+IHJlcXVlc3RzIHRvIG9ubGluZS9vZmZsaW5l
IG1lbW9yeSBmcm9tIHVzZXIgc3BhY2UuDQo+IA==
next prev parent reply other threads:[~2018-08-30 19:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 10:44 [PATCH RFCv2 0/6] mm: online/offline_pages called w.o. mem_hotplug_lock David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-21 10:44 ` [PATCH RFCv2 1/6] mm/memory_hotplug: make remove_memory() take the device_hotplug_lock David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 19:35 ` Pasha Tatashin
2018-08-30 19:35 ` Pasha Tatashin
2018-08-30 19:35 ` Pasha Tatashin
2018-08-30 19:35 ` Pasha Tatashin
2018-08-31 13:12 ` David Hildenbrand
2018-08-31 13:12 ` David Hildenbrand
2018-08-31 13:12 ` David Hildenbrand
2018-08-21 10:44 ` [PATCH RFCv2 2/6] mm/memory_hotplug: make add_memory() " David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 19:36 ` Pasha Tatashin
2018-08-30 19:36 ` Pasha Tatashin
2018-08-30 19:36 ` Pasha Tatashin
2018-08-30 19:36 ` Pasha Tatashin
2018-08-21 10:44 ` David Hildenbrand
2018-08-21 10:44 ` [PATCH RFCv2 3/6] mm/memory_hotplug: fix online/offline_pages called w.o. mem_hotplug_lock David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 19:37 ` Pasha Tatashin
2018-08-30 19:37 ` Pasha Tatashin
2018-08-30 19:37 ` Pasha Tatashin
2018-08-30 19:37 ` Pasha Tatashin
2018-09-03 0:36 ` Rashmica
2018-09-03 0:36 ` Rashmica
2018-09-17 7:32 ` David Hildenbrand
2018-09-17 7:32 ` David Hildenbrand
2018-09-17 7:32 ` David Hildenbrand
2018-09-25 1:26 ` Rashmica Gupta
2018-09-25 1:26 ` Rashmica Gupta
2018-09-25 1:26 ` Rashmica Gupta
2018-08-21 10:44 ` David Hildenbrand
2018-08-21 10:44 ` [PATCH RFCv2 4/6] powerpc/powernv: hold device_hotplug_lock when calling device_online() David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin
2018-08-21 10:44 ` [PATCH RFCv2 5/6] powerpc/powernv: hold device_hotplug_lock in memtrace_offline_pages() David Hildenbrand
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin
2018-08-21 10:44 ` [PATCH RFCv2 6/6] memory-hotplug.txt: Add some details about locking internals David Hildenbrand
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin [this message]
2018-08-30 19:38 ` Pasha Tatashin
2018-08-30 19:38 ` Pasha Tatashin
2018-08-21 10:44 ` David Hildenbrand
2018-08-30 12:31 ` [PATCH RFCv2 0/6] mm: online/offline_pages called w.o. mem_hotplug_lock David Hildenbrand
2018-08-30 12:31 ` David Hildenbrand
2018-08-30 15:54 ` Pasha Tatashin
2018-08-30 15:54 ` Pasha Tatashin
2018-08-30 15:54 ` Pasha Tatashin
2018-08-30 15:54 ` Pasha Tatashin
2018-08-30 12:31 ` David Hildenbrand
2018-08-31 20:54 ` Oscar Salvador
2018-08-31 20:54 ` Oscar Salvador
2018-08-31 20:54 ` Oscar Salvador
2018-09-01 14:03 ` David Hildenbrand
2018-09-01 14:03 ` David Hildenbrand
2018-09-01 14:03 ` 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=b46f358b-8fea-b380-1978-5f3e772130d4@microsoft.com \
--to=pavel.tatashin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=xen-devel@lists.xenproject.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.