On Fri, Jun 14, 2019 at 01:08:44PM +0200, Greg Kurz wrote: > There are several places where CONFIG_KVM is used to guard code that > should only be built when KVM is supported. It is generally preferable > to avoid that and leave such guards in header files for improved > readability. > > In many cases, the execution of the code is also conditionned by > kvm_enabled() which expands to (0) when CONFIG_KVM is not defined. > This is likely to cause the compiler to optimize the code out, > and if it doesn't, the right way to address compiling issues is > to add stubs. > > Successfuly compile tested on x86_64 and ppc64le linux. Travis shows > this builds fine on OSX as well.
1..5 applied. Still need to look at 6..7 more closely.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: PGP signature
