From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3] hw/i386: Deprecate the machines pc-0.10 to pc-1.2
Date: Wed, 12 Jul 2017 17:26:00 -0300 [thread overview]
Message-ID: <20170712202600.GO6020@localhost.localdomain> (raw)
In-Reply-To: <20170712150400.GH5237@redhat.com>
On Wed, Jul 12, 2017 at 04:04:00PM +0100, Daniel P. Berrange wrote:
> 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.
I'd bet most people won't read the deprecation policy
documentation, and a deprecation warning for 1 or 2 releases
would be still useful before we finally remove a machine-type.
--
Eduardo
next prev parent reply other threads:[~2017-07-12 20:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 8:22 [Qemu-devel] [PATCH v3] hw/i386: Deprecate the machines pc-0.10 to pc-1.2 Thomas Huth
2017-07-12 13:31 ` Gerd Hoffmann
2017-07-12 14:51 ` Eduardo Habkost
2017-07-12 15:17 ` Michael S. Tsirkin
2017-07-12 20:15 ` Eduardo Habkost
2017-07-12 20:31 ` Michael S. Tsirkin
2017-07-12 20:56 ` Eduardo Habkost
2017-07-12 22:27 ` Michael S. Tsirkin
2017-07-13 0:23 ` Laszlo Ersek
2017-07-13 0:45 ` Michael S. Tsirkin
2017-07-13 0:47 ` Michael S. Tsirkin
2017-07-13 15:17 ` Eduardo Habkost
2017-07-13 15:34 ` Laszlo Ersek
2017-07-13 22:41 ` Michael S. Tsirkin
2017-07-14 15:40 ` Eduardo Habkost
2017-07-13 15:24 ` Eric Blake
2017-07-12 15:45 ` Markus Armbruster
2017-07-12 17:48 ` Eduardo Habkost
2017-07-12 15:04 ` Daniel P. Berrange
2017-07-12 16:00 ` Thomas Huth
2017-07-12 16:12 ` Daniel P. Berrange
2017-07-12 16:23 ` Thomas Huth
2017-07-12 16:32 ` Daniel P. Berrange
2017-07-12 16:23 ` Paolo Bonzini
2017-07-12 16:29 ` Daniel P. Berrange
2017-07-12 20:37 ` Eduardo Habkost
2017-07-13 23:14 ` Michael S. Tsirkin
2017-07-14 16:33 ` Eduardo Habkost
2017-07-12 20:26 ` Eduardo Habkost [this message]
2017-07-13 0:30 ` Laszlo Ersek
2017-07-13 0:47 ` Michael S. Tsirkin
2017-07-13 1:02 ` Laszlo Ersek
2017-07-13 1:00 ` Michael S. Tsirkin
2017-07-13 15:20 ` Eduardo Habkost
2017-07-13 23:04 ` Michael S. Tsirkin
2017-07-14 5:37 ` Thomas Huth
2017-07-14 9:50 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170712202600.GO6020@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=berrange@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).