linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: erik cameron <cameron@senta.uchicago.edu>
To: Jim Terman <terman@ddi.com>
Cc: Claude Robitaille <crobitaille@videotron.ca>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: question about altivec registers
Date: Mon, 25 Oct 1999 17:44:35 -0500	[thread overview]
Message-ID: <19991025174435.D9975@senta.uchicago.edu> (raw)
In-Reply-To: <199910252231.PAA08775@sade.ddi.com>



perhaps this is a stupid question, but aren't the values of the altivec
registers just saved as part of the process' hardware context and swapped
in and out as part of a context switch?  in which case it wouldn't matter
if the kernel (or any other process) changed the values while your job
was on a sleeping.

On Mon, Oct 25, 1999 at 03:31:48PM -0700, Jim Terman wrote:
> 
> I understand how to get it working from the processor point of view.  I 
> just want to make sure that the linuxppc kernal will not interfere if I 
> compile a program that uses these registers.
> 
> The bottom line is that I am not looking for any help with the altivec
> registers from the kernal.  I just want to be sure that there will not
> be any inteference.  If not, great.  I'd just like that insurance.
> Thanks for any clarification you can give me.
> 
> Claude Robitaille writes:
> > There is a flag for that purpose. You should look into the Altivec
> > environment on Motorola's Web site, or at www.altivec.org
> > 
> > Claude
> > 
> > 
> > On Mon, 25 Oct 1999, Jim Terman wrote:
> > 
> > > 
> > > I have a question about using the altivec registers on a G4 Macintosh
> > > running linuxppc.  Will there be any conflicts.  I don't expect any
> > > kernal support, but can I be confident that the kernal will not touch
> > > any of the altivec registers.  Any info will be greatly appreciated.
> > > 
> > > -- 
> > > ______________________________________________________________________________
> > > Jim Terman       |   323 Vintage Park Dr.   |   Voice: (650) 356-5446
> > > terman@ddi.com   |   Foster City, CA        |   Fax:   (650) 356-5490
> > > Diab-SDS, Inc.   |   94404                  |   web site - http://www.ddi.com
> > > 
> > > 
> > 
> > 
> -- 
> ______________________________________________________________________________
> Jim Terman       |   323 Vintage Park Dr.   |   Voice: (650) 356-5446
> terman@ddi.com   |   Foster City, CA        |   Fax:   (650) 356-5490
> Diab-SDS, Inc.   |   94404                  |   web site - http://www.ddi.com

-- 
erik cameron  unix systems administrator
jfi/mrsec @ the university of chicago
e-cameron@uchicago.edu

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

  reply	other threads:[~1999-10-25 22:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-25 20:51 question about altivec registers Jim Terman
1999-10-25 22:27 ` Claude Robitaille
1999-10-25 22:31   ` Jim Terman
1999-10-25 22:44     ` erik cameron [this message]
1999-10-25 23:28     ` Claude Robitaille
     [not found]     ` <Pine.LNX.4.10.9910251916060.5902-100000@modemcable220.93-200-24.mtl.mc.vi deotron.net>
1999-10-25 23:53       ` Rob Barris
1999-10-26 18:22         ` Geert Uytterhoeven
1999-10-26 22:13           ` Rob Barris
1999-10-26 22:38           ` Tom Vier
1999-10-26 22:03         ` Tom Vier
1999-10-26  4:42 ` Kumar Gala
1999-10-26 21:52   ` Jim Terman
1999-10-26 22:43     ` Kumar Gala
1999-10-27  8:58       ` Adrian Cox
1999-10-27 13:21         ` Gabriel Paubert
1999-10-27 16:05           ` Geert Uytterhoeven
1999-10-27 18:23           ` Kumar Gala
1999-10-27 22:39           ` Tony Mantler
1999-10-28 11:01             ` Gabriel Paubert
1999-10-28 21:20               ` Tony Mantler
1999-10-29 11:58                 ` Benjamin Herrenschmidt
1999-10-29 12:49                 ` Gabriel Paubert
1999-10-30  4:14                   ` Tony Mantler

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=19991025174435.D9975@senta.uchicago.edu \
    --to=cameron@senta.uchicago.edu \
    --cc=crobitaille@videotron.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=terman@ddi.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).