From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Whitney <jwhitney-linuxppc@sands-edge.com>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Altivec Vector code bug
Date: Wed, 07 Apr 2004 16:30:53 +1000 [thread overview]
Message-ID: <1081319452.1382.44.camel@gaston> (raw)
In-Reply-To: <BE309A52-8807-11D8-B1DF-000A95A07384@sands-edge.com>
On Wed, 2004-04-07 at 06:19, John Whitney wrote:
> The attached patch corrects the following problem with the Altivec
> vector:
>
> When running Linux 2.6.5-rc2 (Altivec NOT configured in) on a 7410-base
> platform, and running a program that attempts to use a vector register,
> the kernel will lock up. This is due to vectoring to 0xf20, which is
> in the middle of the exception prolog as the exception handler is now
> written.
Thanks, forwarded upstream.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-04-07 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 20:19 Altivec Vector code bug John Whitney
2004-04-07 6:30 ` Benjamin Herrenschmidt [this message]
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=1081319452.1382.44.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jwhitney-linuxppc@sands-edge.com \
--cc=linuxppc-dev@lists.linuxppc.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).