Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp1407278img; Sat, 23 Mar 2019 02:00:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqwQ+hbBahRvhnw0eWQDB4iqSA8JZEPLR29mxLs8s437f4u60lI7Wrvb0dCSGoRAHR/judmb X-Received: by 2002:a63:5c66:: with SMTP id n38mr13125711pgm.15.1553331631472; Sat, 23 Mar 2019 02:00:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553331631; cv=none; d=google.com; s=arc-20160816; b=B6Iny4FKlQbulhPOXXKqMZv03jOILr6B918OGn+3zm18c1LryfaRqzC7Sdb2xZ3zJh tZi0O2owUJiy73AkjeqtYeqqZVgEK1YhiBs28APrxktfzgcruZmShGw1vFFPT/t8OCtw pUBX2nFamxseBmhVlAyMQbS6Mj9Q7ngIq1eiEndMC37AjMMxtV1lY5AYZFZVfgRqXdhf ImHFFWN04YaJw4ufSy7sjGgGVxW8X2gWpAPdy7Gldu3TcQcDptXj7l1Qy5FUztXq2TI+ quQ9q0vZS3vxdYqDrB39ehq6bd34us9IpK2sMzKqB7YhkIVlxPYGLBK+a9EDN42zH76j X7XA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=fv/Gc6KFftce6AQ0F5UIVNtAfNvWMEqV8X/90dTF/jg=; b=WuJhizwNhAAdX1DlCJVJyaUZwfd23qKm5XLlc8Cv7LctooBjNPRAT1tDLCORpYEDrl 0GnSDjoko2PNaakccX/2WspuG2fCfmMZgppenKvgVNqa6HlKLEGgyFSNm8FFS6w6Dgv2 SFJRqeuSoqQkhDSdMIuzKWOWuvafJWlHt+5IhR1HUwXUa39D0A80qKTDKfiD0zRhpWA5 2S6vGHRKYnecT/gpaabrLfj9vR+9wuHnwD7lsBc2QrOW43LvApjHkdMP7zhkaYT/sr+Y WL/7woKe60hF88sLPhrdA6sdBTwkPfWr1RInOEgyzH6wZR307julljG1uxSllVEk9m6w 21ZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=bffld3oa; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r201si8198124pgr.445.2019.03.23.02.00.16; Sat, 23 Mar 2019 02:00:31 -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; dkim=pass header.i=@alien8.de header.s=dkim header.b=bffld3oa; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726301AbfCWI73 (ORCPT + 99 others); Sat, 23 Mar 2019 04:59:29 -0400 Received: from mail.skyhub.de ([5.9.137.197]:56680 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725976AbfCWI73 (ORCPT ); Sat, 23 Mar 2019 04:59:29 -0400 Received: from zn.tnic (p200300EC2F098000329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f09:8000:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id AE2EE1EC00FF; Sat, 23 Mar 2019 09:59:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553331567; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=fv/Gc6KFftce6AQ0F5UIVNtAfNvWMEqV8X/90dTF/jg=; b=bffld3oaARaEx1vr/kidG4jjUVCLj6OPycAzT5OM5C3CFDjECo/I9U2RAHzAY/+CnXOsYy 2iusge4eJnI6bv8bH5UUn/t0+HjC4N2OzxKNAknUzRKFFqc91C1DUnL0UaTMcoEaPq0tpt C/v8jKk8FsgnCitOoD5ARxr/DKP3FC8= Date: Sat, 23 Mar 2019 09:59:34 +0100 From: Borislav Petkov To: Pu Wen Cc: "tglx@linutronix.de" , "mingo@redhat.com" , "hpa@zytor.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [RFC PATCH] x86/cpu/hygon: Fix phys_proc_id calculation logic for multi-die processor Message-ID: <20190323085934.GB23698@zn.tnic> References: <1553251380-7015-1-git-send-email-puwen@hygon.cn> <20190322155449.GE12472@zn.tnic> <639a5bc6-f821-ee9d-1594-d02701321192@hygon.cn> <20190322171632.GI12472@zn.tnic> <18e15073-81c2-73a3-abf1-e785d6a5649b@hygon.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <18e15073-81c2-73a3-abf1-e785d6a5649b@hygon.cn> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 23, 2019 at 10:13:39AM +0800, Pu Wen wrote: > Current physical id is computed via "phys_proc_id = initial_apicid >> > bits". > > For 4-Die 2 socket system, the physical id of socket 2 is: > initial_apicid >> bits = 0b1xxxxxx >> 6 = 1. > The result is true. > > But for 2-Die 2 socket system, the physical id of socket 2 is: > initial_apicid >> bits = 0b10xxxxx >> 5 = 2, > and for 1-Die 2 socket system, the physical id of socket 2 is: > initial_apicid >> bits = 0b100xxxx >> 4 = 4. > The results are not correct any more. > > So the adjustment for the 1-Die/2-Die 2 socket system is needed. > And just use ApicId[6], which already defined the right thing, as the > socket ID. I understand all that. But let me repeat my question: So why do you need to do something different than what AMD does? You said you're programming the initial APIC ID the same as AMD. So why doesn't this need to be changed in AMD code too but only for hygon? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.