From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754538Ab3L0Mr7 (ORCPT ); Fri, 27 Dec 2013 07:47:59 -0500 Received: from mail-ea0-f170.google.com ([209.85.215.170]:63933 "EHLO mail-ea0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752748Ab3L0Mr5 (ORCPT ); Fri, 27 Dec 2013 07:47:57 -0500 Date: Fri, 27 Dec 2013 14:47:49 +0200 From: Gleb Natapov To: One Thousand Gnomes Cc: Viresh Kumar , Josh Boyer , Dirk Brandewie , "Rafael J. Wysocki" , "cpufreq@vger.kernel.org" , Linux PM list , "Linux-Kernel@Vger. Kernel. Org" Subject: Re: intel_pstate divide error with v3.13-rc4-256-gb7000ad Message-ID: <20131227124749.GE10961@minantech.com> References: <20131227122422.62857cec@alan.etchedpixels.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131227122422.62857cec@alan.etchedpixels.co.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 27, 2013 at 12:24:22PM +0000, One Thousand Gnomes wrote: > On Tue, 24 Dec 2013 21:36:01 +0530 > Viresh Kumar wrote: > > > Adding Dirk.. > > > > On 24 December 2013 20:06, Josh Boyer wrote: > > > Hi All, > > > > > > We've had a report [1] that the pstate driver causes KVM guests to > > > fail to boot because of a divide error. See the backtrace below. > > > > > > 4.839784] Intel P-state driver initializing. > > > [ 4.859972] Intel pstate controlling: cpu 0 > > > [ 4.867653] cpufreq: __cpufreq_add_dev: ->get() failed > > > > After a call to ->init(), ->get() is supposed to work. > > @Dirk: Any idea why it failed? > > > > And then I don't know what made this divide by zero to happen :) > > > > [ 4.878127] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 > > Emulator bug perhaps ? > KVM does not emulate P-states at all. intel_pstate_init() calls intel_pstate_msrs_not_valid() before printing "Intel P-state driver initializing." which suppose to fail since it checks that two reads of MSR_IA32_APERF return different values, but KVM does not emulate this msr at all, so both calls should return zero (KVM suppose to inject #GP, all rdmsrl are patched to be rdmsrl_safe in a guest). Anything interesting in host dmesg? Is it reproducible? -- Gleb.