Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-04-10 Thread Nick Kossifidis
Στις 2019-03-13 00:08, Anup Patel έγραψε: Currently, we have to boot RISCV64 kernel from a 2MB aligned physical address and RISCV32 kernel from a 4MB aligned physical address. This constraint is because initial pagetable setup (i.e. setup_vm()) maps entire RAM using hugepages (i.e. 2MB for

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-18 Thread Mike Rapoport
On Mon, Mar 18, 2019 at 06:46:18PM +0530, Anup Patel wrote: > On Mon, Mar 18, 2019 at 12:48 PM Mike Rapoport wrote: > > > > On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote: > > > On Fri, Mar 15, 2019 at 9:52 PM Anup Patel wrote: > > > > > > > > On Fri, Mar 15, 2019 at 9:28 PM Mike

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-18 Thread Paul Walmsley
On Mon, 18 Mar 2019, Mike Rapoport wrote: > On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote: > > > We started exploring ways to re-claim memory below kernel because > > we are trying to get Linux working on Kendryte K210 board > > (https://kendryte.com/). This board has dual-core

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-18 Thread Anup Patel
On Mon, Mar 18, 2019 at 12:48 PM Mike Rapoport wrote: > > On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote: > > On Fri, Mar 15, 2019 at 9:52 PM Anup Patel wrote: > > > > > > On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > > > > > > > I still don't get why it is that important

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-18 Thread Mike Rapoport
On Sat, Mar 16, 2019 at 04:55:30AM +0530, Anup Patel wrote: > On Fri, Mar 15, 2019 at 9:52 PM Anup Patel wrote: > > > > On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > > > > > I still don't get why it is that important to relax alignment of the > > > kernel > > > load address. Provided

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-15 Thread Anup Patel
On Fri, Mar 15, 2019 at 9:52 PM Anup Patel wrote: > > On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > > > On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote: > > > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote: > > > > > > > > On Thu, Mar 14, 2019 at 02:36:01AM +0530,

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-15 Thread Anup Patel
On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote: > > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote: > > > > > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote: > > > > On Thu, Mar 14, 2019 at 12:01 AM Mike

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-15 Thread Anup Patel
On Fri, Mar 15, 2019 at 9:28 PM Mike Rapoport wrote: > > On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote: > > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote: > > > > > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote: > > > > On Thu, Mar 14, 2019 at 12:01 AM Mike

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-15 Thread Mike Rapoport
On Thu, Mar 14, 2019 at 11:28:32PM +0530, Anup Patel wrote: > On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote: > > > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote: > > > On Thu, Mar 14, 2019 at 12:01 AM Mike Rapoport wrote: > > > > > > > > On Tue, Mar 12, 2019 at 10:08:22PM

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-14 Thread Anup Patel
On Thu, Mar 14, 2019 at 12:23 PM Mike Rapoport wrote: > > On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote: > > On Thu, Mar 14, 2019 at 12:01 AM Mike Rapoport wrote: > > > > > > On Tue, Mar 12, 2019 at 10:08:22PM +, Anup Patel wrote: > > > > Currently, we have to boot RISCV64

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-14 Thread Mike Rapoport
On Thu, Mar 14, 2019 at 02:36:01AM +0530, Anup Patel wrote: > On Thu, Mar 14, 2019 at 12:01 AM Mike Rapoport wrote: > > > > On Tue, Mar 12, 2019 at 10:08:22PM +, Anup Patel wrote: > > > Currently, we have to boot RISCV64 kernel from a 2MB aligned physical > > > address and RISCV32 kernel from

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-13 Thread Anup Patel
On Thu, Mar 14, 2019 at 12:01 AM Mike Rapoport wrote: > > On Tue, Mar 12, 2019 at 10:08:22PM +, Anup Patel wrote: > > Currently, we have to boot RISCV64 kernel from a 2MB aligned physical > > address and RISCV32 kernel from a 4MB aligned physical address. This > > constraint is because

Re: [PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-13 Thread Mike Rapoport
On Tue, Mar 12, 2019 at 10:08:22PM +, Anup Patel wrote: > Currently, we have to boot RISCV64 kernel from a 2MB aligned physical > address and RISCV32 kernel from a 4MB aligned physical address. This > constraint is because initial pagetable setup (i.e. setup_vm()) maps > entire RAM using

[PATCH 3/3] RISC-V: Allow booting kernel from any 4KB aligned address

2019-03-12 Thread Anup Patel
Currently, we have to boot RISCV64 kernel from a 2MB aligned physical address and RISCV32 kernel from a 4MB aligned physical address. This constraint is because initial pagetable setup (i.e. setup_vm()) maps entire RAM using hugepages (i.e. 2MB for 3-level pagetable and 4MB for 2-level pagetable).