qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: libvir-list@redhat.com, Igor Mammedov <imammedo@redhat.com>,
	qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [libvirt] [PATCH] deprecate -mem-path fallback to anonymous RAM
Date: Mon, 24 Jun 2019 10:36:55 +0100	[thread overview]
Message-ID: <20190624093655.GE17698@redhat.com> (raw)
In-Reply-To: <87blynv1lu.fsf@dusky.pond.sub.org>

On Mon, Jun 24, 2019 at 10:17:33AM +0200, Markus Armbruster wrote:
> Igor Mammedov <imammedo@redhat.com> writes:
> 
> > Fallback might affect guest or worse whole host performance
> > or functionality if backing file were used to share guest RAM
> > with another process.
> >
> > Patch deprecates fallback so that we could remove it in future
> > and ensure that QEMU will provide expected behavior and fail if
> > it can't use user provided backing file.
> >
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > PS:
> > Patch is written on top of
> >   [PATCH v4 0/3] numa: deprecate '-numa node,  mem' and default memory distribution
> > to avoid conflicts in qemu-deprecated.texi
> >
> >  numa.c               | 4 ++--
> >  qemu-deprecated.texi | 8 ++++++++
> >  2 files changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/numa.c b/numa.c
> > index 91a29138a2..53d67b8ad9 100644
> > --- a/numa.c
> > +++ b/numa.c
> > @@ -494,8 +494,8 @@ static void allocate_system_memory_nonnuma(MemoryRegion *mr, Object *owner,
> >              if (mem_prealloc) {
> >                  exit(1);
> >              }
> > -            error_report("falling back to regular RAM allocation.");
> > -
> > +            warn_report("falling back to regular RAM allocation. "
> > +                        "Fallback to RAM allocation is deprecated.");
> 
> Can we give the user clues on how to avoid the deprecated fallback?

There's nothing a user can do aside from ensuring they have sufficient
free memory before launching QEMU to satisfy the huge pag request.

Probably just needs changing to do.

    "This is deprecated, future QEMU releases will exit when
     huge pages cannot be allocated"

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 :|


  reply	other threads:[~2019-06-24  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 11:41 [Qemu-devel] [PATCH] deprecate -mem-path fallback to anonymous RAM Igor Mammedov
2019-06-20 11:52 ` Daniel P. Berrangé
2019-06-20 13:34 ` Dr. David Alan Gilbert
2019-06-24  8:17 ` Markus Armbruster
2019-06-24  9:36   ` Daniel P. Berrangé [this message]
2019-06-24 10:50     ` [Qemu-devel] [libvirt] " Igor Mammedov
2019-06-24  9:58   ` [Qemu-devel] " Igor Mammedov
2019-06-24 14:01     ` Markus Armbruster
2019-06-25 11:32       ` 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=20190624093655.GE17698@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=libvir-list@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).