[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-arm] [Qemu-devel] [RFC] memory: use memory_region_init_ram() i
From: |
Igor Mammedov |
Subject: |
Re: [Qemu-arm] [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 |
On Fri, 15 Feb 2019 19:18:50 +0100
Paolo Bonzini <address@hidden> 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
>
Re: [Qemu-arm] [RFC] memory: use memory_region_init_ram() instead of memory_region_allocate_system_memory(), Peter Maydell, 2019/02/14