From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] FYI - Reading uncached memory
Date: Tue, 12 Jun 2018 13:29:56 -0400 [thread overview]
Message-ID: <f46d02f3-ad06-d380-1b28-4911745f2bf1@redhat.com> (raw)
FYI Graz have been able to prove the Intel processors will allow
speculative reads of /explicitly/ UC memory (e.g. marked in MTRR). I
believe they actually use the QPI SAD table to determine what memory is
speculation safe and what memory has side effects (i.e. if it's HA'able
memory then it's deemed ok to rampantly speculate from it).
Just in case anyone thought UC was safe against attacks.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next reply other threads:[~2018-06-12 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 17:29 Jon Masters [this message]
2018-06-14 16:59 ` [MODERATED] Encrypted Message Tim Chen
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=f46d02f3-ad06-d380-1b28-4911745f2bf1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.