Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp3157773pxb; Tue, 12 Oct 2021 23:28:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxQDQF54VIYJ+aR6UKoFUFxevijUhV0A7u2plk64MCkirzqWiWzbzLXNYrpuipfgVeYQRY8 X-Received: by 2002:a17:902:74c7:b0:13f:48e1:3cd2 with SMTP id f7-20020a17090274c700b0013f48e13cd2mr11460127plt.33.1634106503984; Tue, 12 Oct 2021 23:28:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634106503; cv=none; d=google.com; s=arc-20160816; b=yDaGmP37WSf2oAFo7q50EXLUv+mLjaE7OToisbgijZweg9zJDpd8qvNC1y8oYbatVV 6T756xYJjw/XahyVGK418pEKor3S7VPRMwonUVRdFIBU3tlww8axKGSRgAxQrwf/CUPR 5AJD2xOn+Lu6OQhBqoE7M3T1jLgebotKdJTGDM00jrK87YxTOGzU14YWsIbcmeOfaPpK JDhfl0PbxMDNmd8zoeEwJRTA0B4w2N9XmnjP6qRAbJTa4x6SsY0TgE8IresZgU/qzuBD aJ5NKyXf80+N9v4PpArnlkyY+RtWpjKxe03YEiLXDgOEpQyy9BXtAew0+nYN9M5X+Kbt PXNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=M1r4UVSywHFrxKSzRmoAA2AVvVNlTRcwY3Az5uiDbcY=; b=GjFWzTx+/gfSBSwbZ4nurQ6s3A/xEnPi9TWQilzcgcq7Dw8RDK7V0J33z9lyjoPvly 9ZJ8w22quktyky/IsPd4Fj4P8qj/UgXKVJLWzcGsghxX9JQzgNkVFtz7NbCQ3fsR68iP e1+3Dsb9WLVUmPeyO/wIR+86O7And4XVJxNXBsftsGTeWi9Bv9ZxlIxJE+7t351w6DPU Vs+OHPU2SW+u8ix3CBIuE3dVonB+Q/9Eslpdaqyd5BiIA50jstLQVKJYRxHHqBWlinAL An7s0iLUQDLRhVgolrvqIryPaQq7CYqhA4OAzHxKmUFjsEAkctC+FdOV3ajdMm6yZ4Gi MZGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=LhGUiMm5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e25si6258369pgv.106.2021.10.12.23.28.10; Tue, 12 Oct 2021 23:28:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=LhGUiMm5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237916AbhJMG2r (ORCPT + 99 others); Wed, 13 Oct 2021 02:28:47 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:27987 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229781AbhJMG2q (ORCPT ); Wed, 13 Oct 2021 02:28:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634106403; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=M1r4UVSywHFrxKSzRmoAA2AVvVNlTRcwY3Az5uiDbcY=; b=LhGUiMm5EvVInZ4nW1mpWH7Yz3cP8nWdciDPmvJQE9SuYt5Sl5sH+SwVA3YtJd0AWd3Jeo sdApowZ/QCuoSBybGk875V3n0UqDs7V9VrxnpfrCK/hmv7SI48pQgd83qRMYHaABgXkZyr DM/m95cBu6FdbJKUXE3602KfFTZN1/U= Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-409-4laRA4nDO1i95GwIas1nfw-1; Wed, 13 Oct 2021 02:26:41 -0400 X-MC-Unique: 4laRA4nDO1i95GwIas1nfw-1 Received: by mail-ed1-f69.google.com with SMTP id g28-20020a50d0dc000000b003dae69dfe3aso1307654edf.7 for ; Tue, 12 Oct 2021 23:26:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=M1r4UVSywHFrxKSzRmoAA2AVvVNlTRcwY3Az5uiDbcY=; b=yFZwFWNkdv3U3uVqCrWWiTK2u3ObAsY7pX7sAw5sA+rRL4jlIOZwkKXYcqRP0AUoac Jd6vAoAATfL7qaVXX9vgjGem1AkEkFCCQMWXJgsP33lFPZzW038hRFfJOqbAH+86s23c xPO8N6UONe8e3raNPghsc7yjagspxhqn+OqBRSaT5C3e8X4MjiwBpJeuakhXOVmaFj63 3gtpgibxim5e0bmyxwYlocmkhpy7k7lOfaxVQ1fzuR/p9Qfv7Ca9dzhcE0VEWXUqbvwa DVt01BsXjPZF3JaVi/QCD0X5j0qjHo1geuoBpMaxSHpx5Es+GbVICLC44ENwC/e6+SzM XTLA== X-Gm-Message-State: AOAM532GDggQoxDyk+Zt0XhO4oWNKwCmDvVEFJfyBmN2kBSYDqns450w kmokd1FTnnLLOikPKZyiU4NNUDohutbLkEx23rT1Scyn8d5EldB6sA64WUaVViZFHgCXsRioH0q n675AhIJoTOx2BDus+SK70OMx X-Received: by 2002:a17:906:3715:: with SMTP id d21mr39321984ejc.74.1634106400732; Tue, 12 Oct 2021 23:26:40 -0700 (PDT) X-Received: by 2002:a17:906:3715:: with SMTP id d21mr39321958ejc.74.1634106400457; Tue, 12 Oct 2021 23:26:40 -0700 (PDT) Received: from ?IPV6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id k19sm5933406ejg.13.2021.10.12.23.26.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Oct 2021 23:26:39 -0700 (PDT) Message-ID: <0962c143-2ff9-f157-d258-d16659818e80@redhat.com> Date: Wed, 13 Oct 2021 08:26:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.1.0 Subject: Re: [patch 13/31] x86/fpu: Move KVMs FPU swapping to FPU core Content-Language: en-US To: "Liu, Jing2" , Thomas Gleixner , LKML Cc: "x86@kernel.org" , "Bae, Chang Seok" , Dave Hansen , Arjan van de Ven , "kvm@vger.kernel.org" , "Nakajima, Jun" , Jing Liu , "seanjc@google.com" References: <20211011215813.558681373@linutronix.de> <20211011223611.069324121@linutronix.de> <8a5762ab-18d5-56f8-78a6-c722a2f387c5@redhat.com> From: Paolo Bonzini In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/10/21 08:15, Liu, Jing2 wrote: > After KVM passthrough XFD to guest, when vmexit opening > irq window and KVM is interrupted, kernel softirq path can call > kernel_fpu_begin() to touch xsave state. This function does > XSAVES. If guest XFD[18] is 1, and with guest AMX state in register, > then guest AMX state is lost by XSAVES. Yes, the host value of XFD (which is zero) has to be restored after vmexit. See how KVM already handles SPEC_CTRL. Passthrough of XFD is only enabled after the guest has caused an #NM vmexit and the full XSAVE state has been dynamically allocated, therefore it is always possible to do an XSAVES even from atomic context. Paolo