Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1522251ybp; Fri, 4 Oct 2019 16:36:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqyUfXqnIL6Vr/oJvfRRkIiDcrLs1caJGEJlKigheMMOokCAZK9wbcmAo6FQ0BfgzGr/2St8 X-Received: by 2002:a17:907:20f1:: with SMTP id rh17mr14664866ejb.110.1570232184480; Fri, 04 Oct 2019 16:36:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570232184; cv=none; d=google.com; s=arc-20160816; b=i4FzzA0ed1z+0p9NL3WjWMqKKf+WpRGb8ED3Iw95nn9oCJsbDg0711pBhOsjwLY6bJ jzoYIfMZ+S8d2RY8DDnsfnzwaSV5BtzQeFLpeiXxGHiTHC4oTNwLJ1xONh5E2CKFgDaS CNXETHWSvoonqcy7VUi07oQOMQ3d0wgIxsucAAIjEs8cICtE2XvXwaaU6FWJunCu8x+6 1xzm0AkHX1VNQ+3HXfTSYKxCQXDkGLgzGXB58MYmte2xtlSgOf57FGEfbPRVLmWdbXJd EAPGPblHMLJ5jkb/XBByp5WogFHnwBCcTkYeFmJ+T5YU8YBSIArx7ktG2LPCTP1IQAJe o4RQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=+T7DRRD+UBJWxQqae2a5KokUy893Q+Fh/NFyFQWVL5c=; b=0yBg2KEwkdTqdnZLUKTMNT2LyvGpUPbuKgg06vbAog9TrV4WrAHubMJYbfiufTPx4G kHYmSQTA19h6gSbAIkRAzqVYcJ8aXSNCUJXATwVv8MOxlbxZ1Tv6WXHsF22OUEqwVAxA UNpwdmmb90kQJxUSi0lscUIx1tbqrbGdLFJ15KK72DhPnCguEs971VwxIcwnKCnMZ2C7 74bizsjR512prko4nzxhW3ULK9zPQGFPFCbLbbDFzzGCzRFHMUUZjRd/tRJf+OFYzRtP LSYW9ExYpsLQB5pIVC1TVWcmVN84owGYasPL6eUPPuPEvlVTWa1JSkK4smmZ3BCGS+za rQiw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=aR+KCZ9i; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m10si3791714ejc.337.2019.10.04.16.36.01; Fri, 04 Oct 2019 16:36:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=aR+KCZ9i; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729714AbfJDXfy (ORCPT + 99 others); Fri, 4 Oct 2019 19:35:54 -0400 Received: from mail-io1-f65.google.com ([209.85.166.65]:42470 "EHLO mail-io1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729976AbfJDXfy (ORCPT ); Fri, 4 Oct 2019 19:35:54 -0400 Received: by mail-io1-f65.google.com with SMTP id n197so17040617iod.9 for ; Fri, 04 Oct 2019 16:35:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+T7DRRD+UBJWxQqae2a5KokUy893Q+Fh/NFyFQWVL5c=; b=aR+KCZ9iMZp71ShYHM33WPPJZLgnz4zsUdnjqJr8GHFuHLR7FyxN/fle/WUHQd2S1g OfLnAhfjfVGHzOaJK0w0TC11rXg1X4dvELPEblK609VJWdmUv3sZEwya23vmrWxc9DIG vIwRS1tb3jC35O1UM0jW9C+Ii5AJiQBiaQ1Ur7s/C07BnQkMOVZ4W9F3sPzf++A2KGb7 xR6BJ5NeINKOa0O4NpITK3QSA5A4hBhi6JPVSDWobx9wowRsCSuZB6NQRnkdoOs+Z2W2 osQu5NuuvxVuUBBBHYMDims/a/amUqM21/mCbGDA6dx/4nzkkCX+H13qHMc6NbHauO0N 1cfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+T7DRRD+UBJWxQqae2a5KokUy893Q+Fh/NFyFQWVL5c=; b=ZSQ1M50Jy7oLYYe55n+zMxm+UzX4VqKZt3XtkjFOFS6C9Tey8vLvnwA1cosYlexfE0 T5H5sJr9zO9Tk2vm1QT0CK5TcqWu1xqBlMhGaTbO32125uuvMHSO8YSiVXJigHlN+Cjt 1+3xjaJDN/NdKD/0liEIVAuWe1AD9VXqS1LJdQQw5oiz8uy7PCmoecDHairo+/0rNAdC FpglDp/eSWCpl23FIAwFomNfqTeLtwge06I2G4P5N3o0ZjGR68tbhyWRUni/7mrMnLhz bOQ7aeBEb03JZWg2uSgFL2UR1HkcZYBHSS0y8uz6rBGpwOFsDBizTemJNZAJCsBv6bSW ieHQ== X-Gm-Message-State: APjAAAU15fusUYXZl5szGuT4N7H0zijI9FSGUUQd0m2jfTk3WYJjsKr+ 6a9x1hxnqXWgkxwGnzvTio0uaS5Q+1d9hFaTsMh88g== X-Received: by 2002:a92:5a10:: with SMTP id o16mr19118181ilb.296.1570232153408; Fri, 04 Oct 2019 16:35:53 -0700 (PDT) MIME-Version: 1.0 References: <20191004215615.5479-1-sean.j.christopherson@intel.com> <20191004215615.5479-9-sean.j.christopherson@intel.com> In-Reply-To: <20191004215615.5479-9-sean.j.christopherson@intel.com> From: Jim Mattson Date: Fri, 4 Oct 2019 16:35:42 -0700 Message-ID: Subject: Re: [PATCH 08/16] KVM: VMX: Check for full VMX support when verifying CPU compatibility To: Sean Christopherson Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , "the arch/x86 maintainers" , Peter Zijlstra , Arnaldo Carvalho de Melo , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Tony Luck , Tony W Wang-oc , "H. Peter Anvin" , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Vitaly Kuznetsov , Wanpeng Li , Joerg Roedel , LKML , kvm list , linux-edac@vger.kernel.org, Borislav Petkov , Jarkko Sakkinen Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 4, 2019 at 2:56 PM Sean Christopherson wrote: > > Explicitly check the current CPU's VMX feature flag when verifying > compatibility across physical CPUs. This effectively adds a check on > IA32_FEATURE_CONTROL to ensure that VMX is fully enabled on all CPUs. > > Signed-off-by: Sean Christopherson Reviewed-by: Jim Mattson