From: sshaiju@mvista.com (shaiju)
To: linux-arm-kernel@lists.infradead.org
Subject: Oops #817 on ARM MPCore with 2.6.22-rc3
Date: Sat, 15 Oct 2011 01:25:22 +0000 (UTC) [thread overview]
Message-ID: <loom.20111015T032223-30@post.gmane.org> (raw)
In-Reply-To: 466690C0.7060500@ccrl-nece.de
Joerg Wagner <wagner <at> ccrl-nece.de> writes:
>
> > One more patch worth testing is:
> >
> > http://www.linux-arm.org/git?p=linux-
2.6.git;a=commitdiff_plain;h=3fe656e0dece808ae1de97f98a2e917c46573beb
>
> That one looks very interesting indeed.
> However I cannot find any information about the mentioned errata.
> Sadly enough the workaround presented here uses privileged access to CP15
which might fix the kernel but
> userspace programs are left out.
>
> If someone can put more light into this I would be glad to hear about it.
> At the first glance it seems to add artificial idle cycles to all operations
based on ldrex/strex
> combination, but why are they coupled to the processor id ? Isn't there a
chance that a process/threads
> gets moved to another processor when running code in kernel space (when
running the idle loop), given a
> preemptive kernel.
>
> Regards !
>
> Joerg
>
Hi wanger,
Did this problem got solved . What was the solution . I am getting
similar Error .
regards,
shaiju
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
>
>
parent reply other threads:[~2011-10-15 1:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <466690C0.7060500@ccrl-nece.de>]
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=loom.20111015T032223-30@post.gmane.org \
--to=sshaiju@mvista.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).