From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: PV-vNUMA issue: topology is misinterpreted by the guest Date: Mon, 27 Jul 2015 16:13:14 +0100 Message-ID: <55B64A8A.7040200@citrix.com> References: <1437042762.28251.18.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZJk5t-0006cx-S2 for xen-devel@lists.xenproject.org; Mon, 27 Jul 2015 15:13:33 +0000 In-Reply-To: <1437042762.28251.18.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli , "xen-devel@lists.xenproject.org" Cc: Elena Ufimtseva , Wei Liu , Andrew Cooper , Jan Beulich , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 16/07/15 11:32, Dario Faggioli wrote: > > Anyway, is there anything we can do to fix or workaround things? This thread has gotten a bit long... For Linux I would like to see: 1. No support for NUMA in PV guests -- if you want new MM features in a guest use HVM. 2. For HVM guests, use the existing hardware interfaces to present NUMA topology. i.e., CPUID, ACPI tables etc. This will work for both kernel and userspace and both will see the same topology. This also has the advantage that any hypervisor/toolstack work will also be applicable to other guests (e.g., Windows). David