From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: intel_pstate divide error with v3.13-rc4-256-gb7000ad
Date: Sat, 04 Jan 2014 18:38:59 +0100
Message-ID: <52C84733.1090507@redhat.com>
References: <CA+5PVA6YpKc6kYK5UiTnGLZpB8uts=-QPtyhotAyZ2kuoG8PPQ@mail.gmail.com> <2513222.AheLcigoE8@vostro.rjw.lan> <52C7C7EE.1070407@redhat.com> <1676077.d8A9e8eo7M@vostro.rjw.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <cpufreq-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=bqPSRNRI+CJP9FuTIxrc9Jfd/vOCrv1XIetEvIlG6rI=;
        b=Ikw86USsU29F3bfjeN+kmK4y2h3ztxs2Om31Wukp+YeB4wtRdNGqGizGoYqCvZWS+b
         zdqT+yku59QgoUCOMvrSk28EdV1kpOrL9M3EE7GQI7sUrYm6YAv1SZD2sxGkyD+HYrLx
         EnPsKkbxckRDoQW8def9Tq15Kew+YmDGG4GSCCWgtckeh5mVGGSMYBcTtXuEybc7J0My
         imHvSyepnbjXWP+txvTI7Rk1HmMivvPySzTrqWvsuW0jg6zTPaqfo/2dIlQRRjpqCTO3
         vtXkTU7AWN/aCcRO1QAQACtM1IBBsx+f75NlPUnsZEwcdX1R2838mj5hj1WWE5BQ3INV
         Ziig==
In-Reply-To: <1676077.d8A9e8eo7M@vostro.rjw.lan>
Sender: cpufreq-owner@vger.kernel.org
List-ID: <cpufreq.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Gleb Natapov <gleb@kernel.org>, Dirk Brandewie <dirk.brandewie@gmail.com>, Kashyap Chamarthy <kchamart@redhat.com>, Josh Boyer <jwboyer@fedoraproject.org>, One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>, Viresh Kumar <viresh.kumar@linaro.org>, "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>, Linux PM list <linux-pm@vger.kernel.org>, "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>, "Richard W.M. Jones" <rjones@redhat.com>

Il 04/01/2014 15:38, Rafael J. Wysocki ha scritto:
> Well, it's just a sanity check and it makes the problem go away for the reporter.
> 
>> > Your patch is welcome but perhaps it should have a WARN_ON too.
> It has been pulled in already, so the WARN_ON() can only be added via a separate
> patch now.  Would you like to prepare that patch?

Yes, I'll add it together with the CPUID check.  I'll send the patch so
that it can get into 3.14.

Paolo