From: Ingo Molnar <mingo@elte.hu>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Linus Torvalds <torvalds@linux-foundation.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 21:27:03 +0200 [thread overview]
Message-ID: <20071015192703.GA7279@elte.hu> (raw)
In-Reply-To: <4713B4E7.2050001@panasas.com>
* Boaz Harrosh <bharrosh@panasas.com> wrote:
> > Honestly, the driver is probably rarely run by people that lack the
> > hardware, I bet...
>
> It was all "flight by instruments only". I called for HW testers and
> none came forward. All these changes, apart from "successful downgrade
> to messy" where also needed in order to push important changes to
> scsi.
>
> But a little bird said that QEMU might simulate this HW. SO I guess it
> is QEMU time for me.
heh. Incidentally i was thinking about using KVM for automated testing.
Important pieces of hardware should get an in-KVM simulator/emulator,
that way developers who do not own that hardware can do functionality
testing too. So basically the highest-quality drivers would have an
"inverse driver" in KVM, which simulates the hardware. (that model is
evidently useful to the hardware maker even for new hardware: it can
then also be used to test the Linux compatibility and Linux performance
of future planned releases of the hardware, etc.)
Ingo
next prev parent reply other threads:[~2007-10-15 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:55 [patch] scsi: fix crash in gdth_timeout() 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 [this message]
2007-10-15 19:38 ` Linus Torvalds
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=20071015192703.GA7279@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@SteelEye.com \
--cc=bharrosh@panasas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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