qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>, Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Antonios Motakis <a.motakis@virtualopensystems.com>,
	"list@suse.de:PowerPC" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC PATCH] file ram alloc: fail if cannot preallocate
Date: Fri, 21 Feb 2014 14:22:41 +0100	[thread overview]
Message-ID: <53075321.6030505@redhat.com> (raw)
In-Reply-To: <57F80552-CE67-411F-8263-35B84A3CEA54@suse.de>

Il 21/02/2014 14:02, Alexander Graf ha scritto:
> I think it makes sense to disable any fallback for -mem-path, so that
> it always only allocates RAM pages from the -mem-path pool. But this
> is a big change from how it used to work before and thus needs to be
> properly coordinated.
>
> Paolo, Peter, any thoughts here? Version 2.0 might be a good fit for
> such a change ;).

I agree it would be nice, but as Alexey said it would be best to only 
require hugepage-backed memory for the bulk of RAM.  So I'd prefer to 
wait for memdev, and then we can just deprecate -mem-path and -mem-prealloc.

Paolo

      parent reply	other threads:[~2014-02-21 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10  6:32 [Qemu-devel] [RFC PATCH] file ram alloc: fail if cannot preallocate Alexey Kardashevskiy
2014-02-21  4:57 ` Alexey Kardashevskiy
2014-02-21  8:57   ` Alexander Graf
2014-02-21 12:56     ` Alexey Kardashevskiy
2014-02-21 13:02       ` Alexander Graf
2014-02-21 13:04         ` Alexey Kardashevskiy
2014-02-21 13:10           ` Alexander Graf
2014-02-21 13:18             ` Alexey Kardashevskiy
2014-02-21 13:22         ` Paolo Bonzini [this message]

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=53075321.6030505@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).