From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Ingenic JZ4730 - illegal instruction
Date: Mon, 09 Mar 2009 10:45:11 -0500 [thread overview]
Message-ID: <49B53987.8020206@paralogos.com> (raw)
In-Reply-To: <49B5302F.4070301@kernelconcepts.de>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Nils Faerber wrote:
> Kevin D. Kissell schrieb:
>
>> Are you sure that the JZ_RISC section is in fact the version of those
>> functions that's being built into your kernel?
>>
>
> Well, there is CONFIG_JZRISC=y in the kernel .config and a
> switch(current_cpu_type) { case CPU_JZRISC: ...} so I would assume it is
> being used. But I will verify that the CONFIG_JZRISC=y is correctly
> translated into a current_cpu_type.
>
Your assumption is reasonable. But given that things aren't working,
yes, it's good to verify.
> Oh, one last question, in order to rule out the cache as bug-spot would
> the kernel option "run uncached" "solve" the issue (and be darn slow)?
>
It would certainly solve the issue, and would *probably* result in a
system that would be fully functional but slow. Very high end and very
low end systems can be rendered unusable by forcing uncached operation,
but it's certainly worth a try. Also, if your cache control logic
supports both write-back and write-through operation, if you set the
default cache "attribute" for kernel and page tables (which is
essentially what you're doing under-the-hood when you configure for
uncached operation) to write-through, that should cure the problems with
copying text pages, but *not* those with re-using them, with less
performance impact. I'd be a little surprised if the Ingenic part
offered both modes, though.
Regards,
Kevin K.
[-- Attachment #2: Type: text/html, Size: 1986 bytes --]
next prev parent reply other threads:[~2009-03-09 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 16:36 Ingenic JZ4730 - illegal instruction Nils Faerber
2009-03-08 14:53 ` Markus Gothe
2009-03-08 16:03 ` ard
2009-03-10 17:12 ` Markus Gothe
2009-03-09 8:39 ` Kevin D. Kissell
2009-03-09 10:00 ` Nils Faerber
2009-03-09 14:12 ` Kevin D. Kissell
2009-03-09 15:05 ` Nils Faerber
2009-03-09 15:45 ` Kevin D. Kissell [this message]
2009-03-09 16:26 ` Nils Faerber
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=49B53987.8020206@paralogos.com \
--to=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
--cc=nils.faerber@kernelconcepts.de \
/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