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: <20110804215619.GA7101@srcf.ucam.org>
Date:	Thu, 4 Aug 2011 22:56:19 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Len Brown <lenb@...nel.org>
Cc:	Andrew Lutomirski <luto@....edu>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Fenghua Yu <fenghua.yu@...el.com>,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH 2/2] x86: Enable monitor/mwait on Intel if BIOS hasn't
 already

On Thu, Aug 04, 2011 at 05:54:04PM -0400, Len Brown wrote:
> > We can't trust BIOS authors to get things right. Where we can reliably 
> > fix up things that are broken, we should do so.
> 
> How about if we can get a BIOS fix for this brand new system,
> then we shall not clutter the kernel with a workaround,
> otherwise we shall.

It's a pretty good rule of thumb that if a BIOS bug is present in one 
BIOS it's present in others, but the users will just never notice.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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