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: <alpine.DEB.2.02.1403121716540.18573@ionos.tec.linutronix.de>
Date:	Wed, 12 Mar 2014 17:20:02 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	joeyli <jlee@...e.com>
cc:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Julian Wollrath <jwollrath@....de>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [RESEND] Fast TSC calibration fails with v3.14-rc1 and later

On Wed, 12 Mar 2014, joeyli wrote:
> I think maybe still using ACPI_FADT_NO_CMOS_RTC to check does
> acpi_early_init() need run before timekeeping_init().
> If there have any future machine that applied ACPI TAD but "Fast TSC
> calibration" fail, at least the alternate TSC calibration can work
> around issue.

Well, it can work around, but it sucks as it's way slower than the
fast one. And we really don't want to pay that price for some half
baken ACPI nonsense.

Why exactly do you need that ACPI stuff before timekeeping_init()?

Thanks,

	tglx
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ