search for: paravirt_cpu

...fig index 97d4f92..ebed686 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -527,20 +527,6 @@ config KVM_GUEST This option enables various optimizations for running under the KVM hypervisor. -config KVM_IODELAY - bool "KVM IO-delay support" - depends on KVM_GUEST - select PARAVIRT_CPU - ---help--- - Usually we wait for PIO access to complete. When inside KVM there's - no need to do that, as we know that we're not going through a bus, - but process PIO requests instantly. - - This option disables PIO waits, but drags in CPU-bound pv-ops. Thus - you will probably...

...fig index 97d4f92..ebed686 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -527,20 +527,6 @@ config KVM_GUEST This option enables various optimizations for running under the KVM hypervisor. -config KVM_IODELAY - bool "KVM IO-delay support" - depends on KVM_GUEST - select PARAVIRT_CPU - ---help--- - Usually we wait for PIO access to complete. When inside KVM there's - no need to do that, as we know that we're not going through a bus, - but process PIO requests instantly. - - This option disables PIO waits, but drags in CPU-bound pv-ops. Thus - you will probably...

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This