[PATCH v2] powerpc/powernv: Initialise nest mmu
Alistair Popple
alistair at popple.id.au
Mon Dec 5 11:02:35 AEDT 2016
Hi,
On Sat, 3 Dec 2016 10:40:58 PM Michael Ellerman wrote:
> Michael Ellerman <mpe at ellerman.id.au> writes:
>
> > Balbir Singh <bsingharora at gmail.com> writes:
> >
> >> <snip>
> >>
> >>> static void __init radix_init_partition_table(void)
> >>> {
> >>> - unsigned long rts_field;
> >>> + unsigned long rts_field, ptcr;
> >>
> >> I think these functions have changed, check for conflicts against
> >> http://git.kernel.org/cgit/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=9d66195807ac6cb8a14231fd055ff755977c5fca
> >
> > They did, I ended up with:
> >
> > https://github.com/linuxppc/linux/commit/fb7314c5d6b00dbaaac14c28a52a87dee7e726df
>
> It's not happy on mambo:
>
> WARNING: 20856759: (20856757): Invalid address 0x0000000028096258 in XSCOM range, SCOM=0x00280962b
> WARNING: 20856759: (20856757): Attempt to store non-existent address 0x00001A0028096258
> 20856759: (20856757): 0x000000003002DA08 : stdcix r26,r0,r3
> FATAL ERROR: 20856759: (20856757): Check Stop for 0:0: Machine Check with ME bit of MSR off
>
> Which looks to be one of the xscom_write()'s from opal_nmmu_set_ptcr().
Weird. Do you happen to know which one? It should only be touching the NMMU
PTCR register which is defined as 0x5012c4b.
> Do I need a newer mambo?
I'm not sure to be honest. I do all of my testing under Simics which uses Mambo
internally but provides some additional models. Perhaps Mambo is missing a
required model? Will see if I can recreate it under Simics with that branch.
- Alistair
> cheers
More information about the Linuxppc-dev
mailing list