qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] a3567b: hostmem: Ignore ENOSYS while setting


From: GitHub
Subject: [Qemu-commits] [qemu/qemu] a3567b: hostmem: Ignore ENOSYS while setting MPOL_DEFAULT
Date: Mon, 23 Nov 2015 09:30:05 -0800

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: a3567ba1e6171ef7cfad55ae549c0cd8bffb1195
      
https://github.com/qemu/qemu/commit/a3567ba1e6171ef7cfad55ae549c0cd8bffb1195
  Author: Pavel Fedin <address@hidden>
  Date:   2015-11-23 (Mon, 23 Nov 2015)

  Changed paths:
    M backends/hostmem.c

  Log Message:
  -----------
  hostmem: Ignore ENOSYS while setting MPOL_DEFAULT

Currently hostmem backend fails if CONFIG_NUMA is enabled in QEMU
(the 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 <address@hidden>
Reviewed-by: Eduardo Habkost <address@hidden>
Signed-off-by: Eduardo Habkost <address@hidden>


  Commit: 5522a841cab5f15ac0f8d207b320c21755a7a1a5
      
https://github.com/qemu/qemu/commit/5522a841cab5f15ac0f8d207b320c21755a7a1a5
  Author: Peter Maydell <address@hidden>
  Date:   2015-11-23 (Mon, 23 Nov 2015)

  Changed paths:
    M backends/hostmem.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/ehabkost/tags/numa-pull-request' into 
staging

NUMA fix for -rc2

# gpg: Signature made Mon 23 Nov 2015 12:45:34 GMT using RSA key ID 984DC5A6
# gpg: Good signature from "Eduardo Habkost <address@hidden>"

* remotes/ehabkost/tags/numa-pull-request:
  hostmem: Ignore ENOSYS while setting MPOL_DEFAULT

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/68c61282fe8a...5522a841cab5

reply via email to

[Prev in Thread] Current Thread [Next in Thread]