From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: L1TFv8
Date: Fri, 29 Jun 2018 05:21:56 -0400 [thread overview]
Message-ID: <cba5f87b-d0a9-2fad-2d0b-f3ec45bd08ce@redhat.com> (raw)
In-Reply-To: <20180614025606.GE30690@tassilo.jf.intel.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On 06/13/2018 10:56 PM, speck for Andi Kleen wrote:
> Note there is no workaround for 32bit !PAE, or on systems which
> have more than MAX_PA/2 worth of memory. The later case is very unlikely
> to happen on real systems.
Sorry if I missed this being discussed before.
Correct me if I'm wrong, but on Skylake-SP, maximum physical is 64TB,
meaning we wouldn't be safe beyond 32TB populated. In a system with node
controllers, it seems quite plausible you'd have customers with systems
that are, in fact that large. I've pinged a few folks on our end about
e.g. HPE Superdome and will ask Intel to consider that when notifying.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-06-29 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180613224846.B1FF561106@crypto-ml.lab.linutronix.de>
2018-06-14 2:56 ` [MODERATED] Re: L1TFv8 Andi Kleen
2018-06-29 9:21 ` Jon Masters [this message]
[not found] <20180613224850.464286110D@crypto-ml.lab.linutronix.de>
2018-06-15 14:50 ` L1TFv8 Thomas Gleixner
2018-06-15 19:48 ` [MODERATED] L1TFv8 Josh Poimboeuf
2018-06-15 20:57 ` Andi Kleen
2018-06-15 21:50 ` Andi Kleen
2018-06-19 14:54 ` Michal Hocko
2018-06-20 16:04 ` Konrad Rzeszutek Wilk
2018-07-10 13:25 ` Michal Hocko
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=cba5f87b-d0a9-2fad-2d0b-f3ec45bd08ce@redhat.com \
--to=jcm@redhat.com \
--cc=speck@linutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).