From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751502Ab2LSVel (ORCPT ); Wed, 19 Dec 2012 16:34:41 -0500 Received: from terminus.zytor.com ([198.137.202.10]:47004 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751009Ab2LSVef (ORCPT ); Wed, 19 Dec 2012 16:34:35 -0500 User-Agent: K-9 Mail for Android In-Reply-To: References: <201212192022.qBJKMrJ6021946@tazenda.hos.anvin.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [GIT PULL] Additional x86 fixes for v3.8-rc1 From: "H. Peter Anvin" Date: Wed, 19 Dec 2012 13:33:40 -0800 To: Linus Torvalds , "H. Peter Anvin" CC: stable , Alan Cox , Dmitry Torokhov , "Eric W. Biederman" , Ingo Molnar , Linux Kernel Mailing List , Michael Brown , Ondrej Zary , "Rafael J. Wysocki" , Thomas Gleixner , Yinghai Lu Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Well, A20 has been done inside the caches since 486, usually in the TLB. Nehalem finally killed off A20M. You're not the only one surprised by this... Linus Torvalds wrote: >On Wed, Dec 19, 2012 at 12:22 PM, H. Peter Anvin >wrote: >> x86, 8042: Enable A20 using KBC to fix S3 resume on some MSI >laptops > >Christ really? What century are we in? There are still machines that >have A20 disabled at all, much less externally? How do they even do >that these days, afaik the CPU caches can't handle the fake aliasing >anyway.. > >Anyway, pulled, I just wanted to express my surprise.. > > Linus -- Sent from my mobile phone. Please excuse brevity and lack of formatting.