Re: ABI change for device drivers using future AVX instruction set

[Arjan van de Ven]

On Fri, 27 Jun 2008 13:31:49 +0200
Agner Fog <agner@xxxxxxxxx> wrote:

> Arjan van de Ven wrote:
> 
> >the linux kernel policy is loud and clear; this is more an OS policy
> >as it is a platform ABI issue.
> 
> It doesn't help to say it "loud and clear" in a closed mailing list.

lkml is rather public

> It has to go into an official document that people can find, and the
> ABI is the most natural place to look for such rules. The ABI is hard
> enough to find. Is there an official OS policy document somewhere
> that I haven't found? Please point me to an authoritative document.

DocBook/kernel-hacking.tmpl has a section about it.


> You can't blame driver makers for using XMM or YMM registers in
> inline assembly or intrinsic functions or calling their own libraries
> or using a different compiler unless there is an official rule
> against it written in some official document that is easy to find. If
> you want to move data in a device driver, it is tempting indeed to
> use the largest register size available.

the good news is that we review drivers before they get included and we
do catch such things. In addition, we give the compiler the command
line options that prevent it from using these instructions....
I don't think this is a problem in practice for Linux drivers.

(I'm deliberately ignoring non-opensource drivers here; you get what
you get with those; "just say no").



-- 
If you want to reach me at my work email, use arjan@xxxxxxxxxxxxxxx
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/