From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: A bug about system call on ARM
Date: Thu, 30 May 2013 10:09:49 +0100 [thread overview]
Message-ID: <20130530090949.GC7483@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D1610991B866@CNBJMBX05.corpusers.net>
On Thu, May 30, 2013 at 02:41:42AM +0100, Wang, Yalin wrote:
> Hi Will,
Hello,
> Have you received the log files?
Yep, and you seem to be completely correct: CPU0 ages the page from which
CPU1 just executed a system call, so we explode trying to load the swi
instruction in order to retrieve the immediate.
> And is there someone looking at this issue now ?
It's on my list, but I'm pretty busy right now and OABI-compat isn't high
priority. Are you actually running OABI binaries? If not, you can simply
turn that option off (in fact, a quick fix to this issue is to make that
depend on !SMP).
> This issue happened on Qcom Scorpoin CPUs,
> And it just happened in our stability test occasionally .
>
> If you have some patch for this issue,
> I can do the test for it .
I'll have a look at cooking something which uses an exception table entry
to rewind the PC and retry the system call. That's simpler than directly
injecting a user page fault from the system call path.
Will
next prev parent reply other threads:[~2013-05-30 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35FD53F367049845BC99AC72306C23D1610991B85B@CNBJMBX05.corpusers.net>
[not found] ` <CAFLxGvy39xWdZmtiVHP+y=zH1coCVmMuREcmD25wSb=w-VK7Xg@mail.gmail.com>
[not found] ` <35FD53F367049845BC99AC72306C23D1610991B85D@CNBJMBX05.corpusers.net>
[not found] ` <35FD53F367049845BC99AC72306C23D1610991B85E@CNBJMBX05.corpusers.net>
2013-05-29 8:46 ` A bug about system call on ARM richard -rw- weinberger
2013-05-29 9:48 ` Will Deacon
[not found] ` <35FD53F367049845BC99AC72306C23D1610991B865@CNBJMBX05.corpusers.net>
2013-05-30 1:41 ` Wang, Yalin
2013-05-30 9:09 ` Will Deacon [this message]
2013-05-30 11:41 ` Will Deacon
2013-05-31 2:56 ` Wang, Yalin
2013-05-31 8:46 ` Will Deacon
2013-05-31 11:02 ` Wang, Yalin
2013-05-31 11:13 ` Will Deacon
2013-05-31 11:30 ` Wang, Yalin
2013-06-03 5:25 ` Wang, Yalin
2013-06-03 9:54 ` Will Deacon
2013-06-03 9:58 ` Wang, Yalin
2013-06-04 5:33 ` Wang, Yalin
2013-06-04 8:48 ` Will Deacon
2013-06-04 9:30 ` Wang, Yalin
2013-06-04 11:27 ` Will Deacon
2013-06-14 6:53 ` Wang, Yalin
2013-05-31 16:48 ` Nicolas Pitre
2013-05-31 16:52 ` Will Deacon
2013-05-31 3:54 ` Nicolas Pitre
2013-05-31 8:45 ` Will Deacon
2013-06-03 10:18 ` Russell King - ARM Linux
2013-06-03 10:27 ` Will Deacon
2013-06-03 10:45 ` Russell King - ARM Linux
2013-06-03 12:39 ` Will Deacon
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=20130530090949.GC7483@mudshark.cambridge.arm.com \
--to=will.deacon@arm.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