From: "Michael S. Tsirkin" <mst@redhat.com>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] numa: check for busy memory backend
Date: Mon, 30 Jun 2014 13:46:43 +0300 [thread overview]
Message-ID: <20140630104643.GA19960@redhat.com> (raw)
In-Reply-To: <1404124095-3934-1-git-send-email-hutao@cn.fujitsu.com>
On Mon, Jun 30, 2014 at 06:28:15PM +0800, Hu Tao wrote:
> Specifying the same memory backend twice leads to an assert:
>
> ./x86_64-softmmu/qemu-system-x86_64 -m 512M -enable-kvm -object
> memory-backend-ram,size=256M,id=ram0 -numa node,nodeid=0,memdev=ram0
> -numa node,nodeid=1,memdev=ram0
> qemu-system-x86_64: /scm/qemu/memory.c:1506:
> memory_region_add_subregion_common: Assertion `!subregion->container'
> failed.
> Aborted (core dumped)
>
> Detect and exit with an error message instead.
>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
Applied, thanks.
> ---
> numa.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/numa.c b/numa.c
> index 2fde740..7bf7834 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -301,6 +301,14 @@ void memory_region_allocate_system_memory(MemoryRegion *mr, Object *owner,
> exit(1);
> }
>
> + if (memory_region_is_mapped(seg)) {
> + char *path = object_get_canonical_path_component(OBJECT(backend));
> + error_report("memory backend %s is used multiple times. Each "
> + "-numa option must use a different memdev value.",
> + path);
> + exit(1);
> + }
> +
> memory_region_add_subregion(mr, addr, seg);
> vmstate_register_ram_global(seg);
> addr += size;
> --
> 1.9.3
prev parent reply other threads:[~2014-06-30 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 10:28 [Qemu-devel] [PATCH v2] numa: check for busy memory backend Hu Tao
2014-06-30 10:46 ` Michael S. Tsirkin [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=20140630104643.GA19960@redhat.com \
--to=mst@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=y-goto@jp.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.