qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] backends/hostmem: Ignore ENOSYS while setting MPOL_DEFAULT
Date: Tue, 27 Oct 2015 15:31:34 -0200	[thread overview]
Message-ID: <20151027173134.GJ4180@thinpad.lan.raisama.net> (raw)
In-Reply-To: <000201d110b6$34ecc700$9ec65500$@samsung.com>

On Tue, Oct 27, 2015 at 03:51:31PM +0300, Pavel Fedin wrote:
> Currently hostmem backend fails if CONFIG_NUMA is enabled for the qemu
> (default), but NUMA is not supported by the kernel. This makes it
> impossible to use ivshmem in such configurations.
> 
> This patch fixes the problem by ignoring ENOSYS error if policy is set to
> MPOL_DEFAULT. This way the code behaves in the same way as if CONFIG_NUMA
> was not defined. qemu will still fail if the user specifies some other
> policy, so that the user knows it.
> 
> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

Thanks. Applied to numa tree, with the following indentation fix:

diff --git a/backends/hostmem.c b/backends/hostmem.c
index 94a4ac0..1b4eb45 100644
--- a/backends/hostmem.c
+++ b/backends/hostmem.c
@@ -315,7 +315,7 @@ host_memory_backend_memory_complete(UserCreatable *uc, Error **errp)
                   maxnode ? backend->host_nodes : NULL, maxnode + 1, flags)) {
             if (backend->policy != MPOL_DEFAULT || errno != ENOSYS) {
                 error_setg_errno(errp, errno,
-                             "cannot bind memory to host NUMA nodes");
+                                 "cannot bind memory to host NUMA nodes");
                 return;
             }
         }

> ---
>  backends/hostmem.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/backends/hostmem.c b/backends/hostmem.c
> index 41ba2af..94a4ac0 100644
> --- a/backends/hostmem.c
> +++ b/backends/hostmem.c
> @@ -313,9 +313,11 @@ host_memory_backend_memory_complete(UserCreatable *uc, Error **errp)
>          assert(maxnode <= MAX_NODES);
>          if (mbind(ptr, sz, backend->policy,
>                    maxnode ? backend->host_nodes : NULL, maxnode + 1, flags)) {
> -            error_setg_errno(errp, errno,
> +            if (backend->policy != MPOL_DEFAULT || errno != ENOSYS) {
> +                error_setg_errno(errp, errno,
>                               "cannot bind memory to host NUMA nodes");
> -            return;
> +                return;
> +            }
>          }
>  #endif
>          /* Preallocate memory after the NUMA policy has been instantiated.
> -- 
> 1.9.5.msysgit.0
> 
> 

-- 
Eduardo

  parent reply	other threads:[~2015-10-27 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 12:51 [Qemu-devel] [PATCH] backends/hostmem: Ignore ENOSYS while setting MPOL_DEFAULT Pavel Fedin
2015-10-27 12:53 ` Pavel Fedin
2015-10-27 17:31 ` Eduardo Habkost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-27 12:11 Pavel Fedin
2015-10-27 12:28 ` Paolo Bonzini

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=20151027173134.GJ4180@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).