Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp5623674imm; Wed, 12 Sep 2018 08:40:05 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZwkQrpGvOcwYSYJncss+9jQX/Rx2A+b0oh/MQyInko0vzShvjL9vCmInmwKDjeHT4MeEwZ X-Received: by 2002:a62:1314:: with SMTP id b20-v6mr3088557pfj.230.1536766805242; Wed, 12 Sep 2018 08:40:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536766805; cv=none; d=google.com; s=arc-20160816; b=IaqB9diSV8vn9vgt//pDwwqPdriwOQRdksvjMdCf0Fb+HfspEyoCM1Z7R4Yc/NA/8I 85xBy+cFr/ge8CCkSchAAMeNhyVhvbygUyJVxjiHsl+FicJ9fYv8kFRvmXXTeOTUdqEL H+41fGhzkjV7iOB/P3RgfqgB/OCQsOGFLJKQ9apfAd94mEkIhwvMmHg54qegh05O2Xpq KC4DnQjPMVs8csSVGrnMtzy1NKKqfN6db0hlzSduyVWV8gChmECKNv3rUupdIK/ZjoE7 nXLpy9Z4D4X/HXrqTnNpvxnXLnTx4FTWoOe7hqAXb1Ap2Bhfp7FsK4OJ4aUePGfHlo1h 4Rbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=VCLQZsKQnDu3VJlgFXg5UU7eWtxBEsx0uUmwsd2y++c=; b=jWIn1zNtQJTzakPd+8WgqZUdosq5EyT0kg0mOhuwKiptdlmSXSQKbDRRjpXf6GFD3g MruaVhfYLdfJ4Q2GINLfqftmtsjuWBUllpTUMT0RoH5RVYbbCh0L56JQ4F+1ZM19F3wk rfjQOPuDzrUV1BacOdivScvFrHYPFkjfSsXzhfIWlJCKJZYiwSMDIp0MNNgBfYONUzux 5lk4o7F9T2Tp3NBNPAUUgnP5ttsyWCLQHEckM43DBYtwwHkxfaI78Qqe0A18jtTNCRFJ JQtWsMWTfgf/NPZYkk2YB2RVwvObgWPwU0+1ZfTzU5mCG5i7EhQsuO5esxgEmPUqAfW8 E92w== 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 m10-v6si1525713pgc.105.2018.09.12.08.39.49; Wed, 12 Sep 2018 08:40:05 -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 S1727122AbeILUoj (ORCPT + 99 others); Wed, 12 Sep 2018 16:44:39 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:33958 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726640AbeILUoj (ORCPT ); Wed, 12 Sep 2018 16:44:39 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 72BAC7A9; Wed, 12 Sep 2018 08:39:35 -0700 (PDT) Received: from [192.168.100.242] (usa-sjc-mx-foss1.foss.arm.com [217.140.101.70]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 125773F5C0; Wed, 12 Sep 2018 08:39:35 -0700 (PDT) Subject: Re: [PATCH] ACPI/PPTT: Handle architecturally unknown cache types To: Jeffrey Hugo , rjw@rjwysocki.net, linux-acpi@vger.kernel.org Cc: linux-kernel@vger.kernel.org, vkilari@codeaurora.org, Sudeep Holla References: <1536694334-5811-1-git-send-email-jhugo@codeaurora.org> <98e2e6fa-7256-b5ac-7d2e-42c858c6e57c@codeaurora.org> From: Jeremy Linton Message-ID: Date: Wed, 12 Sep 2018 10:39:34 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <98e2e6fa-7256-b5ac-7d2e-42c858c6e57c@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 09/12/2018 09:41 AM, Jeffrey Hugo wrote: > The HW designers have indicated that there is no sane way to provide > sets/ways information to software, even on an informational basis (ie > not for cache maintenance, but for performance optimizations). Therefore > the firmware will not provide this information because it will be wrong. > > So, therefore, we should still be able to tell the user that a cache > exists at the relevant level, and what size it is.  On the concerned > system, we cannot do that currently. Ok, so set the fields to zero in firmware node, and mark them valid. That logically says that there isn't any set/way information for the cache (which implies direct mapped).