Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp4433410ybh; Tue, 6 Aug 2019 11:33:53 -0700 (PDT) X-Google-Smtp-Source: APXvYqyXRMDN7LdTyS5EfTPVpxajiDE9TnpUPAD+YiyJRZvn2YO7onRuh6YILsI7tY9NUSoVSSn5 X-Received: by 2002:a62:1d11:: with SMTP id d17mr5131481pfd.249.1565116433841; Tue, 06 Aug 2019 11:33:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565116433; cv=none; d=google.com; s=arc-20160816; b=Nu32LjomEcAhmyHX71DGbt1yzR8hhxpAhb8hgKdj4yhvNmS4sawJR5w2iHiOypWxqz C24OdCKZX2hRHwpxyYFL4fSmQohBhUhsSKV60ydtOGRnYYS2zrWcpVC7BgcxvjGS9tw7 yPA22Iphlxb6fM/SBju6CeKmSDZ3ykJpbVtUvYbA2wa6YiFlXa5shiXAwwyIyTtKDXaw N/BgWlzbPHc2BUop2aEd7LAScTgltf/wgew5eOjzeoNxgfJV/JmnfKqRIBySBhd4WSfZ d+o+WKdlaOHbZnfbFb7kziLZyfZX14oT9d7ziv/xXxerXoMbKsLPjgYZgvXEP05I5JEi X45g== 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=/l9VW0w4uCu16D3f5mJOrOKOlGq/I6xHwmMbd4lMFWY=; b=fuNLIepLxwF2OKr/jsPz4ifh77TKXefcpm6+x95uzZFIifvbgmQY9xCQCD/tfxCUpK dRN03hujYL/utREIJemqppj+HknrtcryMqgnS9Rq3E28UmKB6L0V+5iCAk6JegYu4NnQ lInbvUzGDGZM2OM7B5BdqBl1Qhj1pW8nQkONN3Bz2q3z0T96YbjN8saQNAfsrXxfJt8v WFlKVCMYLT64prm7+Yr4LtQMU101bwYwwVH34VEdIGVJLE7CwoLbNTaWTFJBlBHFWglL KBGXHTKjfSYmyrmsokcdnlRjgw/pOnktzdAoaylMQ4xt/1DgvdMSuoXO3aG9rTDuyCcc AGzQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=E6PqIWDx; 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 e129si48123197pgc.344.2019.08.06.11.33.36; Tue, 06 Aug 2019 11:33:53 -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=E6PqIWDx; 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 S1731825AbfHFScu (ORCPT + 99 others); Tue, 6 Aug 2019 14:32:50 -0400 Received: from mail.skyhub.de ([5.9.137.197]:60212 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728041AbfHFSct (ORCPT ); Tue, 6 Aug 2019 14:32:49 -0400 Received: from zn.tnic (p200300EC2F1369001D2C1334F0CDB20E.dip0.t-ipconnect.de [IPv6:2003:ec:2f13:6900:1d2c:1334:f0cd:b20e]) (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 DF6541EC0503; Tue, 6 Aug 2019 20:32:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1565116368; 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=/l9VW0w4uCu16D3f5mJOrOKOlGq/I6xHwmMbd4lMFWY=; b=E6PqIWDxKsMdip2+UpzkKRhk0TairgFhYExErCT9qvrOrQsJmKnrQCMeS9/1ZNqmdHTSxQ PlPbpWeag0ZjofSNuhZqgrV39jMpENR5p2hxcQFnPS05ppqikHEC+lbNLIBQpQ5g2W79OS 8qP5T3jE8skvcVkF05PMF63U+FQ2fx0= Date: Tue, 6 Aug 2019 20:33:33 +0200 From: Borislav Petkov To: Reinette Chatre Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com, kuo-lang.tseng@intel.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V2 01/10] x86/CPU: Expose if cache is inclusive of lower level caches Message-ID: <20190806183333.GA4698@zn.tnic> References: <6c78593207224014d6a9d43698a3d1a0b3ccf2b6.1564504901.git.reinette.chatre@intel.com> <20190802180352.GE30661@zn.tnic> <20190803094423.GA2100@zn.tnic> <122b005a-46b1-2b1e-45a8-7f92a5dba2d9@intel.com> <20190806155716.GE25897@zn.tnic> <151002be-33e6-20d6-7699-bc9be7e51f33@intel.com> <20190806173300.GF25897@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: 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 Tue, Aug 06, 2019 at 11:13:22AM -0700, Reinette Chatre wrote: > Some platforms being enabled in this round have SKUs with inclusive > cache and also SKUs with non-inclusive cache. The non-inclusive cache > SKUs do not support cache pseudo-locking and cannot be made to support > cache pseudo-locking with software changes. Needing to know if cache is > inclusive or not will thus remain a requirement to distinguish between > these different SKUs. Supporting cache pseudo-locking on platforms with > non inclusive cache will require new hardware features. Is there another way/CPUID bit or whatever to tell us whether the platform supports cache pseudo-locking or is the cache inclusivity the only one? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.