Received: by 2002:a25:5b86:0:0:0:0:0 with SMTP id p128csp1630839ybb; Fri, 29 Mar 2019 08:14:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqyIlg5qfzRhR+YrBNcoJ3kr4cDlJ+dSr42VFKRntkr9RA9Tiwg3AQQ9RhwAELfoBYpGxk0i X-Received: by 2002:a17:902:ab95:: with SMTP id f21mr49711408plr.188.1553872442245; Fri, 29 Mar 2019 08:14:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553872442; cv=none; d=google.com; s=arc-20160816; b=xO2okEnodY+fYMC5hkDJhVkTg2HukiAq3wZGW47OeQoids4hxGFMra2LeXGKbxuh8/ L9dF8pDr3LMKYkXqdTOe8EsFybOk+gZJAGnQmm6WMzYbSRrqVqdWLk4yXPPFYGlh4S7Y s8mL/NLqJ2YBbbTc4D7IVgIxzvkj7DiCXp5sZopxdoQvu5+ypOqUyzxEFpd1kDspH9CE 3u7pK2MlLN59+l6KMtk3RzcGrfPVTOP1ikICE/aQQefQzmw1Uao3Bj8ukl14OotP92Nv d/hbY1cUyBgw/qxObczMROCiYB8utlgu8VqZN22oqyIZXcoLj0UWY1LNwqD9R1T0879F upGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:mime-version:in-reply-to:references :subject:cc:to:from:date:message-id; bh=zv0110l3msn0T+BDqDJVlAWZIFlUbXH7tAxALR+CE90=; b=MpCV5nV2nqYdXV5tSwVQ5vj12svtfS11CyjXyxCqNlI5eEpZDrIson/E1DzWBKZfj/ Ubsfuhr4a/ZcY5IJVNSeXDGrrKDQQi01FDJDIMh0zVdM1r+tlK5y+mfp81PBMDF8kVIa pqbzJZrBw265rywhu0jbTlyElvVHBVPM6H0r2E7ZUfMUCZwSmLc2uEo5Nv1rWeHYVr98 1qYfM41eTDEzYkn6lNpyxE5tFLBbUeXKuIzA1oXFLIP7mW8kpntXJMnYWS1WCQcVE+TI yZFYv2Pmzxf2dAXTrntq9w9gquVe+ZiQmM+7EVS+SC5Gz7G67Jcz7z3JquChiJwXpa35 HtMw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t17si1988190pfe.250.2019.03.29.08.13.46; Fri, 29 Mar 2019 08:14:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729486AbfC2PMx convert rfc822-to-8bit (ORCPT + 99 others); Fri, 29 Mar 2019 11:12:53 -0400 Received: from prv1-mh.provo.novell.com ([137.65.248.33]:59014 "EHLO prv1-mh.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728903AbfC2PMw (ORCPT ); Fri, 29 Mar 2019 11:12:52 -0400 Received: from INET-PRV1-MTA by prv1-mh.provo.novell.com with Novell_GroupWise; Fri, 29 Mar 2019 09:12:51 -0600 Message-Id: <5C9E35EF0200007800222E0B@prv1-mh.provo.novell.com> X-Mailer: Novell GroupWise Internet Agent 18.1.0 Date: Fri, 29 Mar 2019 09:12:47 -0600 From: "Jan Beulich" To: "Boris Ostrovsky" Cc: "Stefano Stabellini" , "xen-devel" , "Juergen Gross" , Subject: Re: [PATCH] x86/Xen: streamline (and fix) PV CPU enumeration References: <5C9B92EA020000780022227B@prv1-mh.provo.novell.com> <2f027b4b-dce2-3e90-dc1b-c824bc8eb355@oracle.com> <5C9C8DDC0200007800222606@prv1-mh.provo.novell.com> <5C9DDD530200007800222B22@prv1-mh.provo.novell.com> <24df98be-21e7-617e-7651-ae34e2a2e512@oracle.com> In-Reply-To: <24df98be-21e7-617e-7651-ae34e2a2e512@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> On 29.03.19 at 14:42, wrote: > On 3/29/19 4:54 AM, Jan Beulich wrote: >>>>> On 28.03.19 at 17:50, wrote: >>> >>> Given especially xen_pv_smp_prepare_cpus(), I think re-working proper >>> setting of present/possible masks is well beyond the scope of your >>> original patch. >> Well, then the question is, what (if any) changes are you >> expecting me to make for this change to be acceptable? Or do >> you perhaps want me to add a 2nd patch on top addressing >> the other outlined anomalies? > > If your goal is just to fix the dom0_max_vcpus issue then this patch is > sufficient (but the commit message should say that this is what the > patch is for). > > But if you are trying to make cpu masks management done properly then I > think this patch alone does not address this fully. I.e. folding the further items discussed into this patch would be fine by you? (I'm just trying to avoid having to go through several more rounds of patch submissions.) Jan