From: Peter Zijlstra <peterz@infradead.org>
To: Liu ping fan <kernelfans@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
qemu-devel@nongnu.org, Ingo Molnar <mingo@redhat.com>,
Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH 1/2] sched: add virt sched domain for the guest
Date: Wed, 23 May 2012 10:23:22 +0200 [thread overview]
Message-ID: <1337761402.9698.62.camel@twins> (raw)
In-Reply-To: <CAFgQCTvhVs8-onz3huovYe=StOYJe2pJO-nka_7KogSju6AttQ@mail.gmail.com>
On Wed, 2012-05-23 at 16:10 +0800, Liu ping fan wrote:
> the movement of vcpu
> threads among host nodes will break the topology initialized by -numa
> option.
You want to remap vcpu to nodes? Are you bloody insane? cpu:node maps
are assumed static, you cannot make that a dynamic map and pray things
keep working.
Also, have you any idea how expensive it is to rebuild the topology vs
migrating the vcpu?
next prev parent reply other threads:[~2012-05-23 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 6:32 [Qemu-devel] [RFC] kvm: export host NUMA info to guest's scheduler Liu Ping Fan
2012-05-23 6:32 ` [Qemu-devel] [PATCH 1/2] sched: add virt sched domain for the guest Liu Ping Fan
2012-05-23 7:54 ` Peter Zijlstra
2012-05-23 8:10 ` Liu ping fan
2012-05-23 8:23 ` Peter Zijlstra [this message]
2012-05-23 8:34 ` Liu ping fan
2012-05-23 8:48 ` Peter Zijlstra
2012-05-23 9:58 ` Liu ping fan
2012-05-23 10:14 ` Peter Zijlstra
2012-05-23 15:23 ` Dave Hansen
2012-05-23 15:52 ` Peter Zijlstra
2012-05-23 6:32 ` [Qemu-devel] [PATCH 2/2] sched: add virt domain device's driver Liu Ping Fan
2012-05-23 6:32 ` [Qemu-devel] [PATCH] kvm: collect vcpus' numa info for guest's scheduler Liu Ping Fan
2012-05-23 6:32 ` [Qemu-devel] [PATCH] Qemu: add virt sched domain device Liu Ping Fan
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=1337761402.9698.62.camel@twins \
--to=peterz@infradead.org \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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).