Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp780980pxy; Wed, 5 May 2021 13:49:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx0d8nPbW1KcVO4Iqi2gDZ2sknd4++A00MF5XWPwXP2SKs6USQmGoTlCoIhm1tm1CKVmNLc X-Received: by 2002:a63:b94b:: with SMTP id v11mr758137pgo.76.1620247789844; Wed, 05 May 2021 13:49:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620247789; cv=none; d=google.com; s=arc-20160816; b=b8HaXdqe02X5WtCyqaG+QZmqDOewuIgrj5QyBY/ZN/ytoiN5RiTO1oHo1JCfJjFc/C 7MPGoGQ1wLTzungJJ+Dk7IF4EsGHkr06qd6/oD0GI/uR4duYrKM86dXHuTGfxOONarAu Qb8b1etKCbaL6DUlOBfGN42Dj5Fq2NE1BfNQgw+ZjEu8NSJP44Nfdoi6nQWEg9MTZtv+ B9D4A6SB+5CLDbJRlYX72CNf2MrrPkvHYwIEDLW9SQ71nQk+sRXwgD6T2CJzKrwaUdHZ VkfOAo207WC+CZdB58KkAAONyoRPYrkbzvTaVn5GTYiejQ1nRtmn5AaYKvY3cPT9gdiu tN0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=kB18wOq0wwABF209vAjteUSBdk4dEBLdqvgC2SNz17Y=; b=F0xsnInsYJvnXS5zzyEkKZl1RY906jXhLC3oDTD3jCcwXbJZiqjSfTMPwmmioiKqPk N3uSOltBGEZGZRhgpfufTYXSw6dfqF1j4CupjYQd7V+2Znx+qwkTpLrfO1F3I0a42uzS 0/W3S9XGeEvHO4gWut/9bRF8I8PvEOjb9//Z77XbBXGT1lyQruOJ+kz0241ukftdG/GT X+Za0QUN+2d6V6desmIBzkwcQUQiRV0S4JUz0Ks3djuIyfoyyIFO2ArF5GT9QGdlvyZG FHjRvK2SXcvf0ax7hjyP2nAtzFbnvOSspU//18tKKUaAjfpe0od4T0XpOSXDSyJYfeJm Hgsw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Go46m6zi; 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 p10si196455plw.276.2021.05.05.13.49.37; Wed, 05 May 2021 13:49:49 -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=Go46m6zi; 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 S233452AbhEEPpJ (ORCPT + 99 others); Wed, 5 May 2021 11:45:09 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:28954 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229798AbhEEPpJ (ORCPT ); Wed, 5 May 2021 11:45:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620229452; 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=kB18wOq0wwABF209vAjteUSBdk4dEBLdqvgC2SNz17Y=; b=Go46m6zi3sbMRMK3WxGXGR1HK+j4TJPDe6hfG81qCzhDBs1zLZJ58CH656R0cCJzZuvb32 RbKaSq5YlcQiaoNzYC4kru6P30raJPz/apA8eiiamMu1RAct8JgZ/FtCmgFH1KCbhvzyeZ 9snN4lD4bU5QHS/UlvwT9AQjJzQrdv4= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-414--rjeofgLPzSsbLZUoC4qCw-1; Wed, 05 May 2021 11:44:10 -0400 X-MC-Unique: -rjeofgLPzSsbLZUoC4qCw-1 Received: by mail-wm1-f70.google.com with SMTP id b16-20020a7bc2500000b029014587f5376dso1563165wmj.1 for ; Wed, 05 May 2021 08:44:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kB18wOq0wwABF209vAjteUSBdk4dEBLdqvgC2SNz17Y=; b=RwoYMnXp1RTTA32V8XrTTrWGffeqdBvPJYnzuHju39a77F05WzW4J3hfwoodESMYuC jVc1PoPF/Gt6aauGJ3fVBZ0KSx4CXsHVHNn8ms+7fet2KWjblUmTlRHvB5T7BcrdYfDy TN6867IW+C1CV5jptjnQqkMSLT4lVPAVgME7cSCN7hDW42NSbGHQtYYpAzOKpU06dqEA WflmAQbPZGotXApSUQ4Hh8PMytrliDKMpH5zRiGiCErxWeFc9YNml5ykiDqEKSUZ1X6J SdvT+4+hGzXS4lIOiGYM0tfS4lZaNbKkKTgygWSHTmzTp+naZyWAVaoIUfYsWdBcuAVG LcCw== X-Gm-Message-State: AOAM530+xiCXckLqwv0AnvJepffTTDXEl+bgrEQBRPDYHcKVjj9tbQ3A lYIHvrQF9K5LIZeN9Zw5GUbDwYlVmAtEu2NvFlKv62RhyPlxiliSzE4YcJMI3RrgILkBvgiDF36 nyXZS6qQzx4Z/26htNa7zrBogqf2RGKrWMQWIBHM5e0cTtfHp/piqbGx2eoGiqw77PJRYGkucCA m4 X-Received: by 2002:a7b:c217:: with SMTP id x23mr10447923wmi.26.1620229449521; Wed, 05 May 2021 08:44:09 -0700 (PDT) X-Received: by 2002:a7b:c217:: with SMTP id x23mr10447895wmi.26.1620229449206; Wed, 05 May 2021 08:44:09 -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 61sm21723917wrm.52.2021.05.05.08.44.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 May 2021 08:44:08 -0700 (PDT) Subject: Re: [PATCH 0/3] KVM: selftests: evmcs_test: Check issues induced by late eVMCS mapping upon restore To: Vitaly Kuznetsov , kvm@vger.kernel.org Cc: Sean Christopherson , Wanpeng Li , Jim Mattson , Maxim Levitsky , linux-kernel@vger.kernel.org References: <20210505151823.1341678-1-vkuznets@redhat.com> From: Paolo Bonzini Message-ID: Date: Wed, 5 May 2021 17:44:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210505151823.1341678-1-vkuznets@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/05/21 17:18, Vitaly Kuznetsov wrote: > A regression was introduced by commit f2c7ef3ba955 > ("KVM: nSVM: cancel KVM_REQ_GET_NESTED_STATE_PAGES on nested vmexit"). When > L2->L1 exit is forced immediately after restoring nested state, > KVM_REQ_GET_NESTED_STATE_PAGES request is cleared and VMCS12 changes (e.g. > fresh RIP) are not reflected to eVMCS. The consequent nested vCPU run gets > broken. Add a test for the condition (PATCH2). PATCH1 is a preparatory > change, PATCH3 adds a test for a situation when KVM_GET_NESTED_STATE is > requested right after KVM_SET_NESTED_STATE, this is still broken in KVM > (so the patch is not to be committed). > > Vitaly Kuznetsov (3): > KVM: selftests: evmcs_test: Check that VMLAUNCH with bogus EVMPTR is > causing #UD > KVM: selftests: evmcs_test: Check that VMCS12 is alway properly synced > to eVMCS after restore > KVM: selftests: evmcs_test: Test that KVM_STATE_NESTED_EVMCS is never > lost > > .../testing/selftests/kvm/x86_64/evmcs_test.c | 150 +++++++++++++----- > 1 file changed, 108 insertions(+), 42 deletions(-) > Queued 1-2, thanks. Paolo