Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3816598ybl; Tue, 21 Jan 2020 07:33:27 -0800 (PST) X-Google-Smtp-Source: APXvYqxemUtRFrIllkp6iTQr2AYKYlcOzQtnf0Rs/n5USRYBt3v5lRAn0oP9+AjPsR/OK40a1I8r X-Received: by 2002:a9d:6849:: with SMTP id c9mr4241633oto.206.1579620807391; Tue, 21 Jan 2020 07:33:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579620807; cv=none; d=google.com; s=arc-20160816; b=MXThz/kw/xLUiJC3VmB8fQ+UM/6gBUneakvYK0MHWXg3Yp7tDsDGEw6Kr9z/GLSW2+ 2OtRWncTTG2eKyWpGvISHS9KnXh526L6hQ6jrOA1ZQxb6XBOuis17Gdtu6h1QsDsOay4 cHJGIi1LbERAxadinNU+NvsszdRVzbQ+DDfyZ6evb7Tz5geCJxlm1Hl5vT7l8uh489NW ZMdklGwYQn7I7Ngjt7m/jlzLleH4ieiQ5OMEq+FD2pagYmo52B3vHZ52lI2i3e+4UmVi crYGAkZjMkgcxA6lKyNIXc7OXajYjoPOUCXt+A4L3C24xfztzHIB+GZbuTJ7fYaZVdDW ptmg== 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:dkim-signature; bh=QuY0WDhZX4kxz2cZdcfoWX6pS1PqJixvjT3hklrb4bg=; b=FZgjgbGFL9hm7i6eUcvVucNkJsliRMA3MzebolUWJnmwDRH7k2395wuoSgOQBRcGQ7 LEKU0oVrAXVTXLCSn0JtgtANCEeXrnwyp/Ye7GtdkNGHkhPR0S6VukeB8MAgIc7vX5Yi vjdXpCzLLAauk7Um0cKir5A2MtxfbAvSxMSycJBhn13xrYQ42duUDfoPDfmuxTp2jufF 4DM/nKsyxybEsC6cTR4JIEXrJFsDgfnggGeIP1nIUGTjahZseAtDqBediGLpLhT4Fcdy 3kXLRlDfTy7cVwSByUpZhzo6nIeXUew1uhc+3fLKPz3EQ4s8k3VMJSWVlErdJ1qRtFbN yoQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=google header.b="L+6DmM/k"; 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 l21si19853838oic.126.2020.01.21.07.33.14; Tue, 21 Jan 2020 07:33:27 -0800 (PST) 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=@linuxfoundation.org header.s=google header.b="L+6DmM/k"; 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 S1729122AbgAUPcQ (ORCPT + 99 others); Tue, 21 Jan 2020 10:32:16 -0500 Received: from mail-il1-f195.google.com ([209.85.166.195]:40530 "EHLO mail-il1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727508AbgAUPcQ (ORCPT ); Tue, 21 Jan 2020 10:32:16 -0500 Received: by mail-il1-f195.google.com with SMTP id c4so2674347ilo.7 for ; Tue, 21 Jan 2020 07:32:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QuY0WDhZX4kxz2cZdcfoWX6pS1PqJixvjT3hklrb4bg=; b=L+6DmM/kq/25mWwwyfuJL5puz+XC8sQxXxmq4SEsjcjIrwPeY2MlaTK+KdFs0tUjpx e9TsO6QoiGoo8N8SYntD/DxXCbi1YZvH7iN2RdjPK7Wc4cGsN53XBYakvS9cUL9SAqI/ RwQuKwy2Lk20eL6NfyGHqSaKkBLw3YLyu6U7w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QuY0WDhZX4kxz2cZdcfoWX6pS1PqJixvjT3hklrb4bg=; b=n9PtVdgy8wLj/wT0eRkwgD1RkxjUVzcCewQkQ5hCc6HHVqF1zfGmanuZHkgSLxT2t2 VzHfwMBpzqS8q93MlZplOsbJdHJ0R5gSxW9Fy16Y+DJixGUMToPcevg3limMe11kjbcK kuNLc/1Qqblsn8jhlzaG+hju+ek22VrRriZk619paUJglb384fTxjGm6KZa3tJhj/pPH wt8YEEvDPqV0KFIVKmnOrM4+HGFJN54elqhnxyD5kEkPOfnkfs9YaJCzhNFrhZlSKIcv so1g4Xpuycjztm3cq1eZqqls6Xjm+36JMxfmO36q/LV1D8nwJf5iZAEyZzIeQCq/50eO ORAQ== X-Gm-Message-State: APjAAAXRyhGoB7u/hDMhSKM+vwpBD5yBBaD03NDH5pwcFDdKxFue9ge7 5VhI6OFQz5ebRMtp5RgzLBTFfQ== X-Received: by 2002:a05:6e02:c83:: with SMTP id b3mr4035768ile.29.1579620735950; Tue, 21 Jan 2020 07:32:15 -0800 (PST) Received: from [192.168.1.112] (c-24-9-64-241.hsd1.co.comcast.net. [24.9.64.241]) by smtp.gmail.com with ESMTPSA id r14sm13344854ilg.59.2020.01.21.07.32.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Jan 2020 07:32:15 -0800 (PST) Subject: Re: [PATCH] iommu: amd: Fix IOMMU perf counter clobbering during init To: Suravee Suthikulpanit , Joerg Roedel Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Shuah Khan References: <20200114151220.29578-1-skhan@linuxfoundation.org> <20200117100829.GE15760@8bytes.org> <42c0a806-9947-1401-9754-8aa88bd7062f@amd.com> From: Shuah Khan Message-ID: <24a46b0f-33d7-5f94-661a-80f035213892@linuxfoundation.org> Date: Tue, 21 Jan 2020 08:32:14 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <42c0a806-9947-1401-9754-8aa88bd7062f@amd.com> 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 On 1/20/20 7:10 PM, Suravee Suthikulpanit wrote: > On 1/17/2020 5:08 PM, Joerg Roedel wrote: >> Adding Suravee, who wrote the IOMMU Perf Counter code. >> >> On Tue, Jan 14, 2020 at 08:12:20AM -0700, Shuah Khan wrote: >>> init_iommu_perf_ctr() clobbers the register when it checks write access >>> to IOMMU perf counters and fails to restore when they are writable. >>> >>> Add save and restore to fix it. >>> >>> Signed-off-by: Shuah Khan >>> --- >>>   drivers/iommu/amd_iommu_init.c | 22 ++++++++++++++++------ >>>   1 file changed, 16 insertions(+), 6 deletions(-) >> Suravee, can you please review this patch? >> > > This looks ok. Does this fix certain issues? Or is this just for sanity. I didn't notice any problems. Counters aren't writable on my system. However, it certainly looks like a bog since registers aren't restored like in other places in this file where such checks are done on other registers. I see 2 banks and 4 counters on my system. Is it sufficient to check the first bank and first counter? In other words, if the first one isn't writable, are all counters non-writable? Should we read the config first and then, try to see if any of the counters are writable? I have a patch that does that, I can send it out for review. > > Reviewed-by: Suravee Suthikulpanit Thanks for the review. thanks, -- Shuah