From: Paul Mackerras <paulus@samba.org>
To: Alan Curry <pacman@TheWorld.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: fix altivec_unavailable_exception Oopses
Date: Wed, 22 Feb 2006 22:46:30 +1100 [thread overview]
Message-ID: <17404.20246.361572.784670@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <200602212339.SAA1138491@shell.TheWorld.com>
Alan Curry writes:
> altivec_unavailable_exception is called without setting r3... it looks like
> the r3 that actually gets passed in as struct pt_regs *regs is the
> undisturbed value of r3 at the time the altivec instruction was encountered.
Nice catch!
Thanks,
Paul.
prev parent reply other threads:[~2006-02-22 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 23:39 [PATCH] powerpc: fix altivec_unavailable_exception Oopses Alan Curry
2006-02-22 0:52 ` Kumar Gala
2006-02-22 6:42 ` Alan Curry
2006-02-22 11:46 ` Paul Mackerras [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=17404.20246.361572.784670@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pacman@TheWorld.com \
/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).