From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: intel_pstate divide error with v3.13-rc4-256-gb7000ad Date: Fri, 27 Dec 2013 18:52:48 +0200 Message-ID: <20131227165248.GG10961@minantech.com> References: <20131227122422.62857cec@alan.etchedpixels.co.uk> <20131227124749.GE10961@minantech.com> <52BD8B8B.1050209@redhat.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <52BD8B8B.1050209@redhat.com> Sender: cpufreq-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Kashyap Chamarthy Cc: Josh Boyer , One Thousand Gnomes , Viresh Kumar , Dirk Brandewie , "Rafael J. Wysocki" , "cpufreq@vger.kernel.org" , Linux PM list , "Linux-Kernel@Vger. Kernel. Org" , "Richard W.M. Jones" On Fri, Dec 27, 2013 at 03:15:39PM +0100, Kashyap Chamarthy wrote: > [. . .] > > >> 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? > > Heya Gleb, > > Here's the relevant dmesg snippet (full dmesg, refer the attachment below): That's guest dmesg. What about host one? Can you ftrace the failure? -- Gleb.