From: Igor Mammedov <imammedo@redhat.com>
To: Hu Tao <hutao@cn.fujitsu.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] numa: check for busy memory backend
Date: Wed, 25 Jun 2014 12:02:01 +0200 [thread overview]
Message-ID: <20140625120201.77f380a3@nial.usersys.redhat.com> (raw)
In-Reply-To: <1403687054-13682-1-git-send-email-hutao@cn.fujitsu.com>
On Wed, 25 Jun 2014 17:04:14 +0800
Hu Tao <hutao@cn.fujitsu.com> wrote:
> ..to prevent one memory backend from being used by more than one numa
> node.
>
> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
> ---
> numa.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/numa.c b/numa.c
> index e471afe..6c1c554 100644
> --- a/numa.c
> +++ b/numa.c
> @@ -279,6 +279,13 @@ 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 busy", path);
> + g_free(path);
> + exit(1);
s/1/EXIT_FAILURE/ please
> + }
> +
> memory_region_add_subregion(mr, addr, seg);
> vmstate_register_ram_global(seg);
> addr += size;
next prev parent reply other threads:[~2014-06-25 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 9:04 [Qemu-devel] [PATCH] numa: check for busy memory backend Hu Tao
2014-06-25 10:02 ` Igor Mammedov [this message]
2014-06-25 11:48 ` Markus Armbruster
2014-06-29 15:20 ` Michael S. Tsirkin
2014-06-30 5:33 ` Hu Tao
2014-06-30 6:53 ` Michael S. Tsirkin
2014-06-30 7:46 ` Hu Tao
2014-06-30 8:28 ` Michael S. Tsirkin
2014-06-30 8:48 ` Igor Mammedov
2014-06-30 9:12 ` Michael S. Tsirkin
2014-06-30 10:16 ` Hu Tao
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=20140625120201.77f380a3@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=mst@redhat.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 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).