All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH] SPTE masking
Date: Fri, 10 Aug 2018 10:45:57 -0700	[thread overview]
Message-ID: <20180810174557.GI4238@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1808101030330.29469@i7.lan>

On Fri, Aug 10, 2018 at 10:32:07AM -0700, speck for Linus Torvalds wrote:
> 
> 
> On Fri, 10 Aug 2018, speck for Andi Kleen wrote:
> > 
> > Normally we have the maxphyaddr reported by CPUID, and then we
> > have a larger maxphyaddr which could exist because VMs are lying
> > (upto 46bits)
> 
> .. or because the CPU itself is lying. Didn't we have some CPU versions 
> that reported a different maxphyaddr than the CPU internally actually had? 
> I'm pretty sure I saw a patch that listed specific CPU versions with the 
> "correction" to the reported size..

Yes some client parts report a lower maxphyaddr than what the cache
internally uses because their external bus supports less.
But in all cases it's <= 46bits.

Still not clear how that applies to Paolo's terminology.

-Andi

  reply	other threads:[~2018-08-10 17:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 23:21 [MODERATED] [PATCH] SPTE masking Jim Mattson
2018-08-09  2:57 ` [MODERATED] " Andi Kleen
2018-08-09  9:24   ` Paolo Bonzini
2018-08-09 17:43     ` Andi Kleen
2018-08-10  7:55       ` Paolo Bonzini
2018-08-10 15:59         ` Jim Mattson
2018-08-10 17:23         ` Andi Kleen
2018-08-10 17:32           ` Linus Torvalds
2018-08-10 17:45             ` Andi Kleen [this message]
2018-08-10 18:37               ` Paolo Bonzini
2018-08-10 19:17                 ` Andi Kleen
2018-08-12 10:57                   ` Paolo Bonzini
2018-08-09  9:25 ` Paolo Bonzini
2018-08-09  9:33   ` Andrew Cooper
2018-08-09 10:01     ` Paolo Bonzini
2018-08-09 10:47       ` Andrew Cooper
2018-08-09 11:13         ` Paolo Bonzini
2018-08-09 11:46           ` Andrew Cooper
2018-08-09 11:54             ` Paolo Bonzini
2018-08-09 14:01               ` Andrew Cooper
2018-08-09 15:00                 ` Paolo Bonzini
2018-08-09 20:14       ` Jim Mattson

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=20180810174557.GI4238@tassilo.jf.intel.com \
    --to=ak@linux.intel.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.