linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 4.13-rc3: Unrecoverable exception 4100
Date: Sat, 5 Aug 2017 23:39:17 +1000	[thread overview]
Message-ID: <20170805233917.72e49d2f@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <877eyjkt0u.fsf@linux-m68k.org>

On Fri, 04 Aug 2017 21:54:57 +0200
Andreas Schwab <schwab@linux-m68k.org> wrote:

> No, this is really a 4.13-rc1 regression.
> 
> Andreas.
> 

SLB miss with MSR[RI]=0 on

lbz     r0,THREAD+THREAD_LOAD_FP(r7)

Caused by bc4f65e4cf9d6cc43e0e9ba0b8648cf9201cd55f

Hmm, I'll see if something can be done, but that MSR_RI stuff in syscall
exit makes things fairly difficult (and will reduce performance improvement
of this patch anyway).

I'm trying to work to a point where we have a soft-RI bit for these kinds of
uses that would avoid all this complexity. Until then it may be best to
just revert this patch.

Thanks for the report

  reply	other threads:[~2017-08-05 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vam3lhtn.fsf__12885.8019285419$1501844971$gmane$org@linux-m68k.org>
2017-08-04 19:39 ` 4.13-rc3: Unrecoverable exception 4100 Andreas Schwab
     [not found] ` <87fud7ktqf.fsf__17563.3519575515$1501875675$gmane$org@linux-m68k.org>
2017-08-04 19:54   ` Andreas Schwab
2017-08-05 13:39     ` Nicholas Piggin [this message]
2017-08-07  9:56       ` Michael Ellerman
2017-08-07 10:26         ` Nicholas Piggin
2017-08-07 11:49           ` Michael Ellerman
2017-08-07 10:40         ` Andreas Schwab
2017-08-07 11:20           ` Michael Ellerman
2017-08-04 10:59 Andreas Schwab
2017-08-04 13:00 ` Benjamin Herrenschmidt

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=20170805233917.72e49d2f@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=schwab@linux-m68k.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).