public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi.kivity@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Nadav Amit <nadav.amit@gmail.com>
Cc: "kvm list" <kvm@vger.kernel.org>, "Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: 2 CPU Conformance Issue in KVM/x86
Date: Mon, 09 Mar 2015 21:49:19 +0200	[thread overview]
Message-ID: <54FDF93F.7080502@gmail.com> (raw)
In-Reply-To: <54FDF6CB.8050209@redhat.com>

On 03/09/2015 09:38 PM, Paolo Bonzini wrote:
>
> On 09/03/2015 20:19, Avi Kivity wrote:
>> I can't think of one with reasonable performance either.  Perhaps the
>> maintainers could raise the issue with Intel.  It looks academic but it
>> can happen in real life -- KVM for example used to rely on reserved bits
>> faults (it set all bits in the PTE so it wouldn't have been caught by
>> this).
> Yes, and it checked that MAXPHYADDR != 52 before.  If you want to set
> only one bit, making that bit 51 makes sense anyway for simplicity, so
> it is still 99.9% academic.  Once processors appear with MAXPHYADDR =
> 52, the remaining 0.1% will become more relevant.
>
> The current limit is IIRC 46 or 48 (on Haswell Xeons).
>

It will be interesting to have processors with 52 bits of physical 
address and 48 bits of virtual address. HIGHMEM for x86_64?  Or 5-level 
page tables?

50 bits == 1 PiB.  That's quite an amount of RAM.

  reply	other threads:[~2015-03-09 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  8:34 2 CPU Conformance Issue in KVM/x86 Nadav Amit
2015-03-03  9:52 ` Paolo Bonzini
2015-03-03 10:18   ` Nadav Amit
2015-03-03 14:31     ` Radim Krčmář
2015-03-09 17:08   ` Avi Kivity
2015-03-09 17:51     ` Nadav Amit
2015-03-09 18:23       ` Avi Kivity
2015-03-09 19:07         ` Nadav Amit
2015-03-09 19:19           ` Avi Kivity
2015-03-09 19:38             ` Paolo Bonzini
2015-03-09 19:49               ` Avi Kivity [this message]
2015-03-10 10:47                 ` Paolo Bonzini
2015-03-10 20:38                   ` Avi Kivity
2015-03-09 19:33     ` Paolo Bonzini
2015-03-09 19:50       ` Avi Kivity
2015-03-10 10:44         ` Paolo Bonzini

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=54FDF93F.7080502@gmail.com \
    --to=avi.kivity@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=nadav.amit@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    /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