Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1154364rwl; Wed, 12 Apr 2023 08:59:32 -0700 (PDT) X-Google-Smtp-Source: AKy350YcHUdg3m/uIMJFsJHteaoVoBb6FMIehe8ksafdBnTFP08uy3EsIeu8erUAevACqte9rVNw X-Received: by 2002:a17:902:cec8:b0:1a1:80ea:4364 with SMTP id d8-20020a170902cec800b001a180ea4364mr24525642plg.31.1681315172303; Wed, 12 Apr 2023 08:59:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681315172; cv=none; d=google.com; s=arc-20160816; b=QzZ+HuKQIwmiTyko8s+Tw9xjwnYv6RlWBzWHUli50T041JaW0dmg8YYXKY9Pb+cG+q ykA+WtDv4a5Nr0I81YOnPiz9EmOX8BIv/n9AAiuRStwncsYAEHPUQZPMA3gG1jwRf6Nb tnYngGVwWvRzUbdJPnvZZAT0iEEseZRihAGsCFAFaniJh9aoJWBS4WYokrc5nBkdbxXe lnh/DVFEp/iWVbtIg1T1k8TxClhooGwKkIMjml0BD2rJMq+uLp62JO75UqkJo0C36kqK YnT+kodBrMchZ6UKFqYAMOKJwfDCHv65065nV5LlcaaLKTqZw1OcuIsvR61CaFHtT82c iZjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:dkim-signature; bh=Ogzsp2Zb5oW4pVyV0bLaflVZnjMH0psN7OLO8aR9z+U=; b=sGzqzKLEUbi+LiWWt2s2Hn6IWUDm+c3EKJ+zp+E8lHMPh5uu70GPLq3XT7+Stq3z3a TN39fz1XQVuO4Gn8+fHK201ofgIte+DRjQyfTUP2QsDp/d+mlOsMEehlViMCdwTYmGH2 RPkd7DwdiipYf76UsN1JbnJmDKmjXvKMezBL/SbGFx1QMnZm58TGjp9TZDMKYUehJInO 5WWjbvVLLgAonrNf+wp5HYvWnVkw1ByBf37ZqTHvAXX8yQnnZy8HfxMi6xWiA+F3ndLC /gv1vO5jw/TzZiuzqgy3lDzcDHgS7okWI9A9X3dOUbtncrhP+3ebLxSFGLoN5wy/05W9 I1bg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=P4Q77Dt8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a191-20020a6390c8000000b0051805159a1csi12149736pge.476.2023.04.12.08.59.16; Wed, 12 Apr 2023 08:59:32 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b=P4Q77Dt8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S231220AbjDLPvE (ORCPT + 99 others); Wed, 12 Apr 2023 11:51:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52234 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230329AbjDLPvB (ORCPT ); Wed, 12 Apr 2023 11:51:01 -0400 Received: from mail-yb1-xb4a.google.com (mail-yb1-xb4a.google.com [IPv6:2607:f8b0:4864:20::b4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BC09D6584 for ; Wed, 12 Apr 2023 08:50:59 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id 132-20020a250c8a000000b00b8f4e12dd57so838544ybm.1 for ; Wed, 12 Apr 2023 08:50:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1681314659; x=1683906659; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=Ogzsp2Zb5oW4pVyV0bLaflVZnjMH0psN7OLO8aR9z+U=; b=P4Q77Dt8KKqjxsvadieiyCHUhDBtlNXfW4kerlliv/IuwMrcjORNbIAEEjp/LVCboY HE5sHotnLn1MCziHYz1yqsm4UMSp9t6ScPEthqJB0oKYv5vLM9kSRMwMT4uR8sOe80Zk IdtyYqfBBGlMdG+wZcCAN8aMwYzx2oyWRXRWULawNtqeogSN+oLTau7yYNPB7S0T0+Xg /SSk6bxpEBgArcYHASwZZaoy3CMnY9Gufg81WUuJA+YBvAv8s+jhTicuGRQjr0nDlZB4 5W/N28B56BxoVOYe3AnhrNT4tSS+SlxFOLaTtiqSyIxZwaOwggBOIFgJ++T2hcm2arRa yjEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681314659; x=1683906659; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Ogzsp2Zb5oW4pVyV0bLaflVZnjMH0psN7OLO8aR9z+U=; b=UEbKzJk7Gp9TMlAJ9AR0ARCQIL4IFxgVMgyBmEq+qbNdWgAJGpm3IS8Gpxnq8bG5J6 W3VReMha5uqHyRX52gIsxtXQ5qIjdk/VKS8C3wHLB4xjqHLzgdo+p7Le65l74sDf2iUj rXmRAFqoXz33eS79x5ZLcTacoDawbwLE1KWvxaEXBeXW1HAvr8nvuaaBgCNJ/5Urqg23 7avE1YPQrwlGyf9JQtcyRCqjlsk/OXquSOxVRYEs70zeN0TudfWNiubhxKRCPfx56M6u Fy/2E0jVKRG0DSbulNzsjq+CFsi4XaoXElyVhnCezaeKgKvbC+FL+ABn2w/zxtIVvqzv oBmg== X-Gm-Message-State: AAQBX9ftXwNU9OD7Wj9FLsYkoq8+wgY/7B523OVNloQsQA1y5g1p/GRi 7a64FNEIp7bILsC2OA8NKv3xYvUbw9E= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a81:eb08:0:b0:54f:97dd:633 with SMTP id n8-20020a81eb08000000b0054f97dd0633mr1398481ywm.4.1681314659054; Wed, 12 Apr 2023 08:50:59 -0700 (PDT) Date: Wed, 12 Apr 2023 08:49:43 -0700 In-Reply-To: <20230405004520.421768-1-seanjc@google.com> Mime-Version: 1.0 References: <20230405004520.421768-1-seanjc@google.com> X-Mailer: git-send-email 2.40.0.577.gac1e443424-goog Message-ID: <168123371052.1068870.10975257258289226380.b4-ty@google.com> Subject: Re: [PATCH v4 0/6] KVM: x86: Fix unpermitted XTILE CPUID reporting From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Aaron Lewis , Mingwei Zhang , Jim Mattson Content-Type: text/plain; charset="utf-8" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 04 Apr 2023 17:45:14 -0700, Sean Christopherson wrote: > This is v4 of Aaron's "Clean up the supported xfeatures" series. > > Fix a bug where KVM treats/reports XTILE_CFG as supported without > XTILE_DATA being supported if userspace queries the supported CPUID but > doesn't request access to AMX, a.k.a. XTILE_DATA. If userspace reflects > that CPUID info back into KVM, the resulting VM may use it verbatim and > attempt to shove bad data into XCR0: XTILE_CFG and XTILE_DATA must be > set/cleared as a pair in XCR0, despite being enumerated separately. > > [...] Applied to kvm-x86 selftests (due to the dependencies on the earlier AMX selftests rework). Thanks! [1/6] KVM: x86: Add a helper to handle filtering of unpermitted XCR0 features https://github.com/kvm-x86/linux/commit/6be3ae45f567 [2/6] KVM: x86: Filter out XTILE_CFG if XTILE_DATA isn't permitted https://github.com/kvm-x86/linux/commit/55cd57b596e8 [3/6] KVM: selftests: Move XGETBV and XSETBV helpers to common code https://github.com/kvm-x86/linux/commit/b213812d3f4c [4/6] KVM: selftests: Rework dynamic XFeature helper to take mask, not bit https://github.com/kvm-x86/linux/commit/7040e54fddf6 [5/6] KVM: selftests: Add all known XFEATURE masks to common code https://github.com/kvm-x86/linux/commit/28f2302584af [6/6] KVM: selftests: Add test to verify KVM's supported XCR0 https://github.com/kvm-x86/linux/commit/03a405b7a522 -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes