linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [patch][5/5] powerpc: Add the general support for Embedded Floating-Point instructions
Date: Sat, 13 Jan 2007 07:52:34 +1100	[thread overview]
Message-ID: <1168635154.5011.31.camel@localhost.localdomain> (raw)
In-Reply-To: <BDC705EB-9078-44FD-800E-D9ADD18B9471@kernel.crashing.org>

On Fri, 2007-01-12 at 12:39 -0600, Kumar Gala wrote:
> On Jan 12, 2007, at 5:05 AM, Benjamin Herrenschmidt wrote:
> 
> >
> >>> Why do we need a separate ret_from_except_spe_full?
> >>
> >> I'm not sure if the kernel will return from exception in a multi- 
> >> thread
> >> way, but the truth is if restoring EVRs in exsiting  
> >> ret_from_except_full,
> >> some non-SPE exception will try to retore EVR. At that time, the
> >> MSR[SPE] may not be enabled, which will cause error.
> >
> > Hrm... you can restore them before returning from the exception if you
> > are careful about doing that with preempt/irqs off I suppose.
> 
> Which is what I thought having the exception be EXC_XFER_EE and  
> flush_spe_to_thread should get you.
> 
> I dont see any reason to dirty up the 'exception' path for stuff we  
> can do in C code.

Well, doing that means that you will flush the SPE to the thread struct
and disable it, return to userland with SPE disabled, and right away
take a new exception as soon as the next SPE instruction is reached.
Maybe not optimal...

Ben.

  reply	other threads:[~2007-01-12 20:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  5:31 [patch][5/5] powerpc: Add the general support for Embedded Floating-Point instructions ebony.zhu
2007-01-12  6:40 ` Kumar Gala
2007-01-12  7:45   ` Zhu Ebony-r57400
2007-01-12 11:05     ` Benjamin Herrenschmidt
2007-01-12 18:39       ` Kumar Gala
2007-01-12 20:52         ` Benjamin Herrenschmidt [this message]
2007-01-12 21:18           ` Kumar Gala
2007-01-12 21:27             ` Benjamin Herrenschmidt
2007-01-12 21:49               ` Kumar Gala
2007-01-12 22:02                 ` Benjamin Herrenschmidt
2007-01-16  9:43                 ` Zhu Ebony-r57400
2007-01-16 21:54                   ` Benjamin Herrenschmidt
2007-01-15  8:06       ` [patch][5/5] powerpc: Add the general support for EmbeddedFloating-Point instructions Zhu Ebony-r57400
2007-01-12 18:53     ` [patch][5/5] powerpc: Add the general support for Embedded Floating-Point instructions Kumar Gala
2007-01-15  7:48       ` Zhu Ebony-r57400
2007-01-12  9:52 ` Christoph Hellwig
2007-01-12 10:23   ` Zhu Ebony-r57400
2007-01-12 12:36     ` Segher Boessenkool
2007-01-15  7:58       ` Zhu Ebony-r57400
2007-01-12 18:57   ` Kumar Gala

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=1168635154.5011.31.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).