Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-11-03 Thread Mike Rapoport
On Mon, Nov 02, 2020 at 06:51:25PM -0800, Sudarshan Rajagopalan wrote: > On 2020-10-30 01:38, Mike Rapoport wrote: > > On Thu, Oct 29, 2020 at 02:29:27PM -0700, Sudarshan Rajagopalan wrote: > > > Hello all, > > > > > > We have a usecase where a module driver adds certain memory blocks > > > using

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-11-03 Thread Sudarshan Rajagopalan
On 2020-10-30 01:38, Mike Rapoport wrote: On Thu, Oct 29, 2020 at 02:29:27PM -0700, Sudarshan Rajagopalan wrote: Hello all, We have a usecase where a module driver adds certain memory blocks using add_memory_driver_managed(), so that it can perform memory hotplug operations on these blocks. I

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-11-03 Thread Sudarshan Rajagopalan
On 2020-10-29 23:41, David Hildenbrand wrote: On 29.10.20 22:29, Sudarshan Rajagopalan wrote: Hello all, Hi! Hi David.. thanks for the response as always. We have a usecase where a module driver adds certain memory blocks using add_memory_driver_managed(), so that it can perform memory

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-11-03 Thread Christoph Hellwig
On Sat, Oct 31, 2020 at 11:05:45AM +0100, David Hildenbrand wrote: > On 31.10.20 10:18, Christoph Hellwig wrote: > > On Fri, Oct 30, 2020 at 10:38:42AM +0200, Mike Rapoport wrote: > > > What do you mean by "system memory block"? There could be a lot of > > > interpretations if you take into account

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-10-31 Thread David Hildenbrand
On 31.10.20 10:18, Christoph Hellwig wrote: On Fri, Oct 30, 2020 at 10:38:42AM +0200, Mike Rapoport wrote: What do you mean by "system memory block"? There could be a lot of interpretations if you take into account memory hotplug, "mem=" option, reserved and firmware memory. I'd suggest you

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-10-31 Thread Christoph Hellwig
On Fri, Oct 30, 2020 at 10:38:42AM +0200, Mike Rapoport wrote: > > What do you mean by "system memory block"? There could be a lot of > interpretations if you take into account memory hotplug, "mem=" option, > reserved and firmware memory. > > I'd suggest you to describe the entire use case in m

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-10-30 Thread Mike Rapoport
On Thu, Oct 29, 2020 at 02:29:27PM -0700, Sudarshan Rajagopalan wrote: > Hello all, > > We have a usecase where a module driver adds certain memory blocks using > add_memory_driver_managed(), so that it can perform memory hotplug > operations on these blocks. In general, these memory blocks aren’t

Re: mm/memblock: export memblock_{start/end}_of_DRAM

2020-10-29 Thread David Hildenbrand
On 29.10.20 22:29, Sudarshan Rajagopalan wrote: Hello all, Hi! We have a usecase where a module driver adds certain memory blocks using add_memory_driver_managed(), so that it can perform memory hotplug operations on these blocks. In general, these memory blocks aren’t something that gets ph

mm/memblock: export memblock_{start/end}_of_DRAM

2020-10-29 Thread Sudarshan Rajagopalan
Hello all, We have a usecase where a module driver adds certain memory blocks using add_memory_driver_managed(), so that it can perform memory hotplug operations on these blocks. In general, these memory blocks aren’t something that gets physically added later, but is part of actual RAM that