From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Cc: stable <stable@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Brown <mbrown@fensystems.co.uk>,
Ondrej Zary <linux@rainbow-software.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Thomas Gleixner <tglx@linutronix.de>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [GIT PULL] Additional x86 fixes for v3.8-rc1
Date: Wed, 19 Dec 2012 13:33:40 -0800 [thread overview]
Message-ID: <de6b1419-6bbd-4ad2-8b1e-dc989c7beba5@email.android.com> (raw)
In-Reply-To: <CA+55aFxeOK5mvuLubtdRLGrnX3waY=wBisFFE49b-nSwGiLaKg@mail.gmail.com>
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 <torvalds@linux-foundation.org> wrote:
>On Wed, Dec 19, 2012 at 12:22 PM, H. Peter Anvin <hpa@linux.intel.com>
>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.
prev parent reply other threads:[~2012-12-19 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 20:22 H. Peter Anvin
2012-12-19 21:02 ` Linus Torvalds
2012-12-19 21:33 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de6b1419-6bbd-4ad2-8b1e-dc989c7beba5@email.android.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=ebiederm@xmission.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=mbrown@fensystems.co.uk \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®