From: Igor Mammedov <imammedo@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: pbonzini@redhat.com, pkrempa@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] machine: add missing doc for memory-backend option
Date: Wed, 20 Jan 2021 11:20:50 +0100 [thread overview]
Message-ID: <20210120112050.2eecf7c4@redhat.com> (raw)
In-Reply-To: <d3bb0b7d-6c1f-90d9-1bd9-a89eef994462@redhat.com>
On Fri, 15 Jan 2021 10:36:05 +0100
Michal Privoznik <mprivozn@redhat.com> wrote:
> On 1/15/21 12:46 AM, 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.
> >
> > 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>)
> > ---
> > backends/hostmem.c | 10 ++++++++++
> > qemu-options.hx | 28 +++++++++++++++++++++++++++-
> > 2 files changed, 37 insertions(+), 1 deletion(-)
> >
>
>
> > @@ -96,6 +97,31 @@ SRST
> > ``hmat=on|off``
> > Enables or disables ACPI Heterogeneous Memory Attribute Table
> > (HMAT) support. The default is off.
> > +
> > + ``memory-backend='id'``
> > + An alternative to legacy ``-mem-path`` and ``mem-prealloc`` options.
> > + Allows to use a memory backend as main RAM.
> > +
> > + For example:
> > + ::
> > + -object memory-backend-file,id=pc.ram,size=512M,mem-path=/hugetlbfs,prealloc=on,share=on
> > + -machine memory-backend=pc.ram
> > + -m 512M
> > +
> > + Migration compatibility note:
> > + a) as backend id one shall use value of 'default-ram-id', advertised by
> > + machine type (available via ``query-machines`` QMP command)
> > + b) for machine types 4.0 and older, user shall
> > + use ``x-use-canonical-path-for-ramblock-id=on`` backend option
> > + (this option must be considered stable, as if it didn't have the 'x-'
> > + prefix including deprecation period, as long as 4.0 and older machine
> > + types exists),
> > + if migration to/from old QEMU (<5.0) is expected.
> > + For example:
> > + ::
> > + -object memory-backend-ram,id=pc.ram,size=512M,x-use-canonical-path-for-ramblock-id=on
> > + -machine memory-backend=pc.ram
> > + -m 512M
>
> Igor, this doesn't correspond with your comment in bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1836043#c31
>
> In fact, we had to turn the attribute OFF so that canonical path is not
> used. Isn't ON the default state anyway?
indeed, it should be 'off',
>
> Michal
>
>
next prev parent reply other threads:[~2021-01-20 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 23:46 [PATCH v2] machine: add missing doc for memory-backend option Igor Mammedov
2021-01-15 9:36 ` Michal Privoznik
2021-01-20 10:20 ` Igor Mammedov [this message]
2021-01-15 10:02 ` Peter Maydell
2021-01-15 10:43 ` Peter Krempa
2021-01-15 10:56 ` Peter Krempa
2021-01-20 13:51 ` 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=20210120112050.2eecf7c4@redhat.com \
--to=imammedo@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--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).