public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH v1 2/2] KVM: VMX: always require WB memory type for EPT
Date: Thu, 10 Aug 2017 21:54:53 +0200	[thread overview]
Message-ID: <f4a058fd-fbdb-7854-3ea1-c02dcf5178d0@redhat.com> (raw)
In-Reply-To: <jpg378zky8f.fsf@linux.bootlegged.copy>

On 10.08.2017 21:40, Bandan Das wrote:
> David Hildenbrand <david@redhat.com> writes:
> 
>> We already always set that type but don't check if it is supported. Also
>> for nVMX, we only support WB for now. Let's just require it.
> 
> Out of curiosity, is there old hardware that supports ept but not WB ?
> 

I guess no. KVM always sets up WB for all eptps. KVM would in the
current state simply not work on these machines (vm entry failure).

I guess the same is also true for 4level page-walk length. This should
also be part of any EPT implementation but still we have to check for it.

-- 

Thanks,

David

  reply	other threads:[~2017-08-10 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 13:35 [PATCH v1 0/2] KVM: VMX: require EPTP WB (write-back) support David Hildenbrand
2017-08-10 13:35 ` [PATCH v1 1/2] KVM: VMX: cleanup EPTP definitions David Hildenbrand
2017-08-10 19:38   ` Bandan Das
2017-08-10 19:53     ` David Hildenbrand
2017-08-10 20:58   ` David Hildenbrand
2017-08-10 13:35 ` [PATCH v1 2/2] KVM: VMX: always require WB memory type for EPT David Hildenbrand
2017-08-10 14:42   ` Paolo Bonzini
2017-08-10 18:30     ` Konrad Rzeszutek Wilk
2017-08-10 20:09       ` David Hildenbrand
2017-08-10 19:40   ` Bandan Das
2017-08-10 19:54     ` David Hildenbrand [this message]
2017-08-10 14:23 ` [PATCH v1 0/2] KVM: VMX: require EPTP WB (write-back) support Radim Krčmář
2017-08-10 14:25   ` David Hildenbrand
2017-08-10 16:34     ` Radim Krčmář

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=f4a058fd-fbdb-7854-3ea1-c02dcf5178d0@redhat.com \
    --to=david@redhat.com \
    --cc=bsd@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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