Re: [PATCH 2/2] docs/core-api: memory-hotplug: add some details about locking internals

2018-10-11 Thread David Hildenbrand
On 11/10/2018 06:58, Mike Rapoport wrote: > From: David Hildenbrand > > 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. > > [ rppt: moved the text

Re: [PATCH 2/2] docs/core-api: memory-hotplug: add some details about locking internals

2018-10-11 Thread David Hildenbrand
On 11/10/2018 06:58, Mike Rapoport wrote: > From: David Hildenbrand > > 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. > > [ rppt: moved the text

[PATCH 2/2] docs/core-api: memory-hotplug: add some details about locking internals

2018-10-10 Thread Mike Rapoport
From: David Hildenbrand 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. [ rppt: moved the text to Documentation/core-api/memory-hotplug.rst ] Link:

[PATCH 2/2] docs/core-api: memory-hotplug: add some details about locking internals

2018-10-10 Thread Mike Rapoport
From: David Hildenbrand 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. [ rppt: moved the text to Documentation/core-api/memory-hotplug.rst ] Link: