Received: by 10.223.185.116 with SMTP id b49csp2637530wrg; Mon, 12 Feb 2018 13:06:43 -0800 (PST) X-Google-Smtp-Source: AH8x2241UZc5wsNEM93GcD80sB7WQB5SfkWkwjVRF88Cq5NZSt2Hcd1lxfVlQaUVScsvqgB6IUhy X-Received: by 2002:a17:902:47:: with SMTP id 65-v6mr4749575pla.194.1518469603113; Mon, 12 Feb 2018 13:06:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518469603; cv=none; d=google.com; s=arc-20160816; b=WD4KWTbBaBJLCLLx4pLRYEYUE52i4/q7JEg3VwHdNhyk1Ttf9r4cbZojDuPe5gag7R f8Miuc5yM6UfaLBJwtI6ujMlWGfYX8eM6JD5GDSxN6CXyGR32lPvXYI3GukgY3V4GXQj UjNhQqDfCDaJZeKTdhxdZTMgRHDCaWF8d5P12WvRjKLmedIcL6HhHBOrZEEjToZyuEOH dykRHoVPw/F8tG8ugCLSabgYgLFxI6efPnBGYTGQP9Slw9DHyuTA5GrL68Wit4dOMNS7 nNlJqT5H650hN4En+kE+FzWmf5P1qsPes0K4o1fyOORhuJc18nNpi0SzPAzaS8VmXCzL 9PIw== 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:arc-authentication-results; bh=JaAjxmVJ4Kwp3IRQJM5hOKWNtb+BrI9QemxWmqhMSSE=; b=mzNRLLJi1tcjTlEr8/adGLznEOMQIfH6oPmQbQP5sycLLhrXbSSqhA6+CyXpWO5Vtp TMQ5aLDsWp41HKvJzLhmXwu5o2oJsCQF7ntYB5BqMS4e/fLD5xHCw5lE5XmlO802NQ+P IZ9Me60YMhk1VJivar7s806C5LBM7VuGVs2UahON/Au7LpO4m4ncO2kgpqKvK02m09v5 LMR92aY8URFEJZkZsO07iN3gv6ctROg1/hiKFiiPt+sJP+nX5iFtnG8OGf9tgnWIufp5 uFnwZxPIwRo4khzz7KN+Xv/U1ntoqTWmUIFkQPW9w7sgZQGlS83mjkfvC7CENaYR0GUQ vO7w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 34-v6si2677433plz.22.2018.02.12.13.06.26; Mon, 12 Feb 2018 13:06:43 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754142AbeBLVEq (ORCPT + 99 others); Mon, 12 Feb 2018 16:04:46 -0500 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:56838 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754111AbeBLVEp (ORCPT ); Mon, 12 Feb 2018 16:04:45 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 13B7083225; Mon, 12 Feb 2018 21:04:45 +0000 (UTC) Received: from krava (ovpn-204-43.brq.redhat.com [10.40.204.43]) by smtp.corp.redhat.com (Postfix) with SMTP id 209BDB2894; Mon, 12 Feb 2018 21:04:42 +0000 (UTC) Date: Mon, 12 Feb 2018 22:04:42 +0100 From: Jiri Olsa To: Raghavendra Rao Ananta Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, namhyung@kernel.org, linux-kernel@vger.kernel.org, psodagud@codeaurora.org, tsoni@codeaurora.org Subject: Re: [PATCH] perf: Add support for creating offline events Message-ID: <20180212210442.GA32093@krava> References: <1518217620-28458-1-git-send-email-rananta@codeaurora.org> <20180212094357.GD5821@krava> <53408020-8638-4947-90f6-87dbc4c2c4e5@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53408020-8638-4947-90f6-87dbc4c2c4e5@codeaurora.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 12 Feb 2018 21:04:45 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.1]); Mon, 12 Feb 2018 21:04:45 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'jolsa@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 12, 2018 at 09:42:05AM -0800, Raghavendra Rao Ananta wrote: > Hi Jiri, > > Thank you for the response. > > Does perf tool has its own check to see if the CPU was offline during the > lifetime of an event? If so, it might ignore these type of events. nope, we don't check on that > > Initially, I tested the same using perf tool and found similar results. > Then I debugged further and found that the perf core was actually sending > data to the userspace (copy_to_user()) and the corresponding count for the > data. Hence, I tested this further by writing my own userspace application, > and I was able to read the count through this, > even when the CPU was made offline and back online. > > Do you think we also have to modify the perf tool accordingly? hum, I wonder what's wrong.. will check jirka