Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

On Thu, 28 Mar 2019 23:50:09 PDT (-0700), a...@brainfault.org wrote: Hi Palmer, On Fri, Mar 29, 2019 at 11:48 AM Palmer Dabbelt wrote: On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote: > Looks good, > > Reviewed-by: Christoph Hellwig Thanks. I've added this to my fixes

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

Hi Palmer, On Fri, Mar 29, 2019 at 11:48 AM Palmer Dabbelt wrote: > > On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote: > > Looks good, > > > > Reviewed-by: Christoph Hellwig > > Thanks. I've added this to my fixes list for the next RC. I have another RC fix as well: "[PATCH

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote: Looks good, Reviewed-by: Christoph Hellwig Thanks. I've added this to my fixes list for the next RC. Btw, what is the 32-bit test vehicle of choice? qemu with the virt machine?

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

On Fri, Mar 22, 2019 at 6:55 PM Christoph Hellwig wrote: > > Looks good, > > Reviewed-by: Christoph Hellwig > > Btw, what is the 32-bit test vehicle of choice? qemu with the > virt machine? Yes, for now QEMU seems to be only the option. I am not aware of any board we can purchase for RV32.

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

Looks good, Reviewed-by: Christoph Hellwig Btw, what is the 32-bit test vehicle of choice? qemu with the virt machine?

[PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

The FIXMAP area overlaps with VMALLOC area in Linux-5.1-rc1 hence we get below warning in Linux RISC-V 32bit kernel. This warning does not show-up in Linux RISC-V 64bit kernel due to large VMALLOC area. WARNING: CPU: 0 PID: 22 at mm/vmalloc.c:150 vmap_page_range_noflush+0x134/0x15c Modules linked