From: Bob Picco <bpicco@meloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH V2] sparc64: sun4v TLB error power off events
Date: Wed, 17 Sep 2014 12:40:29 +0000 [thread overview]
Message-ID: <20140917124029.GL17331@zareason> (raw)
In-Reply-To: <1410874007-11501-1-git-send-email-bpicco@meloft.net>
David Miller wrote: [Tue Sep 16 2014, 08:49:43PM EDT]
> From: Bob Picco <bpicco@meloft.net>
> Date: Tue, 16 Sep 2014 09:26:47 -0400
>
> > Normally sun4v_itlb_error_report() and sun4v_dtlb_error_report() would call
> > prom_halt() and drop us to OF command prompt "ok". This isn't the case for
> > LDOMs and the machine powers off.
> >
> > For the HV reported error of HV_ENORADDR for HV HV_MMU_MAP_ADDR_TRAP we cause
> > a SIGBUS error by qualifying it within do_sparc64_fault() for fault code mask
> > of FAULT_CODE_BAD_RA. This is done when trap level (%tl) is less or equal
> > one("1"). Otherwise, for %tl > 1, we proceed eventually to die_if_kernel().
>
> This patch is great, applied, thanks Bob.
>
> I think I'd like to request a follow-on patch to this if you don't
> mind.
Fine by me.
>
> If %tl > 1, the only situation we can possibly be in is to be taking a
> TLB miss during a window spill/fill trap, in which case we should
> up-trap back up through the spill/fill handler and into the long path
> fault code via winfix_trampoline.
Yes I agree.
>
> Then you can kill all of the {i,d}tlb error code paths.
Let me look at this.
>
> Thanks!
you're welcome and thanx!
next prev parent reply other threads:[~2014-09-17 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 13:26 [PATCH V2] sparc64: sun4v TLB error power off events Bob Picco
2014-09-16 21:47 ` David Miller
2014-09-17 0:16 ` David Miller
2014-09-17 0:35 ` David Miller
2014-09-17 0:49 ` David Miller
2014-09-17 12:19 ` Bob Picco
2014-09-17 12:24 ` Bob Picco
2014-09-17 12:40 ` Bob Picco [this message]
2014-09-17 16:00 ` 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=20140917124029.GL17331@zareason \
--to=bpicco@meloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.