From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D163C43334 for ; Fri, 15 Jul 2022 15:58:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230099AbiGOP6X (ORCPT ); Fri, 15 Jul 2022 11:58:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57374 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229693AbiGOP6V (ORCPT ); Fri, 15 Jul 2022 11:58:21 -0400 Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C056F65D61 for ; Fri, 15 Jul 2022 08:58:20 -0700 (PDT) Received: by mail-pj1-x1032.google.com with SMTP id v4-20020a17090abb8400b001ef966652a3so11907946pjr.4 for ; Fri, 15 Jul 2022 08:58:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=xsKYhSLwsE8/SUXFxlsoQGizq/ndscv+1fEJX7G56IY=; b=WcGQ3p99TKasjnSfcWoBHd0IlimUMNYF7oGcVhFYwjkB1bYUS8HG3RfUQo9rksrGYI vmegpOSM1MfpWMTrkTNxNzAZT0+AiprGuV7mAdN0unBZI4+NN244skhoiJSAXDl4C7fJ 8T5Mw6gZtDzLfE75JYN817ArQfyivhjWJ3pScPwPOEsqURQES0odQuxCNJxwKG4Bmke5 j9O9SG72ZogYopzZnJrobPJot83KAwCreHM6aRrrQkCZ9EfFPYj16Lc7PiZKer59xpVg pR51RMvs8vIbYPzYWRqeSLJVnQHAznii+MgM2Rf+mIJX4WgmHw1pw8F9TVtyKw1a+NkM mXKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=xsKYhSLwsE8/SUXFxlsoQGizq/ndscv+1fEJX7G56IY=; b=n59A6QOaSry43hS7TU9s9YrfasRCeKZ1+nDhqBnIzcRSW7iL1h4fa+QRd8joI0zdmQ Qr2OxgHtcOY7chNHl68YpVXLSRk8DpaErsHZ3C8hFX2fnihoepkvjce1P5CINWMX2sq6 fkPGThFee2wNDzq+YiX+kYeQDh6wT6UkzeFy61bEVzHfyS4XG0i7UdofnE02zSZ2bsAN nPRGcVXJ7XEOACLTDhUzIOqbRTaBmOjSLrqug4TWsxdsYVtXhcEJHB1EI6uLS+ejT6xb uhCInOmYI3vnpZQeghqg5mPGJyClpIiwwUZwbczmcs9P+nAscaVT9XlqKfGuPHAJzoAU Lkcw== X-Gm-Message-State: AJIora8th3TXnJhcWpbVhxeN0FrsoIZ1oMgocO8vekFItaarqVSB/dTj 36X7Ly2Q6UN6Maa6YK68KK7MQykRyQs0kg== X-Google-Smtp-Source: AGRyM1tqzKoamzwlhHnc+IM9pZxIoOzEVydP45L6Isk2EsXkeVmHXci+zPyFL6vkZ7f5VwiGiuTyYA== X-Received: by 2002:a17:90b:341:b0:1e0:cf43:df4f with SMTP id fh1-20020a17090b034100b001e0cf43df4fmr16491919pjb.126.1657900700196; Fri, 15 Jul 2022 08:58:20 -0700 (PDT) Received: from google.com (123.65.230.35.bc.googleusercontent.com. [35.230.65.123]) by smtp.gmail.com with ESMTPSA id k2-20020a170902ce0200b0016c09e23b18sm3676427plg.154.2022.07.15.08.58.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Jul 2022 08:58:19 -0700 (PDT) Date: Fri, 15 Jul 2022 15:58:16 +0000 From: Sean Christopherson To: "Yang, Weijiang" Cc: Paolo Bonzini , Peter Zijlstra , x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, rick.p.edgecombe@intel.com Subject: Re: [PATCH 00/19] Refresh queued CET virtualization series Message-ID: References: <20220616084643.19564-1-weijiang.yang@intel.com> <62d4f7f0-e7b2-83ad-a2c7-a90153129da2@redhat.com> <8a38488d-fb6e-72f9-3529-b098a97d8c97@redhat.com> <2855f8a9-1f77-0265-f02c-b7d584bd8990@intel.com> <950988cd-708c-af25-9d0e-47062aded504@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <950988cd-708c-af25-9d0e-47062aded504@intel.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Fri, Jul 15, 2022, Yang, Weijiang wrote: > > On 7/15/2022 3:36 AM, Sean Christopherson wrote: > > It's definitely uncommon; unless I'm forgetting features, LA57 is the only feature > > that KVM fully virtualizes (as opposed to emulates in software) without requiring > > host enablement. Ah, and good ol' MPX, which is probably the best prior are since > > it shares the same XSAVE+VMCS for user+supervisor state management. So more than > > one, but still not very many. > > Speaking of MPX, is it really active in recent kernel? I can find little > piece of code at native side, instead, more code in KVM. Nope, native MPX support was ripped out a year or two ago. The kernel provides just enough save+restore support so that KVM can continue to virtualize MPX.