linux-kernel - Re: [PATCH v2] x86, tsc: Add missing Baytrail frequency to the table

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140206054410.GB18884@gmail.com>
Date:	Thu, 6 Feb 2014 06:44:11 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:	Bin Gao <bin.gao@...ux.intel.com>, linux-kernel@...r.kernel.org,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Bin Gao <bin.gao@...el.com>
Subject: Re: [PATCH v2] x86, tsc: Add missing Baytrail frequency to the table


* Mika Westerberg <mika.westerberg@...ux.intel.com> wrote:

> On Wed, Jan 29, 2014 at 01:47:54PM -0800, Bin Gao wrote:
> > On Tue, Jan 28, 2014 at 02:04:07PM +0200, Mika Westerberg wrote:
> > > Actually it does not work. I had the fallback path still in the patch when
> > > I tried.
> > 
> > Let's merge the ptach v2 then(continue on msr calibration retuning 0).
> > All supported SoCs now have the correct frequency ID coding
> > so continuing on non-PIC SoCs has very very small possibility.
> 
> x86 maintainers, any comments on this patch (v2)? Without the patch some
> Baytrail systems fail to boot 3.14-rc1.

It should be split in two: first a patch to fix the divide by zero 
bug, second the Baytrail addition.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/