* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> 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.
something like that wont enable 100%
On Mon, 2007-10-15 at 10:08 -0700, Linus Torvalds wrote:
>
> On Mon, 15 Oct 2007, Ingo Molnar wrote:
> >
> > A further problem is probably that the GDTH timer is not stopped by a
> > failed GDTH probe?
>
> Indeed. Maybe this is a better fix?
>
> That driver is pretty messy, and this should
On Mon, 15 Oct 2007, Alan Cox wrote:
>
> For some things. I do it a bit because you can use it to fake
> failures that are tricky to do in the real world. It won't tell you the
> driver works but its suprisingly good for testing for races (forcing IRQ
> delivery at specific points), buggy
On Mon, 15 Oct 2007 12:38:06 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> 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.
For
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
* Boaz Harrosh <[EMAIL PROTECTED]> 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
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> On Mon, 15 Oct 2007, Ingo Molnar wrote:
> >
> > A further problem is probably that the GDTH timer is not stopped by a
> > failed GDTH probe?
>
> Indeed. Maybe this is a better fix?
>
> That driver is pretty messy, and this should have been found
On Mon, Oct 15 2007 at 19:57 +0200, Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Linus Torvalds wrote:
>> On Mon, 15 Oct 2007, Ingo Molnar wrote:
>>> A further problem is probably that the GDTH timer is not stopped by a
>>> failed GDTH probe?
>> Indeed. Maybe this is a better fix?
>>
>> That driver is
Linus Torvalds wrote:
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found ealier.
James? Boaz?
FWIW, the gdth
On Mon, 15 Oct 2007, Ingo Molnar wrote:
>
> A further problem is probably that the GDTH timer is not stopped by a
> failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found ealier.
James? Boaz?
Linus
---
the patch below fixes a bootup-crash bug merged via today's SCSI git
merge:
commit df3d80f5a5c74168be42788364d13cf6c83c7b9c
Merge: 3d06f7a... c8e91b0...
Author: Linus Torvalds <[EMAIL PROTECTED]>
Date: Mon Oct 15 08:19:33 2007 -0700
Merge
the patch below fixes a bootup-crash bug merged via today's SCSI git
merge:
commit df3d80f5a5c74168be42788364d13cf6c83c7b9c
Merge: 3d06f7a... c8e91b0...
Author: Linus Torvalds [EMAIL PROTECTED]
Date: Mon Oct 15 08:19:33 2007 -0700
Merge
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found ealier.
James? Boaz?
Linus
---
Linus Torvalds wrote:
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found ealier.
James? Boaz?
FWIW, the gdth
On Mon, Oct 15 2007 at 19:57 +0200, Jeff Garzik [EMAIL PROTECTED] wrote:
Linus Torvalds wrote:
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy,
* Linus Torvalds [EMAIL PROTECTED] wrote:
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found ealier.
* Boaz Harrosh [EMAIL PROTECTED] 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
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
On Mon, 15 Oct 2007 12:38:06 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
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.
For some
On Mon, 15 Oct 2007, Alan Cox wrote:
For some things. I do it a bit because you can use it to fake
failures that are tricky to do in the real world. It won't tell you the
driver works but its suprisingly good for testing for races (forcing IRQ
delivery at specific points), buggy hardware
On Mon, 2007-10-15 at 10:08 -0700, Linus Torvalds wrote:
On Mon, 15 Oct 2007, Ingo Molnar wrote:
A further problem is probably that the GDTH timer is not stopped by a
failed GDTH probe?
Indeed. Maybe this is a better fix?
That driver is pretty messy, and this should have been found
* Linus Torvalds [EMAIL PROTECTED] wrote:
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.
something like that wont enable 100% coverage (or
22 matches
Mail list logo
