From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SX6Og-0008BT-BA for qemu-devel@nongnu.org; Wed, 23 May 2012 03:54:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SX6Od-000196-Rx for qemu-devel@nongnu.org; Wed, 23 May 2012 03:54:17 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48045) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SX6Od-00018F-Na for qemu-devel@nongnu.org; Wed, 23 May 2012 03:54:15 -0400 Message-ID: <1337759644.9698.49.camel@twins> From: Peter Zijlstra Date: Wed, 23 May 2012 09:54:04 +0200 In-Reply-To: <1337754751-9018-2-git-send-email-kernelfans@gmail.com> References: <1337754751-9018-1-git-send-email-kernelfans@gmail.com> <1337754751-9018-2-git-send-email-kernelfans@gmail.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/2] sched: add virt sched domain for the guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liu Ping Fan Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, qemu-devel@nongnu.org, Ingo Molnar , Avi Kivity , Anthony Liguori On Wed, 2012-05-23 at 14:32 +0800, Liu Ping Fan wrote: > From: Liu Ping Fan >=20 > The guest's scheduler can not see the numa info on the host and > this will result to the following scene: > Supposing vcpu-a on nodeA, vcpu-b on nodeB, when load balance, > the tasks' pull and push between these vcpus will cost more. But > unfortunately, currently, the guest is just blind to this. >=20 > This patch want to export the host numa info to the guest, and help > guest to rebuild its sched domain based on host's info. Hell no, we're not going to export sched domains, if kvm/qemu wants this its all in sysfs. The whole sched_domain stuff is a big enough pain as it is, exporting this and making it a sodding API is the worst thing ever.=20 Whatever brainfart made you think this is needed anyway? sysfs contains the host topology, qemu can already create whatever guest topology you want (see the -smp and -numa arguments), so what gives?