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.txt49
1 files changed, 10 insertions, 39 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 076a2c02adaf..d2af87ba96e1 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -386,34 +386,6 @@ Who: Tejun Heo <tj@kernel.org>
386 386
387---------------------------- 387----------------------------
388 388
389What: Support for VMware's guest paravirtuliazation technique [VMI] will be
390 dropped.
391When: 2.6.37 or earlier.
392Why: With the recent innovations in CPU hardware acceleration technologies
393 from Intel and AMD, VMware ran a few experiments to compare these
394 techniques to guest paravirtualization technique on VMware's platform.
395 These hardware assisted virtualization techniques have outperformed the
396 performance benefits provided by VMI in most of the workloads. VMware
397 expects that these hardware features will be ubiquitous in a couple of
398 years, as a result, VMware has started a phased retirement of this
399 feature from the hypervisor. We will be removing this feature from the
400 Kernel too. Right now we are targeting 2.6.37 but can retire earlier if
401 technical reasons (read opportunity to remove major chunk of pvops)
402 arise.
403
404 Please note that VMI has always been an optimization and non-VMI kernels
405 still work fine on VMware's platform.
406 Latest versions of VMware's product which support VMI are,
407 Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence
408 releases for these products will continue supporting VMI.
409
410 For more details about VMI retirement take a look at this,
411 http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html
412
413Who: Alok N Kataria <akataria@vmware.com>
414
415----------------------------
416
417What: Support for lcd_switch and display_get in asus-laptop driver 389What: Support for lcd_switch and display_get in asus-laptop driver
418When: March 2010 390When: March 2010
419Why: These two features use non-standard interfaces. There are the 391Why: These two features use non-standard interfaces. There are the
@@ -530,16 +502,6 @@ Who: Thomas Gleixner <tglx@linutronix.de>
530 502
531---------------------------- 503----------------------------
532 504
533What: old ieee1394 subsystem (CONFIG_IEEE1394)
534When: 2.6.37
535Files: drivers/ieee1394/ except init_ohci1394_dma.c
536Why: superseded by drivers/firewire/ (CONFIG_FIREWIRE) which offers more
537 features, better performance, and better security, all with smaller
538 and more modern code base
539Who: Stefan Richter <stefanr@s5r6.in-berlin.de>
540
541----------------------------
542
543What: The acpi_sleep=s4_nonvs command line option 505What: The acpi_sleep=s4_nonvs command line option
544When: 2.6.37 506When: 2.6.37
545Files: arch/x86/kernel/acpi/sleep.c 507Files: arch/x86/kernel/acpi/sleep.c
@@ -564,6 +526,16 @@ Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
564 526
565---------------------------- 527----------------------------
566 528
529What: iwlwifi disable_hw_scan module parameters
530When: 2.6.40
531Why: Hareware scan is the prefer method for iwlwifi devices for
532 scanning operation. Remove software scan support for all the
533 iwlwifi devices.
534
535Who: Wey-Yi Guy <wey-yi.w.guy@intel.com>
536
537----------------------------
538
567What: access to nfsd auth cache through sys_nfsservctl or '.' files 539What: access to nfsd auth cache through sys_nfsservctl or '.' files
568 in the 'nfsd' filesystem. 540 in the 'nfsd' filesystem.
569When: 2.6.40 541When: 2.6.40
@@ -573,4 +545,3 @@ Why: This is a legacy interface which have been replaced by a more
573Who: NeilBrown <neilb@suse.de> 545Who: NeilBrown <neilb@suse.de>
574 546
575---------------------------- 547----------------------------
576