linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Altivec on 2.4.xx?
Date: Thu, 27 Jul 2000 21:15:27 -0400	[thread overview]
Message-ID: <3980DEAF.ACFB0C43@embeddededge.com> (raw)


Anyone out there using Altivec with a 2.4.0 kernel?  Maybe this
is the wrong list to ask....suggestions welcome.

There is a bug in the Instruction fault handler that interprets the
Altivec enabled flag in the MSR as a write attempt to a protected
instruction page.  It is because we commonly use the DSISR and SRR1,
and call it 'error_code' in do_page_fault.  The 0x02000000 is the
Altivec enabled flag in SRR1.

This should also break 2.2.xx (unless Altivec enabled is managed
differently and I don't know that).

Right now, I am just removing this as part of the exception handler,
so this function never finds this bit set for instruction faults.
Anyone else?


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-07-28  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-28  1:15 Dan Malek [this message]
2000-07-28  7:24 ` Altivec on 2.4.xx? Daniel Marmier
2000-07-28 14:48   ` Dan Malek
2000-07-28 16:57     ` Daniel Marmier

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=3980DEAF.ACFB0C43@embeddededge.com \
    --to=dan@netx4.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).