From: luis@debethencourt.com (Luis de Bethencourt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to handle float-point operations
Date: Wed, 1 Jul 2015 11:53:49 +0100 [thread overview]
Message-ID: <20150701105349.GA26760@turing> (raw)
In-Reply-To: <CAE_iR+gqFbF5JQ5CnjPdHv1GjbbxT9payUPoWYWqmRU=eSp5Sw@mail.gmail.com>
On Wed, Jul 01, 2015 at 01:58:30PM +0530, priyaranjan wrote:
> Hi Arun,
>
>
> >On Thu, Jun 25, 2015 at 2:33 PM, Arun KS <getarunks@gmail.com> wrote:
> >Hello Mudongliang,
> >
> >
> > >On Tue, Jun 23, 2015 at 9:01 AM, ??? <mudongliangabcd@gmail.com> wrote:
> > >>
> > >> I know there are rarely float-point operations! What's the exception?
> > > In the linux kernel, how does it handle the float-point operations in
> > the >userland?
> >
> > >>Most of the userspace programs do not use FP instructions. So by
> > >>default floating point engine is turned off during a context switch.
> > >>When a process executes floating point instruction, an undefined
> > >>exception is generated. Exception handler enables the floating point
> > >>engine and jump back to the same instruction which caused the
> > >>exception so that it will get re executed with FP engine on.
> >
> > Is this somehow related to the platform in which linux runs? If the FP
> > operations are valid, then will that still generate the exception or it
> > does a context switch, turns on FP engine and re-executed?
> >
Hi Priyaranjan,
Your email got mangled. Please don't send HTML attachments in your emails to
the Linux Kernel mailing lists.
Try again to reply to Arun.
Thanks,
Luis
next prev parent reply other threads:[~2015-07-01 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 3:31 How to handle float-point operations 慕冬亮
2015-06-25 9:03 ` Arun KS
2015-07-01 8:28 ` priyaranjan
2015-07-01 10:53 ` Luis de Bethencourt [this message]
2015-07-06 7:43 ` priyaranjan
2015-07-08 7:56 ` Arun KS
2015-07-08 10:41 ` priyaranjan
2015-07-09 2:41 ` Kernel idle jinzhao at wingtech.com
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=20150701105349.GA26760@turing \
--to=luis@debethencourt.com \
--cc=kernelnewbies@lists.kernelnewbies.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).