Setting pinning policy for vcpu which exceed current vcpus number
makes no sense, and it could cause problem for APIs which
associate the vcpu thread id with cgroup.
---
src/conf/domain_conf.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/conf/domain_conf.c
On 10/10/2012 01:14 PM, Osier Yang wrote:
Setting pinning policy for vcpu which exceed current vcpus number
makes no sense, and it could cause problem for APIs which
associate the vcpu thread id with cgroup.
---
src/conf/domain_conf.c |4 ++--
1 files changed, 2 insertions(+), 2
On 2012年10月10日 22:59, Martin Kletzander wrote:
On 10/10/2012 01:14 PM, Osier Yang wrote:
Setting pinning policy for vcpu which exceed current vcpus number
makes no sense, and it could cause problem for APIs which
associate the vcpu thread id with cgroup.
---
src/conf/domain_conf.c |4 ++--