From: Matt Fleming <matt.fleming@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yinghai Lu <yinghai@kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
"H. Peter Anvin" <hpa@zytor.com>, Jan Beulich <jbeulich@suse.com>,
David Howells <dhowells@redhat.com>,
Grant Likely <grant.likely@secretlab.ca>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Arnd Bergmann <arnd@arndb.de>, Dave Jones <davej@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] x86/uapi for 3.8
Date: Sun, 16 Dec 2012 12:46:10 +0000 [thread overview]
Message-ID: <1355661970.2903.28.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CA+55aFwxtt2Rs7dJt_icCsH5QUzrV_UaATQ3aJQY2KGH+anc3A@mail.gmail.com>
On Sat, 2012-12-15 at 15:37 -0800, Linus Torvalds wrote:
> And why do we have to call the get-time calls so early? Couldn't we
> move them later and avoid all the crazy "let's create silly magical
> page tables just for the idiotic EFI problems".
Unfortunately not, because this patch series fixes the case where some
ASUS EFI machines ignore parts of the memory map that we invalidate with
SetVirtualAddressMap() - so the firmware is accessing mappings for
devices after we explicitly tell it they're no longer valid.
It's possible to trigger this broken behaviour at whatever point we
interact with the firmware.
next prev parent reply other threads:[~2012-12-16 12:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 22:11 H. Peter Anvin
2012-12-12 23:48 ` David Howells
2012-12-14 18:25 ` Linus Torvalds
2012-12-14 23:45 ` David Howells
2012-12-15 1:16 ` Linus Torvalds
2012-12-15 1:41 ` Linus Torvalds
2012-12-15 1:47 ` Linus Torvalds
2012-12-15 16:33 ` Markus Trippelsdorf
2012-12-15 16:35 ` Markus Trippelsdorf
2012-12-16 12:43 ` Matt Fleming
2012-12-16 13:25 ` Markus Trippelsdorf
2012-12-16 14:54 ` Matt Fleming
2012-12-16 20:12 ` Linus Torvalds
2012-12-16 22:07 ` Linus Torvalds
2012-12-16 22:25 ` H. Peter Anvin
2012-12-16 22:40 ` Matt Fleming
2012-12-16 22:52 ` Linus Torvalds
2012-12-16 23:49 ` Markus Trippelsdorf
2012-12-15 18:35 ` Linus Torvalds
2012-12-15 19:41 ` H. Peter Anvin
2012-12-15 19:58 ` Linus Torvalds
2012-12-15 20:06 ` Markus Trippelsdorf
2012-12-15 21:04 ` Markus Trippelsdorf
2012-12-15 21:06 ` Linus Torvalds
2012-12-15 21:36 ` H. Peter Anvin
2012-12-15 22:05 ` Yinghai Lu
2012-12-15 23:37 ` Linus Torvalds
2012-12-15 23:46 ` H. Peter Anvin
2012-12-16 12:46 ` Matt Fleming [this message]
2012-12-15 21:37 ` Dave Jones
2012-12-15 23:47 ` H. Peter Anvin
2012-12-17 9:04 ` Jan Beulich
2012-12-17 15:44 ` Linus Torvalds
2012-12-17 16:00 ` Jan Beulich
2012-12-17 16:39 ` H. Peter Anvin
2012-12-17 17:03 ` Jan Beulich
2012-12-17 17:15 ` H. Peter Anvin
2012-12-18 8:02 ` Jan Beulich
2012-12-15 4:25 ` H. Peter Anvin
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=1355661970.2903.28.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=g.liakhovetski@gmx.de \
--cc=grant.likely@secretlab.ca \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@elte.hu \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--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®