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: Fri, 12 Jan 2007 21:27:57 +0000 [thread overview]
Message-ID: <1168637277.5011.36.camel@localhost.localdomain> (raw)
In-Reply-To: <615F9884-6695-485A-A4B4-A53BD98F969E@kernel.crashing.org>
> I think its a fair assumption that nothing is going to interrupt the
> handling of the exception, so its safe to assume the process causing
> the interrupt will be the same one we return to.
What about the get_user to get to the faulting instruction ? I suppose
if those processors are UP only and we use an exception with EE
disabled, there should be no way the page has been evicted since the
access, so that should work, but will that ever be true ?
Ben.
next prev parent reply other threads:[~2007-01-12 21:27 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
2007-01-12 21:18 ` Kumar Gala
2007-01-12 21:27 ` Benjamin Herrenschmidt [this message]
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=1168637277.5011.36.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).