From: Michal Privoznik <mprivozn@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pkrempa@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v3] machine: add missing doc for memory-backend option
Date: Wed, 27 Jan 2021 11:40:45 +0100 [thread overview]
Message-ID: <5786708e-002c-f919-5586-d8d09d40bb0f@redhat.com> (raw)
In-Reply-To: <20210121161504.1007247-1-imammedo@redhat.com>
On 1/21/21 5:15 PM, Igor Mammedov wrote:
> Add documentation for '-machine memory-backend' CLI option and
> how to use it.
>
> And document that x-use-canonical-path-for-ramblock-id,
> is considered to be stable to make sure it won't go away by accident.
>
> x- was intended for unstable/iternal properties, and not supposed to
> be stable option. However it's too late to rename (drop x-)
> it as it would mean that users will have to mantain both
> x-use-canonical-path-for-ramblock-id (for QEMU 5.0-5.2) versions
> and prefix-less for later versions.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
> v2:
> - add doc that x-use-canonical-path-for-ramblock-id is considered stable,
> (Peter Krempa <pkrempa@redhat.com>)
> v3:
> - s/x-use-canonical-path-for-ramblock-id=on/x-use-canonical-path-for-ramblock-id=off/
> (Michal Privoznik <mprivozn@redhat.com>)
> - add to commit message why x- prefix is preserved
> - drop clause about x-use-canonical-path-for-ramblock-id being stable
> from help section, but keep it in code comment above
> x-use-canonical-path-for-ramblock-id property. It's sufficient
> to prevent option being changed/removed by accident.
> (Peter Maydell <peter.maydell@linaro.org>)
> ---
> backends/hostmem.c | 10 ++++++++++
> qemu-options.hx | 26 +++++++++++++++++++++++++-
> 2 files changed, 35 insertions(+), 1 deletion(-)
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Michal
next prev parent reply other threads:[~2021-01-27 10:42 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 [this message]
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é
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=5786708e-002c-f919-5586-d8d09d40bb0f@redhat.com \
--to=mprivozn@redhat.com \
--cc=imammedo@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).