aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt30
1 files changed, 30 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index ea401495528d..db205276bb53 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -538,3 +538,33 @@ Why: Duplicate functionality with the gspca_zc3xx driver, zc0301 only
538 sensors) wich are also supported by the gspca_zc3xx driver 538 sensors) wich are also supported by the gspca_zc3xx driver
539 (which supports 53 USB-ID's in total) 539 (which supports 53 USB-ID's in total)
540Who: Hans de Goede <hdegoede@redhat.com> 540Who: Hans de Goede <hdegoede@redhat.com>
541
542----------------------------
543
544What: KVM memory aliases support
545When: July 2010
546Why: 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.
551Who: Avi Kivity <avi@redhat.com>
552
553----------------------------
554
555What: KVM kernel-allocated memory slots
556When: July 2010
557Why: 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.
561Who: Avi Kivity <avi@redhat.com>
562
563----------------------------
564
565What: KVM paravirt mmu host support
566When: January 2011
567Why: 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.
570Who: Avi Kivity <avi@redhat.com>