about summary refs log tree commit diff
path: root/modules/system
Commit message (Collapse)AuthorAgeFilesLines
* machines: Remove tyree and brawndoaszlig2023-09-145-88/+0
| | | | | | | | | | | | | The former no longer exists and the latter has a new hardware and it's self-managed by the owner now (which is always the best IMHO). With both machines gone, we no longer need the "managed" profile and the BFQ module that was used for the old hardware of Brawndo was no longer used anywhere else. Same with the T100HA module, since Tyree was an ASUS T100HA and apart from the module being probably very much outdated we don't have another such hardware in Vuizvui. Signed-off-by: aszlig <aszlig@nix.build>
* modules/bfq: Rebase patch against kernel 5.4aszlig2019-12-082-1/+15
| | | | | | | | | | | The patch no longer applies because the default elevator initalisation has been refactored a bit[1] in kernel 5.4. Content-wise our patch is still the same. [1]: https://github.com/torvalds/linux/commit/a0958ba7fcdc316e3900f8d2afda519850d60985 Signed-off-by: aszlig <aszlig@nix.build>
* bfq: Fix kernel config with SCSI_MQ_DEFAULTaszlig2019-03-191-1/+1
| | | | | | | This option was removed in Linux 5.0, so let's make its absence non-fatal for the build of the config. Signed-off-by: aszlig <aszlig@nix.build>
* bfq: Don't fail if DM_MQ_DEFAULT can't be enabledaszlig2018-12-251-1/+1
| | | | | | | | | | Since kernel 4.20, the option no longer exists and it's enabled unconditionally. So in order to stay backwards-compatible with older kernels, let's only enable that option if it actually exists (thus the "?"). Signed-off-by: aszlig <aszlig@nix.build>
* zswap: Drop patch for z3fold reclaim racesaszlig2018-12-041-9/+1
| | | | | | | | | | The patch got posted to the LKML a while ago and a better[1] patch[2] eventually got into stable, so we can safely drop the patch on our end. [1]: https://lore.kernel.org/patchwork/patch/959862/#1191565 [2]: https://patchwork.kernel.org/patch/10668441/ Signed-off-by: aszlig <aszlig@nix.build>
* zswap: Add patch to fix crash for z3foldaszlig2018-07-211-2/+10
| | | | | | | | | | | | | I now experienced the crash for the second time whenever my machine starts swapping. The details about the crash(es) and the corresponding fix can be found at: https://bugs.chromium.org/p/chromium/issues/detail?id=822360 When the patch lands in mainline and stable, we can revert this very commit. Signed-off-by: aszlig <aszlig@nix.build>
* modules/zswap: Fix typos in descriptionaszlig2018-07-161-4/+3
| | | | Signed-off-by: aszlig <aszlig@nix.build>
* Add module for zswapaszlig2018-07-161-0/+38
| | | | | | | | Even though these options are rather opinionated rather than generally useful, it makes sense to have an option for that because I'm going to use it for my managed machines as well. Signed-off-by: aszlig <aszlig@nix.build>
* modules/bfq: Rebase patch against kernel 4.18-rc1aszlig2018-06-222-3/+17
| | | | | | | The patch no longer applies with this kernel version because the patch context has changed. Signed-off-by: aszlig <aszlig@nix.build>
* modules/bfq: Rebase patch against kernel 4.15-rc1aszlig2017-11-302-1/+16
| | | | | | | The patch for <= 4.14 no longer applies, because elevator_get() now has an additional argument. Signed-off-by: aszlig <aszlig@nix.build>
* modules/bfq: Reintroduce SCSI_MQ_DEFAULT for 4.13aszlig2017-09-061-1/+1
| | | | | | | | | | | The change dropping the SCSI_MQ_DEFAULT option has been reverted in torvalds/linux@cbe7dfa26eee4819db7b5846181d56fd0cece0ea, so while the release canidate versions didn't have this option, the final release however does have it again. So we need to wait until 4.14 for it to become removed hopefully. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* bfq: Remove SCSI_MQ_DEFAULT option for kernel 4.13aszlig2017-07-201-4/+6
| | | | | | | This has been removed upstream and is no longer needed, see commit torvalds/linux@5c279bd9e40624f4ab6e688671026d6005b066fa. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Introduce new system.kernel.useBleedingEdge optionaszlig2017-07-201-0/+23
| | | | | | | | | | | | This dissolves the user.aszlig.system.kernel module, which was not only to stay on the latest bleeding edge kernel but also to enable BFQ. The latter has been factored out already a while ago already. Originally, I had a fully custom kernel config for mmrnmhrm and dnyarri, but it's no longer the case and thus the user.aszlig.system.kernel module is now no longer needed. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Move BFQ stuff into its dedicated moduleaszlig2017-07-062-0/+43
| | | | | | | | | 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
* modules/thinkpad: Move into modules/hardwareaszlig2016-02-231-31/+0
| | | | | | | | | | | | | We already have a directory just for hardware-specific configuration options and the module option already says "vuizvui.hardware", so it should better be consistent with the directory layout. Tested using: nix-instantiate release.nix -A machines.profpatsch.katara Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @Profpatsch
* hardware.tinkpad: module for thinkpad optionsProfpatsch2015-12-221-0/+31
|
* modules/system: Add an option to build an ISO.aszlig2015-08-131-0/+12
| | | | | | | | | | | | | | Building ISO images for all machines really doesn't make sense if we only have _one_ machine at the moment, where we really use it (kzerza). So we now have an option which can be defined for a particular machine configuration, which is then going te be excempted from the ISO building process. The latter isn't yet implemented however, only the option is here right now. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Revert new system module to enable KSM.aszlig2015-04-011-20/+0
| | | | | | | | This reverts commit fc53a72f48ae6b567e7bf9901a2bd3657853633c. Applied upstream at NixOS/nixpkgs@224ed7e. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* modules: Add a new system module to enable KSM.aszlig2015-04-011-0/+20
This is very useful if you're running a lot of the same instances of particular applications. For example virtual machines or even lots of terminals. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-01 12:45:46 +0000