fxsave

What are coding conventions for using floating-point in Linux device drivers?

两盒软妹~` 提交于 2019-12-22 03:22:41
问题 This is related to this question. I'm not an expert on Linux device drivers or kernel modules, but I've been reading "Linux Device Drivers" [O'Reilly] by Rubini & Corbet and a number of online sources, but I haven't been able to find anything on this specific issue yet. When is a kernel or driver module allowed to use floating-point registers? If so, who is responsible for saving and restoring their contents? (Assume x86-64 architecture) If I understand correctly, whenever a KM is running, it

Linux device driver unsafe FXSAVE/FXRSTOR bug — any precedents?

你离开我真会死。 提交于 2019-12-21 20:34:59
问题 There's a nasty problem that has temporarily stumped a number of engineers at my company trying to debug it. The C++ program is normally run on a cluster of multicore computers with MPI. It will run for a very long time -- perhaps days -- and then suddenly fail. Most of engineers working on it have eliminated any reasonable possibility of a bug in the program itself, so they're starting to assign blame to a possible hardware problem, but I suspect there must be a software problem in either a

What are coding conventions for using floating-point in Linux device drivers?

a 夏天 提交于 2019-12-05 02:14:33
This is related to this question . I'm not an expert on Linux device drivers or kernel modules, but I've been reading "Linux Device Drivers" [O'Reilly] by Rubini & Corbet and a number of online sources, but I haven't been able to find anything on this specific issue yet. When is a kernel or driver module allowed to use floating-point registers? If so, who is responsible for saving and restoring their contents? (Assume x86-64 architecture) If I understand correctly, whenever a KM is running, it is using a hardware context (or hardware thread or register set -- whatever you want to call it) that