From: Al Viro <viro@zeniv.linux.org.uk>
To: Richard Henderson <rth@twiddle.net>
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] alpha: fix FEN fault handling
Date: Sat, 7 Jan 2023 21:28:19 +0000 [thread overview]
Message-ID: <Y7nj80buxCO3u69l@ZenIV> (raw)
In-Reply-To: <Y7jdARsEQXPugR0t@ZenIV>
On Sat, Jan 07, 2023 at 02:46:26AM +0000, Al Viro wrote:
> Not sure it's worth bothering with in palcode-clipper - for Linux it's
> useless (run out of timeslice and FEN will end up set, no matter what),
> nothing in NetBSD or OpenBSD trees generates that call_pal, current
> FreeBSD doesn't support alpha and their last version to do so hadn't
> generated that call_pal either... What else is out there? OSF?
BTW, out of curiosity - what was
case 5: /* illoc */
default: /* unexpected instruction-fault type */
about in that switch in do_entIF()?
All documentation I'd been able to find had only 0..4 as expected
values (bpt/bugcheck/gentrap/fen/opdec)...
next prev parent reply other threads:[~2023-01-07 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 0:59 [PATCH] alpha: fix FEN fault handling Al Viro
2023-01-07 1:55 ` Richard Henderson
2023-01-07 2:46 ` Al Viro
2023-01-07 21:28 ` Al Viro [this message]
2023-01-07 23:03 ` Richard Henderson
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=Y7nj80buxCO3u69l@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).