From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f174.google.com (mail-pf0-f174.google.com [209.85.192.174]) by dpdk.org (Postfix) with ESMTP id EABF3239 for ; Mon, 11 Dec 2017 06:38:35 +0100 (CET) Received: by mail-pf0-f174.google.com with SMTP id u19so10762074pfa.12 for ; Sun, 10 Dec 2017 21:38:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=2UpgYvVXRGCWRRlkzKRp9ImLYoB5dc8sfkR06yy7A1U=; b=gsjeR4RgxhFSf2QoauUWFZo2M+f0DyY+r55KP+iorXPFmXwrKirdh413rBIcm4gxMs k564SHF/OnEP9UiCnaD+yZUaQY77L81E9VISE40zpFKBg1pFcnTNvck0OR5/kYN4Phfe 0QHjzthRSd1QM2na1jhtkmbd9PJRY37E77dUaw/uKtkFb9KqSTRq/ypDzrWkuV6vib/l joEI010Xief4jLRJErmd8qrLi1W4YuLZv41b69XmshIIaKTMfChj0kPJzzuvd4C+RmDA Q8iyVADTYzZZPB2tQ0zSvQB4Dj0VGuwNqrMahxvlfsbh3Ycn+fnrrnsrrOtVZWq06QPv qPEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=2UpgYvVXRGCWRRlkzKRp9ImLYoB5dc8sfkR06yy7A1U=; b=emKXFUQAcucrl/oonJaLF/0/jeTDrWc2SV8zEqMS49WDfMiyPbNm1f6n3bW+W9a2BJ ACB0W5CkcP1Nxo4F5mFxLgFrcN0BsruzgSdNMvnXCtq9/S7iX2ymDmFnRhSupGRcwI4J QodKBwAKO3Cujq6y6c2CDvMl6/WEK4qogy0yb6GHwve1dhYNpv838GXvojgxHZPcaZbm 2MhyOpAqN5CzxasWDbYD0jcFhXSyQu6Uf2jUM4sX2MS2lTci4Vv78brhp/chC9eqqfZ4 wy2xhNGIX+Q4ajE76hV3CTypkIgVWV97Z2Cf28wbikNmJ2ytoVmn37iILyz5Ax/t1V6c yQXw== X-Gm-Message-State: AJaThX4M4/9/ia7ZZvlvU+0q6XWdxzGaUzYFeKn1agqhp6AoEkmaAUvB pVntiNYHAZJwA/O3bFO7bj558dc0 X-Google-Smtp-Source: AGs4zMZb5ZtY1qewhZwOecz4etfnCQBubpW+EuTbhFOJLMHmgFsqlvESV2RIxzyPVu/sC2Al60j+jg== X-Received: by 10.99.183.15 with SMTP id t15mr38067835pgf.128.1512970714822; Sun, 10 Dec 2017 21:38:34 -0800 (PST) Received: from [0.0.0.0] (67.209.179.165.16clouds.com. [67.209.179.165]) by smtp.gmail.com with ESMTPSA id d81sm24060980pfj.163.2017.12.10.21.38.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 Dec 2017 21:38:34 -0800 (PST) From: Jia He To: Jerin Jacob , "dev@dpdk.org" Message-ID: <676baa87-777b-ca6e-41c9-7233f90740b6@gmail.com> Date: Mon, 11 Dec 2017 13:38:25 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=gbk; format=flowed Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] About pmu cycle counter usage in armv8 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2017 05:38:36 -0000 Hi Jerin In [1], I met a pmu cycle counter problem (all return value is 0) occasionally. And then I submited a patch to kernel maillist, but was rejected by maintainer at last [2]. He said: "We only intend for the in-kernel perf infrastructure to access pmccntr_el0; nothing else should touch it." So maybe it is not proper for dpdk to use pmu cycle counter? [1] http://dpdk.org/ml/archives/dev/2017-November/080998.html [2]https://lkml.org/lkml/2017/11/16/22 -- Cheers, Jia