numa: remove deprecated -mem-path fallback to anonymous RAM
it has been deprecated since 4.0 by commit
cb79224b7
(deprecate -mem-path fallback to anonymous RAM)
Deprecation period ran out and it's time to remove it
so it won't get in a way of switching to using hostmem
backend for RAM.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20200219160953.13771-2-imammedo@redhat.com>
This commit is contained in:
parent
6c599282f8
commit
68a86dc15c
@ -784,24 +784,8 @@ static void allocate_system_memory_nonnuma(MemoryRegion *mr, Object *owner,
|
|||||||
{
|
{
|
||||||
if (mem_path) {
|
if (mem_path) {
|
||||||
#ifdef __linux__
|
#ifdef __linux__
|
||||||
Error *err = NULL;
|
|
||||||
memory_region_init_ram_from_file(mr, owner, name, ram_size, 0, 0,
|
memory_region_init_ram_from_file(mr, owner, name, ram_size, 0, 0,
|
||||||
mem_path, &err);
|
mem_path, &error_fatal);
|
||||||
if (err) {
|
|
||||||
error_report_err(err);
|
|
||||||
if (mem_prealloc) {
|
|
||||||
exit(1);
|
|
||||||
}
|
|
||||||
warn_report("falling back to regular RAM allocation");
|
|
||||||
error_printf("This is deprecated. Make sure that -mem-path "
|
|
||||||
" specified path has sufficient resources to allocate"
|
|
||||||
" -m specified RAM amount\n");
|
|
||||||
/* Legacy behavior: if allocation failed, fall back to
|
|
||||||
* regular RAM allocation.
|
|
||||||
*/
|
|
||||||
mem_path = NULL;
|
|
||||||
memory_region_init_ram_nomigrate(mr, owner, name, ram_size, &error_fatal);
|
|
||||||
}
|
|
||||||
#else
|
#else
|
||||||
fprintf(stderr, "-mem-path not supported on this host\n");
|
fprintf(stderr, "-mem-path not supported on this host\n");
|
||||||
exit(1);
|
exit(1);
|
||||||
|
@ -113,15 +113,6 @@ QEMU using implicit generic or board specific splitting rule.
|
|||||||
Use @option{memdev} with @var{memory-backend-ram} backend or @option{mem} (if
|
Use @option{memdev} with @var{memory-backend-ram} backend or @option{mem} (if
|
||||||
it's supported by used machine type) to define mapping explictly instead.
|
it's supported by used machine type) to define mapping explictly instead.
|
||||||
|
|
||||||
@subsection -mem-path fallback to RAM (since 4.1)
|
|
||||||
Currently if guest RAM allocation from file pointed by @option{mem-path}
|
|
||||||
fails, QEMU falls back to allocating from RAM, which might result
|
|
||||||
in unpredictable behavior since the backing file specified by the user
|
|
||||||
is ignored. In the future, users will be responsible for making sure
|
|
||||||
the backing storage specified with @option{-mem-path} can actually provide
|
|
||||||
the guest RAM configured with @option{-m} and QEMU will fail to start up if
|
|
||||||
RAM allocation is unsuccessful.
|
|
||||||
|
|
||||||
@subsection RISC-V -bios (since 4.1)
|
@subsection RISC-V -bios (since 4.1)
|
||||||
|
|
||||||
QEMU 4.1 introduced support for the -bios option in QEMU for RISC-V for the
|
QEMU 4.1 introduced support for the -bios option in QEMU for RISC-V for the
|
||||||
|
Loading…
Reference in New Issue
Block a user