From: Alistair Popple <alistair@popple.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Balbir Singh <bsingharora@gmail.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v2] powerpc/powernv: Initialise nest mmu
Date: Mon, 05 Dec 2016 11:02:35 +1100 [thread overview]
Message-ID: <1500348.HuelYn9x60@new-mexico> (raw)
In-Reply-To: <87mvgdxmt1.fsf@concordia.ellerman.id.au>
Hi,
On Sat, 3 Dec 2016 10:40:58 PM Michael Ellerman wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
>
> > Balbir Singh <bsingharora@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
next prev parent reply other threads:[~2016-12-05 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 5:29 [PATCH v2] powerpc/powernv: Initialise nest mmu Alistair Popple
2016-12-02 9:24 ` Michael Ellerman
2016-12-03 0:08 ` Alistair Popple
2016-12-03 1:33 ` Tyrel Datwyler
2016-12-02 11:04 ` Balbir Singh
2016-12-03 10:56 ` Michael Ellerman
2016-12-03 11:40 ` Michael Ellerman
2016-12-05 0:02 ` Alistair Popple [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-05 1:59 Michael Ellerman
2016-12-05 6:32 ` Balbir Singh
2016-12-05 7:23 ` Aneesh Kumar K.V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1500348.HuelYn9x60@new-mexico \
--to=alistair@popple.id.au \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox