On Sun, 18 Aug 2019 23:00:40 PDT (-0700), bmeng...@gmail.com wrote:
On Wed, Aug 14, 2019 at 5:46 PM Bin Meng wrote:
Hi Palmer,
On Sat, Aug 10, 2019 at 9:49 AM Alistair Francis wrote:
>
> On Wed, Aug 7, 2019 at 7:50 PM Bin Meng wrote:
> >
> > For RV32, the root page table's PPN has 22 bits h
On Wed, Aug 14, 2019 at 5:46 PM Bin Meng wrote:
>
> Hi Palmer,
>
> On Sat, Aug 10, 2019 at 9:49 AM Alistair Francis wrote:
> >
> > On Wed, Aug 7, 2019 at 7:50 PM Bin Meng wrote:
> > >
> > > For RV32, the root page table's PPN has 22 bits hence its address
> > > bits could be larger than the maxi
Hi Palmer,
On Sat, Aug 10, 2019 at 9:49 AM Alistair Francis wrote:
>
> On Wed, Aug 7, 2019 at 7:50 PM Bin Meng wrote:
> >
> > For RV32, the root page table's PPN has 22 bits hence its address
> > bits could be larger than the maximum bits that target_ulong is
> > able to represent. Use hwaddr in
On Wed, Aug 7, 2019 at 7:50 PM Bin Meng wrote:
>
> For RV32, the root page table's PPN has 22 bits hence its address
> bits could be larger than the maximum bits that target_ulong is
> able to represent. Use hwaddr instead.
>
> Signed-off-by: Bin Meng
Reviewed-by: Alistair Francis
Alistair
>
For RV32, the root page table's PPN has 22 bits hence its address
bits could be larger than the maximum bits that target_ulong is
able to represent. Use hwaddr instead.
Signed-off-by: Bin Meng
---
Changes in v2:
- promote ppn, env->satp/env->sptbl to hwaddr otherwise the page
table base will
