From owner-freebsd-arch@FreeBSD.ORG Mon May 12 15:14:09 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDDC379F; Mon, 12 May 2014 15:14:09 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 752392FE3; Mon, 12 May 2014 15:14:09 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id a108so7720160qge.22 for ; Mon, 12 May 2014 08:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QIbCHbp0C1SqcWEd87wHH/HoozajtJh31AZaVbEZnzw=; b=zc2PoDOZ/e6WyPpkzJRw3k139d6DP6ugKZhGCQqlQaohFpSsd96cPnVnxwDOu0Z92D Vqh5Ech6pcCKdOXXHvOVww58+hdvpA87QEEMig10G86N7m9zx59++1mxaGOC8h8IDz9t 6MiAJniH3fZhokbs+6ukgDdRByptfBlw8A+Aa6f2rw3DgdKuG6j1BcJ53QBq4yWnZ0e/ eJp9AOF6fmu4E+UbET2qtA+YFgl5MlipmN19Dvj8S2C7gR2WpBGKInGQ6dc1eWG3AcU6 wLPoRfYmFLwur5dZeFK0LsJ4R29zmRfIZ6Tm0r4L9LgS2nwY+qSqyOcM84LNfNPpMgx2 Sszw== MIME-Version: 1.0 X-Received: by 10.224.38.138 with SMTP id b10mr12191463qae.98.1399907648569; Mon, 12 May 2014 08:14:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Mon, 12 May 2014 08:14:08 -0700 (PDT) In-Reply-To: References: <20140505011654.O11699@sola.nimnet.asn.au> <2223.1399233644@critter.freebsd.dk> <20140505153421.W11699@sola.nimnet.asn.au> <85787.1399271121@critter.freebsd.dk> <20140505163316.R11699@sola.nimnet.asn.au> <7681.1399629328@critter.freebsd.dk> Date: Mon, 12 May 2014 08:14:08 -0700 X-Google-Sender-Auth: pPW8a4SXPe8A-EAwASqWOsbjHUU Message-ID: Subject: Re: proposal: set default lid state to S3, performance/economy Cx states to Cmax From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , Ian Smith , "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 15:14:10 -0000 The documentation is uhm, what's on intel's (growing) blog post and responses: https://software.intel.com/en-us/articles/intel-performance-counter-monitor-a-better-way-to-measure-cpu-utilization Yes, we can / should add clearer documentation. I had to also go hunting in the source to figure some of it out. FREQ/AFREQ is just the current clock cycle counters / clock reference counter (TSC). Ie, a freq or afreq of 1.0 means the clock cycle counters == TSC counter. FREQ takes the sleep state into account (ie, only counts _running_ cycles.) AFREQ doesn't. So FREQ gives you a good indication of the running duty cycle versus the ideal maximum, and AFREQ tells you what frequency the core is running at versus the reference frequency. An AFREQ of < 1.0 means that the chip is underclocking that core. An AFREQ of > 1.0 means turboboost is on and it's overclocking that core. -a On 11 May 2014 17:40, Kevin Oberman wrote: > On Fri, May 9, 2014 at 1:36 PM, Adrian Chadd wrote: >> >> cool! >> >> next; >> >> # pkg install intel-pcm >> # kldload cpuctl >> # pcm.x 1 >> >> See what it reports. > > > OK. Any documentation on what this is supposed to tell me? Some of it makes > perfect sense and some baffles me. > > I see C-states of C1 and C6 when on AC and C1, C3, and C7 when on battery > (and, of course, C0). FREQ vs. AFREQ look interesting, but I'm not sure I > really understand the implications. The last few lines, from " PHYSICAL CORE > IPC", are particularly mysterious to me. I can understand the words, but I > think that they carry more significance than is obvious, at least to me. I'm > not a hardware guy. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com