Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp1426112pxu; Fri, 16 Oct 2020 11:37:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy13Zm4jPBnksOUhLMatmgnfDVaBalDidk0/TqBraAVJHvwqNLHiWF4OZKqBzOcTiU6FbKB X-Received: by 2002:aa7:d4c6:: with SMTP id t6mr5416170edr.372.1602873426202; Fri, 16 Oct 2020 11:37:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602873426; cv=none; d=google.com; s=arc-20160816; b=V0LEkzEIodtwVgk9OsmZZsUx2HzrqfF3VUGmczb/bzsaYaEYmls68IZ0pmqI3PcVv5 kFfmTd6xnYj8noVuZvqLxOGpWiJxs5YtPrpoYQ45qNzx9w/IascT/2x9pBMYkh3mbjOP OXCysYkPorBrIt/fGEA1TpZTKSi7/QkHEssntJg4eOzwjPaYkZe6rwRZwIf5in/rBrJR cjGr6lw5gETH0/2A5r4pOaLLhsCw7I2rGSzfkJ8q9jjLUw0X54yqWOLggtH5Y0KVEndG e8exMeEgMC/ftfAiewAfdl3L4Oht65maYUaAC0Ke+gGkwUldnte9S63cv1IsTzrrAc24 rmzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=CxH/8B+N2hDQf/bdaLAbphrBwg9v/pM99BjFp6W2aDM=; b=Gm8gnV79CVwxSe9lIjyrcBo6a5vqlQ8BIhvwkQy26a1Nn+3yNd4q/jZhOGLpS6R2Hs snjhDjMuMYzIH8KVFqTdQYv5bGksVbzn7c2WyfZEtR4K8RmE1+lQjXwwKky4YfRfgX4o PkkCCdvy9cdrHl9qjb2r5pIQuInnMYKpQWHkirx+4EuWqkn2EzOeqvqBU0QxabYf8RvM Qjd3j8R/qtI4L4VLOrY9DIqjPkmjUDAATZZrdxlJvNROI2Y+jXIwdZjcby6CTFQM8zMM RK8mZaAWuzOUOvwiU3r4EcTWe264FtkM1SUB4As2ONy1/fXKsYRrfIMYMPlHmNCEqytA GF3w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k3si2438112eji.109.2020.10.16.11.36.43; Fri, 16 Oct 2020 11:37:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2407375AbgJPNR5 (ORCPT + 99 others); Fri, 16 Oct 2020 09:17:57 -0400 Received: from foss.arm.com ([217.140.110.172]:37216 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2407363AbgJPNR5 (ORCPT ); Fri, 16 Oct 2020 09:17:57 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 79AEC1FB; Fri, 16 Oct 2020 06:17:56 -0700 (PDT) Received: from [10.57.50.28] (unknown [10.57.50.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 87CB73F71F; Fri, 16 Oct 2020 06:17:53 -0700 (PDT) Subject: Re: [PATCH] coresight: etm4x: Add config to exclude kernel mode tracing To: Leo Yan Cc: Sai Prakash Ranjan , Denis Nikitin , Mathieu Poirier , linux-arm-msm@vger.kernel.org, coresight@lists.linaro.org, linux-kernel@vger.kernel.org, Stephen Boyd , linux-arm-kernel@lists.infradead.org, Mike Leach References: <20201015124522.1876-1-saiprakash.ranjan@codeaurora.org> <20201015160257.GA1450102@xps15> <20201016072401.GC4646@leoy-ThinkPad-X240s> <20201016092450.GG4646@leoy-ThinkPad-X240s> <20201016131407.GA31839@leoy-ThinkPad-X240s> From: Suzuki Poulose Message-ID: <16b3be3a-0d2d-0d0f-24a5-020480ed980c@arm.com> Date: Fri, 16 Oct 2020 14:17:51 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: <20201016131407.GA31839@leoy-ThinkPad-X240s> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/16/20 2:14 PM, Leo Yan wrote: > On Fri, Oct 16, 2020 at 12:38:47PM +0100, Suzuki Kuruppassery Poulose wrote: > > [...] > >>>> What happens to the sysfs mode of tracing? For that we would still >>>> need a config right to exclude kernel mode tracing completely. >>> >>> IIUC, sysfs mode and perf mode both can apply the same approach, the >>> guest OS runs a thread context for the host, so when a guest OS is >>> switched in or out, the hypervisor can save/restore the context for >>> the guest OS; thus every guest OS will have its dedicated context and >>> trace data ideally. >> >> I don't think Guest Context is something we can support as mentioned >> above, at least for systems without sysreg access for ETMs (and virtualizing >> ETRs is a different story !) > > Thanks for sharing thoughts, Suzuki. > > I missed the device virtulisation. Here should virtualize all devices > (includes CoreSight ETM/funnel/ETR/ETF)? Or only need to virtualize > ETRs? I wouldn't even think of virtualizing the components without sysreg access. So let us not worry about it :-) Cheers Suzuki