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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Jun 2008 21:14:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Agner Fog <agner@...er.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ABI change for device drivers using future AVX instruction set

> 3. When compiling a device driver, the compiler may insert implicit 
> calls to library functions such as memcpy and memset. These functions 
> typically have a CPU dispatcher that chooses the largest register size 
> available. The device driver may therefore use YMM registers without the 
> knowledge of the programmer and without compiling with the AVX switch on.

Linux uses its own routines in these cases - and in fact for MMX we
generally avoid kernel usage in order to avoid the overheads (ditto FP).

> A decision on this question should be made and published in the ABI so 
> that people can make compatible device drivers.

The beauty of the Linux kernel being source based - we don't have to worry
about ABI problems like this.

Alan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/