qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
	mark.cave-ayland@ilande.co.uk, qemu-devel@nongnu.org,
	qemu-arm@nongnu.org, jan.kiszka@web.de, atar4qemu@gmail.com
Subject: Re: [Qemu-devel] [RFC] memory: use memory_region_init_ram() instead of memory_region_allocate_system_memory()
Date: Mon, 18 Feb 2019 10:31:38 +0100	[thread overview]
Message-ID: <20190218103138.21aa9c05@Igors-MacBook-Pro.local> (raw)
In-Reply-To: <b94c91de-5390-b04f-27d3-f183d010f730@redhat.com>

On Fri, 15 Feb 2019 19:18:50 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:

> On 15/02/19 16:42, Igor Mammedov wrote:
> >>
> >> What about -m, too?  Then you'd specify a memdev instead of the initial
> >> memory size.
> > that somewhat what I've planned,
> > make -m X translate into -object memory-backend-ram,id=magically-get-what-board-uses-now,size=X -machine memdev=thatid
> > 
> > one more reason for memdev vs device is that -numa now uses memdevs and so far it
> > doesn't look that non-numa initial RAM would get immediate benefits from using -device
> > on most boards (well, I couldn't come up with any modulo backend/frontend consistent usage)
> 
> What I meant is what about making the non-NUMA option -m memdev=thatid
> (and the automatic translation you mention too).  Yes, bikeshedding. :)
sure, I can add it,
it would be just an alias to machine.memdev


> 
> Paolo
> 

  reply	other threads:[~2019-02-18  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 14:07 [Qemu-devel] [RFC] memory: use memory_region_init_ram() instead of memory_region_allocate_system_memory() Igor Mammedov
2019-02-14 18:11 ` Paolo Bonzini
2019-02-15 11:33   ` Igor Mammedov
2019-02-15 14:48     ` Paolo Bonzini
2019-02-15 15:42       ` Igor Mammedov
2019-02-15 18:18         ` Paolo Bonzini
2019-02-18  9:31           ` Igor Mammedov [this message]
2019-02-14 18:30 ` Peter Maydell
2019-02-15 11:45   ` 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=20190218103138.21aa9c05@Igors-MacBook-Pro.local \
    --to=imammedo@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).