Well you can already do whatever proprietary stuff you want with your own kernels if you're not putting them on devices that you sell to people. In practice, th

Well you can already do whatever proprietary stuff you want with your own kernels if you're not putting them on devices that you sell to people. In practice, this means that Amazon, Google, etc likely have pretty fancy, totally unshared scheduler changes that are worth a significant amount of money. [0] As for the risk of selling something with proprietary scheduler bits, the upshot is that this is well handled, because most of the interfaces are GPL-only. IANAL, but this [1] is probably an interesting read. [0] btw, more often than not the reason that these things don't go upstream is because upstream says "no." Even if such changes are worth a lot of money to the business, it's not enough that the competitive advantage outweighs the maintenance cost of a forked scheduler [1] https://lore.kernel.org/netdev/20210916032104.35822-1-alexei.starovoitov@gmail.com/ https://lore.kernel.org/netdev/20210916032104.35822-1-alexei...