From: Agner Fog <agner@agner.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: ABI change for device drivers using future AVX instruction set
Date: Sat, 28 Jun 2008 10:05:46 +0200 [thread overview]
Message-ID: <4865F0DA.2050906@agner.org> (raw)
In-Reply-To: <20080627072231.7337ba18@infradead.org>
Arjan van de Ven wrote:
>the good news is that we review drivers before they get included and
we do catch such things.
Are you saying that some group should have the monopoly of approving
device drivers? That is exectly the policy that Microsoft has been so
much criticized for. You can only control the drivers that are included
in your own Linux distribution.
Nothing should prevent me from publishing my own driver for some special
purpose (in fact, I am going to do so). The open source principle would
allow anybody to make a different compiler for device drivers, possibly
using a different programming language. Or making a function library for
use in device drivers.
Thank you for the reference to DocBook/kernel-hacking. The title reads
"Unreliable Guide To Hacking The Linux Kernel". This doesn't really look
like the place to look for authoritative information. It warns against
using floating point/MMX, but not XMM. You can't blame programmers for
making faulty device drivers when there is no authoritative guideline to
follow.
You don't seem to realize the importance of proper documentation. Do you
want me to write in my manual: "There is no authoritative information on
this, but the Linux Junta says so-and-so.."?
How can you expect people to regard Linux as a serious and reliable
alternative to ..BEEP.. when there is no proper documentation?
It is a disgrace that the ABI consists of fractions stored in weird
places and some of them still drafts, but at least there is consensus on
which one to look in for authoritative information. There should be an
authoritative document on what you can do and not do in a device driver,
and the ABI would be the most natural place to put this information. It
is important to tell people that they can save and restore an XMM
register under certain conditions, but not a YMM register. You can't
expect people to search through a huge mailing list archive for such
information.
Note: Please Cc: me of answers
next prev parent reply other threads:[~2008-06-28 8:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 15:32 ABI change for device drivers using future AVX instruction set Agner Fog
2008-06-25 16:22 ` Arjan van de Ven
2008-06-25 19:54 ` Agner Fog
2008-06-25 20:09 ` Arjan van de Ven
2008-06-26 1:11 ` H. Peter Anvin
2008-06-27 11:31 ` Agner Fog
2008-06-27 14:22 ` Arjan van de Ven
2008-06-28 8:05 ` Agner Fog [this message]
2008-06-28 8:10 ` David Miller
2008-06-28 11:47 ` Andi Kleen
2008-06-28 15:09 ` Agner Fog
2008-06-28 15:44 ` Helge Hafting
2008-06-28 20:02 ` Andi Kleen
2008-06-29 11:33 ` Avi Kivity
2008-06-29 12:21 ` Andi Kleen
2008-06-29 12:31 ` Avi Kivity
2008-06-29 13:07 ` Andi Kleen
2008-06-29 13:18 ` Avi Kivity
2008-06-29 13:23 ` Andi Kleen
2008-06-29 13:29 ` Avi Kivity
2008-06-29 22:08 ` H. Peter Anvin
2008-06-29 12:29 ` Alan Cox
2008-07-01 15:30 ` Arjan van de Ven
2008-06-25 20:14 ` Alan Cox
2008-06-26 14:01 ` Andi Kleen
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=4865F0DA.2050906@agner.org \
--to=agner@agner.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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