From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: requiring virtual NMI for Intel processors? Date: Mon, 20 Feb 2017 17:00:20 -0500 (EST) Message-ID: <204276770.23896790.1487628020731.JavaMail.zimbra@redhat.com> References: <3f272924-3878-5005-fc8c-200d808da2bb@redhat.com> <277837C2-746F-4DBC-AF6F-C4E464831CC3@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: KVM list To: Nadav Amit Return-path: Received: from mx3-phx2.redhat.com ([209.132.183.24]:35745 "EHLO mx3-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750951AbdBTWAd (ORCPT ); Mon, 20 Feb 2017 17:00:33 -0500 In-Reply-To: <277837C2-746F-4DBC-AF6F-C4E464831CC3@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: > 1. It seems you look on Xeons (excluding Yonah and Cedarmill). Desktop and > laptop CPUs may have different fusing than servers. Yeah, the attached file mostly included Xeons because I couldn't find a desktop or laptop CPU for each generation. However I did find Penryn and Nehalem desktop CPUs and they already had vNMI support. I stopped at Haswell because we still don't support nesting some Broadwell+ extensions (e.g. PML). In fact we don't support EPT A/D bits too, though that one shouldn't be hard to add. The list of server-only features seems to be small though until Haswell: only EPT 1GB page tables, PLE and APICv. > 2. No Atoms in the list. Centerton (Saltwell-based) is the only one I have access to and it's the same as Conroe, so it has it. Paolo