Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-09-10 Thread Nicolas Pitre
On Mon, 10 Sep 2012, Cyril Chemparathy wrote: > On 8/12/2012 12:36 AM, Nicolas Pitre wrote: > > On Fri, 10 Aug 2012, Cyril Chemparathy wrote: > > > > > On Keystone platforms, physical memory is entirely outside the 32-bit > > > addressible range. Therefore, the (bank->start > ULONG_MAX) check

Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-09-10 Thread Cyril Chemparathy
On 8/12/2012 12:36 AM, Nicolas Pitre wrote: On Fri, 10 Aug 2012, Cyril Chemparathy wrote: On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank->start > ULONG_MAX) check below marks the entire system memory as highmem, and this causes

Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-09-10 Thread Cyril Chemparathy
On 8/12/2012 12:36 AM, Nicolas Pitre wrote: On Fri, 10 Aug 2012, Cyril Chemparathy wrote: On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank-start ULONG_MAX) check below marks the entire system memory as highmem, and this causes

Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-09-10 Thread Nicolas Pitre
On Mon, 10 Sep 2012, Cyril Chemparathy wrote: On 8/12/2012 12:36 AM, Nicolas Pitre wrote: On Fri, 10 Aug 2012, Cyril Chemparathy wrote: On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank-start ULONG_MAX) check below marks

Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-08-11 Thread Nicolas Pitre
On Fri, 10 Aug 2012, Cyril Chemparathy wrote: > On Keystone platforms, physical memory is entirely outside the 32-bit > addressible range. Therefore, the (bank->start > ULONG_MAX) check below marks > the entire system memory as highmem, and this causes unpleasentness all over. > > This patch

Re: [PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-08-11 Thread Nicolas Pitre
On Fri, 10 Aug 2012, Cyril Chemparathy wrote: On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank-start ULONG_MAX) check below marks the entire system memory as highmem, and this causes unpleasentness all over. This patch

[PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-08-10 Thread Cyril Chemparathy
On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank->start > ULONG_MAX) check below marks the entire system memory as highmem, and this causes unpleasentness all over. This patch eliminates the extra bank start check (against ULONG_MAX)

[PATCH v2 16/22] ARM: mm: cleanup checks for membank overlap with vmalloc area

2012-08-10 Thread Cyril Chemparathy
On Keystone platforms, physical memory is entirely outside the 32-bit addressible range. Therefore, the (bank-start ULONG_MAX) check below marks the entire system memory as highmem, and this causes unpleasentness all over. This patch eliminates the extra bank start check (against ULONG_MAX) by