From: Ralf Baechle <ralf@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: IP30: SMP, Almost there?
Date: Mon, 1 Jun 2015 21:32:08 +0200 [thread overview]
Message-ID: <20150601193208.GA29986@linux-mips.org> (raw)
In-Reply-To: <556142C5.7090206@gentoo.org>
On Sat, May 23, 2015 at 11:17:25PM -0400, Joshua Kinard wrote:
> I even got the IRQs to be fanned out across both CPUs. Well, primarily the
> qla1280 drivers. They randomly hop between both CPUs, but no ill effects so far.
>
> But if I boot that *same* working kernel on an R14000 dual module, I get handed
> an IBE as soon as the userland mounts. The only documented differences that I
> can find on the R14000 is that it supports DDR memory, being able to do memory
> operations on the rising edge and falling edge of each clock. Not sure if that
> matters to the kernel at all, but I know of nothing else that describes the
> R14K's internals, such as if there's some new bit in CP0 config,
> branch-diagnostic, status, etc, that might explain why these IBE's are happening.
>
> Guess I need to hunt down my old dual R10K module next and verify that works
> fine...
>
> Also, is there a way to hardcode the cca=5 setting for IP30? Maybe it needs to
> be a hidden Kconfig item?. I tried setting cpu->writecombine in cpu-probe.c,
> but no dice there. If I boot an SMP kernel on dual R12K's w/o cca=5, I'll get
> one or two pretty-specific oopses. The one I did grab complains about bad
> spinlock magic in the core tty driver somewhere. I can transcribe that oops
> later on if interested.
Can you insert something like:
printk("c0_config: %08x\n", read_c0_config());
into a kernel and boot it without cca=5? I'm really curious what the
startup CCA is.
Ralf
next prev parent reply other threads:[~2015-06-01 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 5:39 IP30: SMP, Almost there? Joshua Kinard
2015-05-18 12:01 ` Joshua Kinard
2015-05-20 5:23 ` Joshua Kinard
2015-05-21 6:00 ` Joshua Kinard
2015-05-22 12:01 ` Maciej W. Rozycki
2015-05-22 17:11 ` Ralf Baechle
2015-05-23 22:52 ` Joshua Kinard
2015-05-24 14:25 ` Maciej W. Rozycki
2015-05-22 16:38 ` Ralf Baechle
2015-05-23 22:57 ` Joshua Kinard
2015-05-22 16:25 ` Ralf Baechle
2015-05-24 3:17 ` Joshua Kinard
2015-06-01 5:08 ` Joshua Kinard
2015-06-01 6:00 ` IP30: SMP, Almost there! Joshua Kinard
2015-06-01 19:32 ` Ralf Baechle [this message]
2015-06-02 5:31 ` IP30: SMP, Almost there? Joshua Kinard
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=20150601193208.GA29986@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
/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