Re: [PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

2019-04-07 Thread Anup Patel
On Sat, Apr 6, 2019 at 2:47 AM Palmer Dabbelt wrote: > > On Thu, 04 Apr 2019 23:01:11 PDT (-0700), a...@brainfault.org wrote: > > On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig > > wrote: > >> > >> On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote: > >> > The Maximum Physical Memory

Re: [PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

2019-04-05 Thread Palmer Dabbelt
On Thu, 04 Apr 2019 23:01:11 PDT (-0700), a...@brainfault.org wrote: On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote: On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote: > The Maximum Physical Memory 2GiB option for 64bit systems is currently > broken because kernel hangs at bo

Re: [PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

2019-04-04 Thread Anup Patel
On Fri, Apr 5, 2019 at 11:24 AM Christoph Hellwig wrote: > > On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote: > > The Maximum Physical Memory 2GiB option for 64bit systems is currently > > broken because kernel hangs at boot-time when this option is enabled > > and the underlying system

Re: [PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB option for 64bit systems

2019-04-04 Thread Christoph Hellwig
On Fri, Apr 05, 2019 at 05:49:34AM +, Anup Patel wrote: > The Maximum Physical Memory 2GiB option for 64bit systems is currently > broken because kernel hangs at boot-time when this option is enabled > and the underlying system has more than 2GiB memory. > > This issue can be easily reproduced