why Does Kernel Module should not do Floating Point operation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

 

Why Does Kernel Module should not do Floating Point operation? If it does what is the problem?

 

Please provide more links or articles towards the reason?

 

I got the following answer from http://kerneltrap.org/node/6405 which I am not able to understand.

 

   saving and restoring the FPU state on every syscall and interrupt is just slow, so it was a design decision not to do that. architectures with more registers than i386 even decided to only use some of them in kernel code to avoid saving and restoring the whole set, or they have a second set of registers just for supervisor code. as with the FPU, code that needs the by default unsaved registers can always save them itself.

 

Please any explanation

 

 

Thanks

Manjunath Naik

DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated..


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux