From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [PATCH 1/3] libxl: check whether vcpu affinity and vnuma info match Date: Tue, 24 Mar 2015 14:41:49 +0000 Message-ID: <20150324144149.GD30219@zion.uk.xensource.com> References: <20150324132630.10874.78040.stgit@Solace.station> <20150324134146.10874.3628.stgit@Solace.station> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20150324134146.10874.3628.stgit@Solace.station> 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 Cc: Wei Liu , Stefano Stabellini , Ian Jackson , Ian Campbell , Xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Mar 24, 2015 at 02:41:48PM +0100, Dario Faggioli wrote: > More specifically, vcpus are assigned to a vnode, which in > turn is associated with a pnode. If a vcpu also has, in its > (hard or soft) affinity, some pcpus that are not part of the > said pnode, print a warning to the user. > Currently all the checks that returns error are all guest visible mis-configurations. I'm trying to reason whether we should return an error or just print a warning. What is the outcome if you have conflicting setting in vNUMA and vcpu affinity? I guess it's just performance penalty but nothing guest visible could happen? Wei.