Commit db358796d95886f9715d1c91e9ae866c005511d7

Authored by Avi Kivity
Committed by Marcelo Tosatti
1 parent d380a5e402

KVM: Plan obsolescence of kernel allocated slots, paravirt mmu

These features are unused by modern userspace and can go away.  Paravirt
mmu needs to stay a little longer for live migration.

Signed-off-by: Avi Kivity <avi@redhat.com>

Showing 1 changed file with 30 additions and 0 deletions Side-by-side Diff

Documentation/feature-removal-schedule.txt
... ... @@ -538,4 +538,34 @@
538 538 sensors) wich are also supported by the gspca_zc3xx driver
539 539 (which supports 53 USB-ID's in total)
540 540 Who: Hans de Goede <hdegoede@redhat.com>
  541 +
  542 +----------------------------
  543 +
  544 +What: KVM memory aliases support
  545 +When: July 2010
  546 +Why: Memory aliasing support is used for speeding up guest vga access
  547 + through the vga windows.
  548 +
  549 + Modern userspace no longer uses this feature, so it's just bitrotted
  550 + code and can be removed with no impact.
  551 +Who: Avi Kivity <avi@redhat.com>
  552 +
  553 +----------------------------
  554 +
  555 +What: KVM kernel-allocated memory slots
  556 +When: July 2010
  557 +Why: Since 2.6.25, kvm supports user-allocated memory slots, which are
  558 + much more flexible than kernel-allocated slots. All current userspace
  559 + supports the newer interface and this code can be removed with no
  560 + impact.
  561 +Who: Avi Kivity <avi@redhat.com>
  562 +
  563 +----------------------------
  564 +
  565 +What: KVM paravirt mmu host support
  566 +When: January 2011
  567 +Why: The paravirt mmu host support is slower than non-paravirt mmu, both
  568 + on newer and older hardware. It is already not exposed to the guest,
  569 + and kept only for live migration purposes.
  570 +Who: Avi Kivity <avi@redhat.com>