From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, cort@fsmlabs.com,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: __switch_to test-and-branch ALTIVEC specific?
Date: Sun, 18 Sep 2005 11:31:39 +1000 [thread overview]
Message-ID: <1127007099.23095.10.camel@gaston> (raw)
In-Reply-To: <28EAC1FF-341D-45C3-BA9E-221AE04F6DC1@freescale.com>
On Tue, 2005-09-13 at 16:43 -0500, Kumar Gala wrote:
> On Sep 13, 2005, at 3:35 PM, Marcelo Tosatti wrote:
>
> > On Tue, Sep 13, 2005 at 02:05:57PM -0500, Kumar Gala wrote:
> >
> >> This probably has to due with what happens on a G4 system with a
> >> kernel not build with Altivec.. However, I dont remember exactly what
> >>
> >
> >
> >> behavior is desired.
> >>
> >
> > What would be the appropriate set of definitions to use, then ?
> >
> > #if defined (CONFIG_ALTIVEC || CONFIG_6xx) ?
>
> That's probably better. Hopefully Ben will have some reason if what
> you suggest is not sufficient.
Just #ifdef CONFIG_ALTIVEC is fine
Ben.
next prev parent reply other threads:[~2005-09-18 1:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:50 __switch_to test-and-branch ALTIVEC specific? Marcelo Tosatti
2005-09-13 19:05 ` Kumar Gala
2005-09-13 20:35 ` Marcelo Tosatti
2005-09-13 21:43 ` Kumar Gala
2005-09-18 1:31 ` Benjamin Herrenschmidt [this message]
2005-09-15 8:21 ` Segher Boessenkool
2005-09-18 1:31 ` Benjamin Herrenschmidt
2005-09-13 22:23 ` -dev and -embedded cross-posting Eugene Surovegin
2005-09-15 11:18 ` __switch_to test-and-branch ALTIVEC specific? Paul Mackerras
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=1127007099.23095.10.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cort@fsmlabs.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.