diff options
| author | Dirk Müller <dirk@dmllr.de> | 2015-03-24 23:11:03 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-03-25 14:35:24 +0100 |
| commit | 1d5bfde1b978b57156d851d140b99eac8b2adbe4 (patch) | |
| tree | 1ffb9da2a07452947419501502137a781681fcb4 /hw/m68k/dummy_m68k.c | |
| parent | 78fa62ff1bc0d66f0115b7147c4eb260ad22022a (diff) | |
| download | qemu-1d5bfde1b978b57156d851d140b99eac8b2adbe4.zip qemu-1d5bfde1b978b57156d851d140b99eac8b2adbe4.tar.gz qemu-1d5bfde1b978b57156d851d140b99eac8b2adbe4.tar.bz2 | |
m68k: memory: Replace memory_region_init_ram with memory_region_allocate_system_memory
Commit 0b183fc871:"memory: move mem_path handling to
memory_region_allocate_system_memory" split memory_region_init_ram and
memory_region_init_ram_from_file. Also it moved mem-path handling a step
up from memory_region_init_ram to memory_region_allocate_system_memory.
Therefore for any board that uses memory_region_init_ram directly,
-mem-path is not supported.
Fix this by replacing memory_region_init_ram with
memory_region_allocate_system_memory.
Signed-off-by: Dirk Mueller <dmueller@suse.com>
Message-Id: <CAL5wTH6X-GsT1AA8kEtP_e7oZWGZgi=fCcDfSs3wLgJN30DbUw@mail.gmail.com>
Reviewed-by: Andreas Färber <afaerber@suse.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'hw/m68k/dummy_m68k.c')
| -rw-r--r-- | hw/m68k/dummy_m68k.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/hw/m68k/dummy_m68k.c b/hw/m68k/dummy_m68k.c index 278f4c0..5b77d93 100644 --- a/hw/m68k/dummy_m68k.c +++ b/hw/m68k/dummy_m68k.c @@ -42,8 +42,8 @@ static void dummy_m68k_init(MachineState *machine) env->vbr = 0; /* RAM at address zero */ - memory_region_init_ram(ram, NULL, "dummy_m68k.ram", ram_size, &error_abort); - vmstate_register_ram_global(ram); + memory_region_allocate_system_memory(ram, NULL, "dummy_m68k.ram", + ram_size); memory_region_add_subregion(address_space_mem, 0, ram); /* Load kernel. */ |