Features/Version3.0: Difference between revisions
(Start a page for brainstorming version 3.0 features) |
(Split the list in parts that are likely doable and the ones that likely need more discussion first) |
||
| Line 1: | Line 1: | ||
Note: This page is used to gather ideas about what we could do when switching to the next major version of QEMU, i.e. version 3.0. The ideas here are by no means mandatory - it is rather meant as a base for discussion. | Note: This page is used to gather ideas about what we could do when switching to the next major version of QEMU, i.e. version 3.0. The ideas here are by no means mandatory - it is rather meant as a base for discussion. | ||
So for version 3.0, we | So for version 3.0, we very likely should do the following: | ||
* Make sure that we remove all deprecated interfaces and features that are marked accordingly in the qemu-doc deprecation chapter (see https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features for details) | * Make sure that we remove all deprecated interfaces and features that are marked accordingly in the qemu-doc deprecation chapter (see https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features for details) | ||
* Use "--accel kvm:hax:tcg" by default instead of running in TCG mode by default | * Use "--accel kvm:hax:tcg" by default instead of running in TCG mode by default | ||
Controversial ideas that likely need some discussion first: | |||
* Get rid of some really, really old and very likely completely unused machine types, like pc-0.10 and pc-0.11 | * Get rid of some really, really old and very likely completely unused machine types, like pc-0.10 and pc-0.11 | ||
* | * Remove some code which is likely hardly used anymore and where we do not have an active maintainer since years? Especially if we do not have an "make check" regression test for it. (i.e. did anybody test the bluetooth code in the recent years?) | ||
* | * Stop supporting SDL 1.2 and GTK2 ? | ||
Revision as of 10:54, 23 November 2017
Note: This page is used to gather ideas about what we could do when switching to the next major version of QEMU, i.e. version 3.0. The ideas here are by no means mandatory - it is rather meant as a base for discussion.
So for version 3.0, we very likely should do the following:
- Make sure that we remove all deprecated interfaces and features that are marked accordingly in the qemu-doc deprecation chapter (see https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features for details)
- Use "--accel kvm:hax:tcg" by default instead of running in TCG mode by default
Controversial ideas that likely need some discussion first:
- Get rid of some really, really old and very likely completely unused machine types, like pc-0.10 and pc-0.11
- Remove some code which is likely hardly used anymore and where we do not have an active maintainer since years? Especially if we do not have an "make check" regression test for it. (i.e. did anybody test the bluetooth code in the recent years?)
- Stop supporting SDL 1.2 and GTK2 ?