mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org,
	James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [patch] scsi: fix crash in gdth_timeout()
Date: Mon, 15 Oct 2007 12:38:06 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0710151232430.6887@woody.linux-foundation.org> (raw)
In-Reply-To: <20071015192703.GA7279@elte.hu>



On Mon, 15 Oct 2007, Ingo Molnar wrote:
> 
> heh. Incidentally i was thinking about using KVM for automated testing. 

Using emulators to test device drivers is almost certain to be pointless.

The problem with device drivers tends to be timing issues, odd hardware 
interactions, and lots of strange (and sometimes undocumented) behaviour 
and dependencies (eg things like "you have to wait 50us after setting the 
reset bit until the hardware has actually reset").

These are all things that you'd generally not catch in emulation - because 
the emulation by necessity is only going to be a very weak picture of the 
real thing.

So I suspect you can find the easy stuff, but only by writing insanely 
complex device model descriptions in the emulator environment itself, and 
only for those device models that have actually been written.

Can it be donein theory? Sure. Practically? Not so sure. Would it help? I 
suspect the effort to do the device model would be many times bigger than 
*any* conceivable effort to just fix the driver bugs as they get found 
through other means.

So we could perhaps have *really* good emulated hardware for a few models 
of hw out there, but likely they'd be fewer and less varied platforms than 
most kernel developers end up having hidden under their desk anyway.. 

			Linus

  reply	other threads:[~2007-10-15 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 16:55 Ingo Molnar
2007-10-15 17:08 ` Linus Torvalds
2007-10-15 17:57   ` Jeff Garzik
2007-10-15 18:43     ` Boaz Harrosh
2007-10-15 19:27       ` Ingo Molnar
2007-10-15 19:38         ` Linus Torvalds [this message]
2007-10-15 20:08           ` Alan Cox
2007-10-15 20:15             ` Linus Torvalds
2007-10-15 22:23           ` Ingo Molnar
2007-10-15 19:24   ` Ingo Molnar
2007-10-15 21:55   ` James Bottomley

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=alpine.LFD.0.999.0710151232430.6887@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bharrosh@panasas.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®