Am Fri, 17 Jan 2014 18:08:13 +
schrieb "Strashko, Grygorii" :
Hello Grygorii,
> > The current patch seems to be overly complicated.
> > The following patch contains only the nomap functionality without
> > any cleanup and refactoring. I will post a V4 patch set which will
> > contain this
Am Fri, 17 Jan 2014 18:08:13 +
schrieb Strashko, Grygorii grygorii.stras...@ti.com:
Hello Grygorii,
The current patch seems to be overly complicated.
The following patch contains only the nomap functionality without
any cleanup and refactoring. I will post a V4 patch set which will
Hi Philipp,
On 01/14/2014 08:52 PM, Philipp Hachtmann wrote:
> Hello Grygorii,
>
> thank you for your comments.
>
> To clarify we have the following requirements for memblock:
>
> (1) Reserved areas can be declared before memory is added.
> (2) The physical memory is detected once only.
> (3)
Hi Philipp,
On 01/14/2014 08:52 PM, Philipp Hachtmann wrote:
Hello Grygorii,
thank you for your comments.
To clarify we have the following requirements for memblock:
(1) Reserved areas can be declared before memory is added.
(2) The physical memory is detected once only.
(3) The free
On Tue, 14 Jan 2014 10:42:53 +0100 Philipp Hachtmann
wrote:
> Am Mon, 13 Jan 2014 16:36:20 -0800
> schrieb Andrew Morton :
>
> > Patch is big. I'll toss this in for some testing but it does look too
> > large and late for 3.14. How will this affect your s390 development?
>
> It is needed
Hello Grygorii,
thank you for your comments.
To clarify we have the following requirements for memblock:
(1) Reserved areas can be declared before memory is added.
(2) The physical memory is detected once only.
(3) The free memory (i.e. not reserved) memory can be iterated to add
it to the
On Tuesday 14 January 2014 08:17 AM, Grygorii Strashko wrote:
> Hi Philipp,
>
> On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
>> Add a new memory state "nomap" to memblock. This can be used to truncate
>> the usable memory in the system without forgetting about what is really
>> installed.
>
Hi Philipp,
On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
> Add a new memory state "nomap" to memblock. This can be used to truncate
> the usable memory in the system without forgetting about what is really
> installed.
Sorry, but this solution looks a bit complex (and probably wrong - from
Am Mon, 13 Jan 2014 16:36:20 -0800
schrieb Andrew Morton :
> Patch is big. I'll toss this in for some testing but it does look too
> large and late for 3.14. How will this affect your s390 development?
It is needed for s390 bootmem -> memblock transition. The s390 dump
mechanisms cannot be
Am Mon, 13 Jan 2014 16:36:20 -0800
schrieb Andrew Morton a...@linux-foundation.org:
Patch is big. I'll toss this in for some testing but it does look too
large and late for 3.14. How will this affect your s390 development?
It is needed for s390 bootmem - memblock transition. The s390 dump
Hi Philipp,
On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
Add a new memory state nomap to memblock. This can be used to truncate
the usable memory in the system without forgetting about what is really
installed.
Sorry, but this solution looks a bit complex (and probably wrong - from
On Tuesday 14 January 2014 08:17 AM, Grygorii Strashko wrote:
Hi Philipp,
On 01/13/2014 03:03 PM, Philipp Hachtmann wrote:
Add a new memory state nomap to memblock. This can be used to truncate
the usable memory in the system without forgetting about what is really
installed.
Sorry,
Hello Grygorii,
thank you for your comments.
To clarify we have the following requirements for memblock:
(1) Reserved areas can be declared before memory is added.
(2) The physical memory is detected once only.
(3) The free memory (i.e. not reserved) memory can be iterated to add
it to the
On Tue, 14 Jan 2014 10:42:53 +0100 Philipp Hachtmann
pha...@linux.vnet.ibm.com wrote:
Am Mon, 13 Jan 2014 16:36:20 -0800
schrieb Andrew Morton a...@linux-foundation.org:
Patch is big. I'll toss this in for some testing but it does look too
large and late for 3.14. How will this affect
On Mon, 13 Jan 2014 14:03:37 +0100 Philipp Hachtmann
wrote:
> Add a new memory state "nomap" to memblock. This can be used to truncate
> the usable memory in the system without forgetting about what is really
> installed.
>
> ...
>
> 5 files changed, 254 insertions(+), 70 deletions(-)
Patch
On Mon, 13 Jan 2014 14:03:37 +0100 Philipp Hachtmann
pha...@linux.vnet.ibm.com wrote:
Add a new memory state nomap to memblock. This can be used to truncate
the usable memory in the system without forgetting about what is really
installed.
...
5 files changed, 254 insertions(+), 70
16 matches
Mail list logo
