From: Linus Torvalds <torvalds@linux-foundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: Is: Tim, Q to you. Was:Re: [PATCH 1/2] L1TF KVM 1
Date: Mon, 4 Jun 2018 18:30:28 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.21.999.1806041828060.3564@i7.lan> (raw)
In-Reply-To: <c4fb8236-403d-83f7-ec4e-c6e56795d24d@redhat.com>
On Mon, 4 Jun 2018, speck for Jon Masters wrote:
>
> I had assumed it was for the more straightforward reason that $future
> uarch has a 64K L1D$, at least according to "The Internet" (TM):
>
> https://en.wikichip.org/wiki/intel/core_i3/i3-8121u
No, that 64kB is just 2x32kB due to two cores.
It's still 8-way and 32kB per core, from what I can tell.
Linus
next prev parent reply other threads:[~2018-06-05 1:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 19:42 [MODERATED] [PATCH 0/2] L1TF KVM 0 Paolo Bonzini
2018-05-29 19:42 ` [MODERATED] [PATCH 1/2] L1TF KVM 1 Paolo Bonzini
2018-05-29 19:42 ` [MODERATED] [PATCH 2/2] L1TF KVM 2 Paolo Bonzini
[not found] ` <20180529194240.7F1336110A@crypto-ml.lab.linutronix.de>
2018-05-29 22:49 ` [PATCH 1/2] L1TF KVM 1 Thomas Gleixner
2018-05-29 23:54 ` [MODERATED] " Andrew Cooper
2018-05-30 9:01 ` Paolo Bonzini
2018-05-30 11:58 ` Martin Pohlack
2018-05-30 12:25 ` Thomas Gleixner
2018-05-30 14:31 ` Thomas Gleixner
2018-06-04 8:24 ` [MODERATED] " Martin Pohlack
2018-06-04 13:11 ` [MODERATED] Is: Tim, Q to you. Was:Re: " Konrad Rzeszutek Wilk
2018-06-04 17:59 ` [MODERATED] Encrypted Message Tim Chen
2018-06-05 1:25 ` [MODERATED] Re: Is: Tim, Q to you. Was:Re: [PATCH 1/2] L1TF KVM 1 Jon Masters
2018-06-05 1:30 ` Linus Torvalds [this message]
2018-06-05 7:10 ` Martin Pohlack
2018-06-05 23:34 ` [MODERATED] Encrypted Message Tim Chen
2018-06-05 23:37 ` Tim Chen
2018-06-07 19:11 ` Tim Chen
2018-06-07 23:24 ` [MODERATED] Re: Is: Tim, Q to you. Was:Re: [PATCH 1/2] L1TF KVM 1 Andi Kleen
2018-06-08 16:29 ` Thomas Gleixner
2018-06-08 17:51 ` [MODERATED] " Josh Poimboeuf
2018-06-11 14:50 ` Paolo Bonzini
2018-05-30 8:55 ` [MODERATED] " Peter Zijlstra
2018-05-30 9:02 ` Paolo Bonzini
2018-05-31 19:00 ` Jon Masters
[not found] ` <20180529194322.8B56F610F8@crypto-ml.lab.linutronix.de>
2018-05-29 23:59 ` [MODERATED] Re: [PATCH 2/2] L1TF KVM 2 Andrew Cooper
2018-05-30 8:38 ` Thomas Gleixner
2018-05-30 16:57 ` [MODERATED] " Andrew Cooper
2018-05-30 19:11 ` Thomas Gleixner
2018-05-30 21:10 ` [MODERATED] " Andi Kleen
2018-05-30 23:19 ` Andrew Cooper
[not found] ` <20180529194239.768D561107@crypto-ml.lab.linutronix.de>
2018-06-01 16:48 ` [MODERATED] Re: [PATCH 1/2] L1TF KVM 1 Konrad Rzeszutek Wilk
2018-06-04 14:56 ` Paolo Bonzini
[not found] ` <20180529194236.EDB8561100@crypto-ml.lab.linutronix.de>
2018-06-06 0:34 ` Dave Hansen
2018-06-06 14:15 ` Dave Hansen
[not found] ` <20180529194240.5654A61109@crypto-ml.lab.linutronix.de>
2018-06-08 17:49 ` Josh Poimboeuf
2018-06-08 20:49 ` Konrad Rzeszutek Wilk
2018-06-08 22:13 ` Josh Poimboeuf
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=alpine.LFD.2.21.999.1806041828060.3564@i7.lan \
--to=torvalds@linux-foundation.org \
--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.