Re:Linux 4.17-rc1: “We removed more lines than we added”
by rbanffy on Monday April 16, 2018 @03:14PM
(#16851838)
> writing emulation taking into account quirks
I believe quirks would be added as they are uncovered. It'd also become a form of documentation. Emulation doesn't need to be precise to be valuable - if we can test it against an emulator on a commodity machine before testing it on metal on a somewhat busy machine, it's still a win - we don't need to waste time on a real multimillion zSeries or Cray if it crashes the emulator.
Re:Linux 4.17-rc1: “We removed more lines than we added”
by littlehood on Tuesday April 17, 2018 @12:05PM
(#16859579)
That way we would be able to create integration test coverage of 100% while still being able to panic on real hardware, until all messy behaviour is implemented. It's like writing unit-test kind of integration tests which then fail when provisioned :)
Re:Linux 4.17-rc1: “We removed more lines than we added”
by rbanffy on Thursday April 19, 2018 @09:52AM
(#16875874)
Passing tests and then failing when provisioned is still better than just failing when provisioned. At least you know that it should work (and maybe does, on different variations of the hardware).
I'd recommend reading Dolphin emulator release notes for a reference how much work is required to properly emulate hardware such that actual software may run without glitches and errors even for (AFAIK) 3 hardware sets.