On Fri, Sep 04, 2015 at 05:30:35PM +0200, Peter Zijlstra wrote: > Should I place the virt_spin_lock() thing under CONFIG_PARAVIRT (maybe > even _SPINLOCKS) such that only paravirt enabled kernels when ran on a > hypervisor that does not support paravirt patching (HyperV, VMware, > etc..) revert to the test-and-set?
Ah, CONFIG_HYPERVISOR_GUEST seems fitting, that's a prerequisite for all the PARAVIRT options too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
