Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp4621695pxb; Tue, 25 Jan 2022 14:45:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJwm3J+jl7FMHqoAy1BdmnqjOnM6NC7Qp7FNJvhOT/nPaxHZtQ0z2tJi2xb5lETjRj9sViS8 X-Received: by 2002:a17:906:7306:: with SMTP id di6mr17538245ejc.93.1643150712477; Tue, 25 Jan 2022 14:45:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643150712; cv=none; d=google.com; s=arc-20160816; b=dUxTXK35eiQXQYEBV/LpWolXKvNd80cYzAzl6ojldoLuZ40yMOvPFTYGGwV6qCIhcp RRxb0VZ4Ah9qe9IRvqERFWFe2acUNCr5/1U2blt5YflyIvW9Pw5b425oQ3C2FDhg+DKK jlZ287/N+XPNllECA0f1cNcGmsx4JgB9MKHT662BxXQyWyHuZ6vOVleBAvHEqlOJVH4P +qXTzEQKkRvizurw0B6Kun3A7EnLuWOZGbCsNQ1cJK3eDB46K76mUZDkWcBIZewJur7S 8iMk6bhELsc5bJ51M28VSaHfGlutlbYixDe2jeQd8uHRdMcXZ0gqxiKP/SHYRl1j2SZx 2hOw== 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=000N8i0ck0tOaQfaIosTwzm6+d1XOHKA+Or39H8w7yU=; b=D4lUZL+Xfhticg1VkzgGCE20I7wZHw4GDPv79gSp6iF5XdYTfuhwSIKrLe08XG8jQh xQMX0Kao/BKleuJOe0WL4WWwB0MNmpi9wim42WkQmiFr1NaKV8nb4SY8cgD9nbhPzGEG 52H92HLxd6r6wRduyhIZnx1ElgL0e5Al9bNK6HkgdczDmusHG11Ku59P+Ar08gspVXxw YxFc0D6ltOIooCVF1gWt/CIOB3RksK8nB9nnmyX2sPnqUvTxxrGPUPA1OQRoXFmvY4ut gzohSyvjHIsmwDEkX24eUeUsOhW9gr9jXjdDIiK15+0ItZaYYa5B9x+lTIq6Bm9EU4Z+ Rt/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U2g3dz1y; 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 g3si2995096edr.256.2022.01.25.14.44.48; Tue, 25 Jan 2022 14:45:12 -0800 (PST) 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=U2g3dz1y; 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 S1357873AbiAYOys (ORCPT + 99 others); Tue, 25 Jan 2022 09:54:48 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:45077 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1580799AbiAYOwd (ORCPT ); Tue, 25 Jan 2022 09:52:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643122351; 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=000N8i0ck0tOaQfaIosTwzm6+d1XOHKA+Or39H8w7yU=; b=U2g3dz1yPLwkFzEk0cboxsBoQzKHfH4LFvKe1vpLgOFDYEGX5C6w9c1CqgUd7c7fWUBjvd QnVeVP1RIu0XUnF04pw6gV0QMtVNxLGsOH2p6CPPEmRq7P1CjW4xx82TkchMG4g4pky8zK 7Mc16yp+ouqPkXZyuORhh0Ki0c1Ichg= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-189-uMLFNgDPPuaAoTbFdeoK9w-1; Tue, 25 Jan 2022 09:52:29 -0500 X-MC-Unique: uMLFNgDPPuaAoTbFdeoK9w-1 Received: by mail-ed1-f70.google.com with SMTP id i22-20020a50fd16000000b00405039f2c59so11074543eds.1 for ; Tue, 25 Jan 2022 06:52:29 -0800 (PST) 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=000N8i0ck0tOaQfaIosTwzm6+d1XOHKA+Or39H8w7yU=; b=119TT9S9BuihVtkNPzopOQ7+JUQ5VVs794mRyDgtOkfyOKsbTEUTLvYjwSbqn7+H42 awEuseaQ2Es6YWLGvgO4DLfJ/bcEIkyUEEaOXvhbmRihjLomwuUYWtvt8NYTeON3BPnF JpaFZpQ++m2pmXcozcJ9G/mfvJUCB5wJQYWO8FiyIVQMFbXYfCokahg8VK7MmxKe3DvU Ek9N16Ve4oDWcVrhak5KTs6Y01BQpTuLVxk66xFrxBhm/AIcW+vktJd4qYlB+8wT+7kl 12rqIKOWBzdD4/C1MTWTGg7HwrPEA5iFQb9qo2onPawdt8XiuXZ+hV0KodmnEITI+3/W hLrg== X-Gm-Message-State: AOAM531Xr7cfTUYvnp+GFBm+Gja4j+u8CjLJGYZynZYwqASa1OvTj8Ww RLQZDNfHG9zAS97Zvqj93eWvvMQaCb9kOSI0bqiCPpuzI0OVQwsigjHvgvomhwJcN4X2oscU06d Eg/EYoDoMlvwe0vUCdt83IagX X-Received: by 2002:a17:906:5d0f:: with SMTP id g15mr16299069ejt.670.1643122348431; Tue, 25 Jan 2022 06:52:28 -0800 (PST) X-Received: by 2002:a17:906:5d0f:: with SMTP id g15mr16299058ejt.670.1643122348252; Tue, 25 Jan 2022 06:52:28 -0800 (PST) Received: from ?IPV6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.googlemail.com with ESMTPSA id t6sm6172259ejd.85.2022.01.25.06.52.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 25 Jan 2022 06:52:27 -0800 (PST) Message-ID: Date: Tue, 25 Jan 2022 15:52:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.4.0 Subject: Re: [PATCH 0/9] KVM: SVM: Fix and clean up "can emulate" mess Content-Language: en-US To: Sean Christopherson Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Tom Lendacky , Brijesh Singh , Liam Merwick References: <20220120010719.711476-1-seanjc@google.com> From: Paolo Bonzini In-Reply-To: <20220120010719.711476-1-seanjc@google.com> 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 1/20/22 02:07, Sean Christopherson wrote: > Revert an amusing/embarassing goof reported by Liam Merwick, where KVM > attempts to determine if RIP is backed by a valid memslot without first > translating RIP to its associated GPA/GFN. Fix the underlying bug that > was "fixed" by the misguided memslots check by (a) never rejecting > emulation for !SEV guests and (b) using the #NPF error code to determine > if the fault happened on the code fetch or on guest page tables, which is > effectively what the memslots check attempted to do. > > Further clean up, harden, and document SVM's "can emulate" helper, and > fix a #GP interception SEV bug found in the process of doing so. > > Sean Christopherson (9): > KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests > Revert "KVM: SVM: avoid infinite loop on NPF from bad address" > KVM: SVM: Don't intercept #GP for SEV guests > KVM: SVM: Explicitly require DECODEASSISTS to enable SEV support > KVM: x86: Pass emulation type to can_emulate_instruction() > KVM: SVM: WARN if KVM attempts emulation on #UD or #GP for SEV guests > KVM: SVM: Inject #UD on attempted emulation for SEV guest w/o insn > buffer > KVM: SVM: Don't apply SEV+SMAP workaround on code fetch or PT access > KVM: SVM: Don't kill SEV guest if SMAP erratum triggers in usermode > > arch/x86/include/asm/kvm_host.h | 3 +- > arch/x86/kvm/svm/sev.c | 9 +- > arch/x86/kvm/svm/svm.c | 162 ++++++++++++++++++++++---------- > arch/x86/kvm/vmx/vmx.c | 7 +- > arch/x86/kvm/x86.c | 11 ++- > virt/kvm/kvm_main.c | 1 - > 6 files changed, 135 insertions(+), 58 deletions(-) > > > base-commit: edb9e50dbe18394d0fc9d0494f5b6046fc912d33 Queued, thanks. Paolo