From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Michal Privoznik <mprivozn@redhat.com>,
pkrempa@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
peter.maydell@linaro.org
Subject: Re: [PATCH v3] machine: add missing doc for memory-backend option
Date: Wed, 27 Jan 2021 17:56:45 +0000 [thread overview]
Message-ID: <20210127175645.GW3653144@redhat.com> (raw)
In-Reply-To: <20210127163522.5a8db09a@redhat.com>
On Wed, Jan 27, 2021 at 04:35:22PM +0100, Igor Mammedov wrote:
> On Wed, 27 Jan 2021 15:24:26 +0100
> Michal Privoznik <mprivozn@redhat.com> wrote:
>
> > On 1/27/21 11:54 AM, Daniel P. Berrangé wrote:
> > > On Wed, Jan 27, 2021 at 10:45:11AM +0000, Daniel P. Berrangé wrote:
> > >> On Thu, Jan 21, 2021 at 11:15:04AM -0500, Igor Mammedov wrote:
> >
> >
> > >>
> > >> How does a mgmt app know which machine types need to use this
> > >> option ? The machine type names are opaque strings, and apps
> > >> must not attempt to parse or interpret the version number
> > >> inside the machine type name, as they can be changed by
> > >> distros. IOW, saying to use it for machine types 4.0 and
> > >> older isn't a valid usage strategy IMHO.
> it's possible (but no necessary) to use knob with new machine types
> (defaults for these match suggested property value).
IIUC, this means that setting the property has no impact on
migration ABI for new machine types > 4.0....
> Limiting knob usage to 4.0 and older would allow us to drop
> without extra efforts once 4.0 is deprecated/removed.
...so, even if we set the property unconditionally for *all*
machine types, then we can still remove it in future, becuase
its removal won't affect ABI of the 5.x, 6.x machine types.
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 :|
next prev parent reply other threads:[~2021-01-27 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:15 [PATCH v3] machine: add missing doc for memory-backend option Igor Mammedov
2021-01-27 10:40 ` Michal Privoznik
2021-01-27 10:45 ` Daniel P. Berrangé
2021-01-27 10:54 ` Daniel P. Berrangé
2021-01-27 14:24 ` Michal Privoznik
2021-01-27 15:09 ` Daniel P. Berrangé
2021-01-27 15:35 ` Igor Mammedov
2021-01-27 17:03 ` Michal Privoznik
2021-01-27 19:31 ` Igor Mammedov
2021-01-27 17:56 ` Daniel P. Berrangé [this message]
2021-01-27 18:30 ` Michal Privoznik
2021-01-27 18:41 ` Daniel P. Berrangé
2021-01-27 19:19 ` Igor Mammedov
2021-02-04 12:21 ` Michal Privoznik
2021-02-05 15:56 ` Igor Mammedov
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=20210127175645.GW3653144@redhat.com \
--to=berrange@redhat.com \
--cc=imammedo@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).