Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2102374pxj; Sat, 19 Jun 2021 03:02:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzZBKQp7RDCOMcuEljEKNwZP+NYk2cCXU8FAaAYIxeLX028YauuuHqqVltv+bE6dVmf8Pxt X-Received: by 2002:a92:1310:: with SMTP id 16mr11098932ilt.60.1624096920698; Sat, 19 Jun 2021 03:02:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624096920; cv=none; d=google.com; s=arc-20160816; b=GFW46K/nF86ToWPdqmIgdb88zeAiHD+e/gpNxMaayz/csWN5Z0no+eCmZ/2P1ahdWH GrzI+0ooBHUHRNNidUUjuY2WBROZXgLgZ/bF2Sfi/9m9eLUmOk32BpZSCJ9I89a502GR K9UyJgBv59XPBSM/tnIjuzExMyuHSy+pz9SI2wmca8ACiFJe96GMuI+Lr5dxvwihTSv/ PUW1mc0bcwWz5upTX5v0nuFfh5KElD0FbeBDWRwJbwMAEVZZBNmvobXF72wwmY5O3wIS BTJ+foCgUEpSDT6jCuQPjxBam6psXMWtsyUTBjOqpxUo5YMt1LOxdKmkS8XXJzzmkjvD qrEA== 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=8ML4REiy5OkcaqfJ6brk7+RfQQvQg3ZqoRzOqMYC4CQ=; b=0i8x7yQdcvwoOW0ddzMx+8NdYZyaIsk+ZeRyVqPCNd8APibIlblxGb3JKgejwPQf9u MR/8FBDzBpCCd7m3lTvIt7tcY+c7PdPvNKZbrZLd0fPbuA2rOqcnP5CkIkDGUzjgZwNG dkW/btN8MgFa0DwwlJpAALApaan6Kghs9dBhBBZOGWkZy7yfYRFMJlFuc3aCp5QaIyr9 2Za2lzDG/T+c2dRtmiVywBC/8+nsf1SeP+NuZVP+uSW2L8aze0GWAwY1cVgNaNVGBXwU KtqSv7dPGLKViQUmZGvp4W4aW+lWcyJCIcoPeFthzNFNDM/zkA/s4Z64XbvQkU9BEbMR oM3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=J0F5GsHh; 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 v20si10030797jas.13.2021.06.19.03.01.48; Sat, 19 Jun 2021 03:02:00 -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=J0F5GsHh; 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 S234174AbhFSHF3 (ORCPT + 99 others); Sat, 19 Jun 2021 03:05:29 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:53714 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234152AbhFSHF1 (ORCPT ); Sat, 19 Jun 2021 03:05:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624086196; 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=8ML4REiy5OkcaqfJ6brk7+RfQQvQg3ZqoRzOqMYC4CQ=; b=J0F5GsHhMdf4BjcqmRPbvxjekUgLvI8ieIlqkO+70qHtKV/eoSgGnb4CRKOZTdUAGtzPKe Dt/NNKKWK5OPBPGQ9nNJ2RT0HATEAatgN9CHg5AFwI9RXhmIlqNCyz27mmtrcEyTCyKunB YTAmIpKU/GxGZeXwEmh7hPdQAP+/QGI= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-47-GdmviMEJMi2d4cU9ewjF6A-1; Sat, 19 Jun 2021 03:03:15 -0400 X-MC-Unique: GdmviMEJMi2d4cU9ewjF6A-1 Received: by mail-ed1-f71.google.com with SMTP id p23-20020aa7cc970000b02903948bc39fd5so2452362edt.13 for ; Sat, 19 Jun 2021 00:03:15 -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=8ML4REiy5OkcaqfJ6brk7+RfQQvQg3ZqoRzOqMYC4CQ=; b=SgNODYcExhybP52FWTszqWZ4MowM26YprfRQCMRx7qufqBkN8DqSfHYYuuU64iMvHm 7+yRtahN/S5UiIaBWAw2aSxlBNrzqHc2rr2+GJaxsFKgKRspRXcjjxctp7ik+L/pzlJo D4fIMSRswqbyrGovKWMssh29zi4LxQwW2tnsdy9txI2LA5L4pwYYGDO5ew2aSWTqjlHL 2qSkEWz78JCh+i2b7vYKS07kYjCDTeNKzw527Gf0Sv3jYQD7sgkV/r17Hck755Er7uGL M2jxhrP4gROxQyIwmYIy0dnkBRmH9TLAq2xTL6AmduXvC6TL1wcFBeUKOcBoHtxWSbj9 Kx/w== X-Gm-Message-State: AOAM530vT4hY+Hs/akEHM3XZhtQCNpea9gaKFXfiwMA/BdXSHfmr8eVP byNWtpGuCq7ekebGmJj+ir7g0PjnIo/B7NevUJfMj502TLxsSk00+RjupJsXdwFRp/UM5eT0HNA EWy5XGkINM1/Ni9r0BmVFa0HR X-Received: by 2002:a05:6402:2317:: with SMTP id l23mr9400537eda.265.1624086194034; Sat, 19 Jun 2021 00:03:14 -0700 (PDT) X-Received: by 2002:a05:6402:2317:: with SMTP id l23mr9400523eda.265.1624086193880; Sat, 19 Jun 2021 00:03:13 -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 hx18sm448140ejc.82.2021.06.19.00.03.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 19 Jun 2021 00:03:13 -0700 (PDT) Subject: Re: [PATCH v3 8/8] KVM: x86: avoid loading PDPTRs after migration when possible To: Sean Christopherson , Maxim Levitsky Cc: kvm@vger.kernel.org, open list , "open list:DOCUMENTATION" , Wanpeng Li , Ingo Molnar , Vitaly Kuznetsov , Thomas Gleixner , Borislav Petkov , Joerg Roedel , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Jim Mattson , Jonathan Corbet , "H. Peter Anvin" References: <20210607090203.133058-1-mlevitsk@redhat.com> <20210607090203.133058-9-mlevitsk@redhat.com> From: Paolo Bonzini Message-ID: <289ac328-703f-6eb0-292e-99b1eda08784@redhat.com> Date: Sat, 19 Jun 2021 09:03:11 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: 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 18/06/21 22:53, Sean Christopherson wrote: > The bool is essentially an extension of > KVM_REQ_GET_NESTED_STATE_PAGES, I think it makes sense to clear the flag whenever > KVM_REQ_GET_NESTED_STATE_PAGES is cleared. So in vcpu_enter_guest? > Another thing that's not obvious is the required ordering between KVM_SET_SREGS2 > and KVM_SET_NESTED_STATE. AFAICT it's not documented, but that may be PEBKAC on > my end. E.g. what happens if walk_mmu == &root_mmu (L1 active in targte KVM) > when SET_SREGS2 is called, and_then_ KVM_SET_NESTED_STATE is called? Either ordering should work. Paolo