On 2019-03-28 5:49 a.m., Mike Rapoport wrote: >> + >> +The direct mapping covers as much of the physical memory space as >> +possible so that it may cover some IO memory. > > Please move the text before the tables, so that meaning of Sv32 and Sv39 > would be clear. > Ok, thanks. I've queued up this change for a v2. Logan
- [PATCH 5/7] RISC-V: Implement memory hotplug Logan Gunthorpe
- [PATCH 3/7] RISC-V: Rework kernel's virtual address space ... Logan Gunthorpe
- Re: [PATCH 3/7] RISC-V: Rework kernel's virtual addre... Palmer Dabbelt
- Re: [PATCH 3/7] RISC-V: Rework kernel's virtual a... Anup Patel
- Re: [PATCH 3/7] RISC-V: Rework kernel's virtu... Logan Gunthorpe
- [PATCH 4/7] RISC-V: Update page tables to cover the whole ... Logan Gunthorpe
- Re: [PATCH 4/7] RISC-V: Update page tables to cover t... Anup Patel
- Re: [PATCH 4/7] RISC-V: Update page tables to cov... Logan Gunthorpe
- [PATCH 2/7] RISC-V: doc: Add file describing the virtual m... Logan Gunthorpe
- Re: [PATCH 2/7] RISC-V: doc: Add file describing the ... Mike Rapoport
- Re: [PATCH 2/7] RISC-V: doc: Add file describing ... Logan Gunthorpe
- [PATCH 1/7] RISC-V: Implement sparsemem Logan Gunthorpe
- [PATCH 7/7] RISC-V: Implement pte_devmap() Logan Gunthorpe