From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergio Gonzalez Monroy Subject: Re: [PATCH 2/2] eal/x86: implement x86 specific tsc hz Date: Wed, 23 Aug 2017 14:57:30 +0100 Message-ID: <3221201e-2e7f-f366-2b7b-cc60f140d01b@intel.com> References: <20170823124241.17552-1-sergio.gonzalez.monroy@intel.com> <20170823124241.17552-2-sergio.gonzalez.monroy@intel.com> <20170823131707.GB13944@bricha3-MOBL3.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, konstantin.ananyev@intel.com To: Bruce Richardson Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 9EEBC377E for ; Wed, 23 Aug 2017 15:57:33 +0200 (CEST) In-Reply-To: <20170823131707.GB13944@bricha3-MOBL3.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 23/08/2017 14:17, Bruce Richardson wrote: > On Wed, Aug 23, 2017 at 01:42:41PM +0100, Sergio Gonzalez Monroy wrote: >> First, try to use CPUID Time Stamp Counter and Nominal Core Crystal >> Clock Information Leaf to determine the tsc hz on platforms that >> supports it (does not require priviledge user). >> >> If the CPUID leaf is not available, then try to determine the tsc hz by >> reading the MSR 0xCE (requires priviledge user). >> >> Default to the DPDK tsc hz estimation if both methods fail. >> >> Signed-off-by: Sergio Gonzalez Monroy >> --- > This patch depends on Jerin's previous set for getting the exact TSC > frequency on different platforms, right? It does, I forgot to mention it. I'll send them apart as these patches are not really dependent. Thanks, Sergio