From: David Ahern <david.ahern@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc: deadlock using perf with sched tracepoints and user callstacks
Date: Tue, 31 Mar 2015 23:52:53 +0000 [thread overview]
Message-ID: <551B3355.2040003@oracle.com> (raw)
In-Reply-To: <551AFA5A.1000908@oracle.com>
On 3/31/15 5:38 PM, David Miller wrote:
> What is different in the PowerPC fault path vs. the Sparc one that
> causes the SIGBUS for sparc where the PowerPC does not see it?
>
> I don't understand where the SIGBUS comes from. In a pagefault
> disable section on sparc, in_atomic() should be true, thus we'll call
> do_kernel_fault(), fall through to the TSTATE_PRIV code path and
> simply run the exception handler.
>
That's what I was hoping someone could explain to me. I'll dig deeper on
Monday.
next prev parent reply other threads:[~2015-03-31 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 19:49 sparc: deadlock using perf with sched tracepoints and user callstacks David Ahern
2015-03-31 23:38 ` David Miller
2015-03-31 23:52 ` David Ahern [this message]
2015-04-22 23:22 ` David Miller
2015-04-23 0:39 ` David Ahern
2015-04-23 1:40 ` David Miller
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=551B3355.2040003@oracle.com \
--to=david.ahern@oracle.com \
--cc=sparclinux@vger.kernel.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).