about summary refs log tree commit diff
path: root/tests/system
Commit message (Collapse)AuthorAgeFilesLines
* tests/bfq: Don't test on bleeding edge kernelaszlig2018-10-031-1/+1
| | | | | | | | | | | | If someone is going to use our patch for the latest release canidate kernel and it doesn't work I'd say it's somewhat expected. Right now the test fails with the current 4.19-rc6 and I don't have time to investigate this. It might be the case that this also might be an upstream issue, but let's actually lazy evaluate this and re-check once 4.19 is released. Signed-off-by: aszlig <aszlig@nix.build>
* tests/bfq: Use SCSI disk interfaceaszlig2017-09-061-1/+2
| | | | | | | | | Using the virtio disk interface isn't very suitable for real-world simulation, so let's use the SCSI interface, because SATA is exposed to userland as a SCSI device. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @devhell
* tests/bfq: Use bleeding edge kernelaszlig2017-07-201-1/+1
| | | | | | | | IMHO it makes more sense to use the latest rc kernel instead of the latest stable kernel to run this test, because what we're actually testing here is whether our bfq-by-default.patch is working. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Move BFQ stuff into its dedicated moduleaszlig2017-07-061-0/+13
Not everybody likes to have the latest release canidate kernel, so we now have an option called vuizvui.system.kernel.bfq.enable, which *only* enables the BFQ scheduler per default. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @devhell