On Wed, Jul 12, 2017 at 10:22:33AM +0200, Thomas Huth wrote: > We don't want to carry along old machine types forever. If we are able to > remove the pc machines up to 0.13 one day for example, this would allow > us to eventually kill the code for rombar=0 (i.e. where QEMU copies ROM > BARs directly to low memory). Everything up to pc-1.2 is also known to > have issues with migration. So let's start with a deprecation message > for the old machine types so that the (hopefully) few users of these old > systems start switching over to newer machine types instead.
I think we must document & agree on our support policy for machine types, before we start marking them as deprecated. eg please consider the following document before accepting this deprecation patch: https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg00652.html Note in that proposal there, I say we do *not* go through trouble of explicitly marking machines as deprecated. We just document upfront the intended lifecycle and then delete them when it is done. Just use deprecation warnings for things where there is no predictable lifecycle upfront. > > Signed-off-by: Thomas Huth <th...@redhat.com> > --- > Note: Even if we mark all these old machines as deprecated, this ofcourse > doesn't mean that we also have to remove them all at once later when we > decide to finally really remove some. We could then also start by removing > 0.10 and 0.11 only, for example (since there should really be no users left > for these), or only up to 0.13 (to be able to kill rombar=0). > > v3: > - Use a more generic approach by introducing a "deprecation_msg" in the > MachineClass instead. > > v2: > - Deprecate machines up to pc-1.2 > > hw/i386/pc_piix.c | 1 + > include/hw/boards.h | 1 + > vl.c | 4 ++++ > 3 files changed, 6 insertions(+) Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
