public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mathiasen@gmail.com
Subject: Re: A set of "standard" virtual devices?
Date: Mon, 02 Apr 2007 14:49:55 -0700	[thread overview]
Message-ID: <adak5wue9a4.fsf@cisco.com> (raw)
In-Reply-To: <46116898.5050701@zytor.com> (H. Peter Anvin's message of "Mon, 02 Apr 2007 13:33:28 -0700")

 > > > Obviously, anyone who adheres to the published interface can
 > > > use one of these VID:DIDs -- as far as I'm concerned, even
 > > > hardware vendors; we'll use the SID to distinguish between
 > > > implementations.

 > > I think for this to work, some attempt at a conformance testing
 > > program is required...

 > How would you propose one goes about that?  It seems to me the only
 > plausible thing is "does it work with the unmodified driver included
 > in the Linux kernel?"  What else can one realistically do?

Well, even "works with the Linux driver" can be formalized with a test
plan that describes how to say it works.  But one can also imagine a
test harness that drives the virtual hardware with synthetic test data
and makes sure it does what it's supposed to.

It also helps when writing the spec to try and write lots of anal
"compliance statements" that can be tested in the suite.

But really, I just think we need a stick to shake at people to force
them to fix bugs in their virtual devices, to avoid a big mess of
quirks that defeats the purpose of the whole exercise.

 - R.

  reply	other threads:[~2007-04-02 21:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 20:18 A set of "standard" virtual devices? H. Peter Anvin
2007-04-02 20:31 ` Roland Dreier
2007-04-02 20:33   ` H. Peter Anvin
2007-04-02 21:49     ` Roland Dreier [this message]
2007-04-02 20:56 ` Jeremy Fitzhardinge
2007-04-02 21:12   ` Andi Kleen
2007-04-02 21:33     ` Jeff Garzik
2007-04-02 21:36       ` Andi Kleen
2007-04-02 21:42         ` Jeremy Fitzhardinge
2007-04-02 21:53           ` Anthony Liguori
2007-04-02 22:04             ` Jeremy Fitzhardinge
2007-04-02 22:10           ` H. Peter Anvin
2007-04-02 22:25             ` Jeff Garzik
2007-04-02 22:30               ` H. Peter Anvin
2007-04-03  9:41             ` Arnd Bergmann
2007-04-03 10:41               ` Cornelia Huck
2007-04-03 12:15                 ` Arnd Bergmann
2007-04-03 13:39                   ` Cornelia Huck
2007-04-03 14:03                     ` Arnd Bergmann
2007-04-03 16:07                       ` Cornelia Huck
2007-04-03  8:29     ` Christian Borntraeger
2007-04-03  8:30       ` Andi Kleen
2007-04-03  9:17         ` Cornelia Huck
2007-04-03  9:26           ` Andi Kleen
2007-04-03 10:51             ` Cornelia Huck
2007-04-03 15:00             ` Adrian Bunk
2007-04-03 17:50           ` Arnd Bergmann
2007-04-03 19:07             ` Jeremy Fitzhardinge
2007-04-03 19:42               ` Arnd Bergmann
2007-04-03 19:55                 ` Jeremy Fitzhardinge
2007-04-03 20:03                   ` H. Peter Anvin
2007-04-03 21:00                     ` Jeremy Fitzhardinge
2007-04-03 21:45                       ` H. Peter Anvin
2007-04-03 21:51                       ` Arnd Bergmann
2007-04-03 22:10                         ` H. Peter Anvin
2007-04-03 22:49                           ` Arnd Bergmann
2007-04-04  0:52                             ` H. Peter Anvin
2007-04-04 13:11                               ` Arnd Bergmann
2007-04-04 15:50                                 ` H. Peter Anvin
2007-04-03 20:50                   ` Arnd Bergmann

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=adak5wue9a4.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathiasen@gmail.com \
    /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