Re: [PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-28 Thread Paul Walmsley
On Tue, 27 Aug 2019, Anup Patel wrote: > On Tue, Aug 27, 2019 at 5:43 AM Paul Walmsley > wrote: > > > > On Mon, 19 Aug 2019, Anup Patel wrote: > > > > > Currently, various virtual memory areas of Linux RISC-V are organized > > > in increasing order of their virtual addresses is as follows: > >

Re: [PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-28 Thread Alistair Francis
On Tue, 2019-08-27 at 08:11 +0530, Anup Patel wrote: > On Tue, Aug 27, 2019 at 5:43 AM Paul Walmsley < > paul.walms...@sifive.com> wrote: > > Hello Anup, > > > > On Mon, 19 Aug 2019, Anup Patel wrote: > > > > > Currently, various virtual memory areas of Linux RISC-V are > > > organized > > > in

Re: [PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-26 Thread Anup Patel
On Tue, Aug 27, 2019 at 5:43 AM Paul Walmsley wrote: > > Hello Anup, > > On Mon, 19 Aug 2019, Anup Patel wrote: > > > Currently, various virtual memory areas of Linux RISC-V are organized > > in increasing order of their virtual addresses is as follows: > > 1. User space area (This is lowest area

Re: [PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-26 Thread Paul Walmsley
Hello Anup, On Mon, 19 Aug 2019, Anup Patel wrote: > Currently, various virtual memory areas of Linux RISC-V are organized > in increasing order of their virtual addresses is as follows: > 1. User space area (This is lowest area and starts at 0x0) > 2. FIXMAP area > 3. VMALLOC area > 4. Kernel

Re: [PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-26 Thread Christoph Hellwig
Palmer, Paul - are you going to pick this up? Seems like we've just missed -rc6.

[PATCH v2] RISC-V: Fix FIXMAP area corruption on RV32 systems

2019-08-18 Thread Anup Patel
Currently, various virtual memory areas of Linux RISC-V are organized in increasing order of their virtual addresses is as follows: 1. User space area (This is lowest area and starts at 0x0) 2. FIXMAP area 3. VMALLOC area 4. Kernel area (This is highest area and starts at PAGE_OFFSET) The maximum