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 X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8E53C4363D for ; Fri, 2 Oct 2020 17:31:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 55C9F2085B for ; Fri, 2 Oct 2020 17:31:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="gAlF4Fb9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388264AbgJBRbE (ORCPT ); Fri, 2 Oct 2020 13:31:04 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:27156 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388225AbgJBRbD (ORCPT ); Fri, 2 Oct 2020 13:31:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1601659861; 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=TxOHOh0IIejZk+BuR1OyBgwvkUAEztBJORaBCqWyOAI=; b=gAlF4Fb9O5p+bwmkrO3IQWzUsbDWwBUIIKUgIbfPUEOA9oIyL+m9zqL9PwIqFWNG/DgtPO z7gKvzm1WyO9P1hY6sRNfnnBJKGYQOpJW0YKn3wZrXugURbV7VB0NOmuGGFEYSiDZ3Xwhi NL6nHfS6lkZyX7hIMF0xhxdUfdB8KH8= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-299-SKQtrNIrP2u3nBhczPgn8A-1; Fri, 02 Oct 2020 13:30:59 -0400 X-MC-Unique: SKQtrNIrP2u3nBhczPgn8A-1 Received: by mail-wm1-f69.google.com with SMTP id m14so263137wmi.0 for ; Fri, 02 Oct 2020 10:30:59 -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=TxOHOh0IIejZk+BuR1OyBgwvkUAEztBJORaBCqWyOAI=; b=EPAp7kqgAWxhJWr34LVXt9zt4O6JbFj0R6KQpha/rOayiFMheSgh3zQjTjkQr4hoh5 gyz3EOgbOINpW1KNDMNp2VEvjSQL8hdkC/PKhZi4BVVq4PeoAT6d5Jxv1d7Ev511pa7V X+/BsvaCM6Sze7cUZt+LVqP0XJAkr4j+oV3YzP9bBqJ5mpxCh6fo4SeIIu/PEtBK2Og0 6Nswr8qXqWIbhz9P6IPZUyAfMAvQfDKpF8Vt+cXm8tzP6dMzqWayCAHHSJJuNfWrS20k wuOZ5uJB6mqjwiUpX8D84wrRgwncguiIqE3ztHXO/WvSi4xItS0d1iN/R4ujpZ2X0ocK REAA== X-Gm-Message-State: AOAM533wv6rabdj3bXCo/tkBrHFCPoEFIM33wy5kKDSgBxNbkqQThPzb nt08pnCsfXvx8H3UnZbAjR87zGZcVOD235ekJfhJuK5+BYFH0jD5vuJ1LBTrhiG57dkaPzR0YD2 g86Z5Lf6pNLedq78XiIBWiA== X-Received: by 2002:a7b:c0c1:: with SMTP id s1mr4244454wmh.73.1601659858185; Fri, 02 Oct 2020 10:30:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzxM8WopKn+E/7ZEMfQTo4iJ+AulaHlScB3Vysd80PrpI/qioSdeZTkZO1byHJi2o6MFioQsA== X-Received: by 2002:a7b:c0c1:: with SMTP id s1mr4244432wmh.73.1601659857933; Fri, 02 Oct 2020 10:30:57 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:47e0:e742:75ba:b84d? ([2001:b07:6468:f312:47e0:e742:75ba:b84d]) by smtp.gmail.com with ESMTPSA id o194sm2808207wme.24.2020.10.02.10.30.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 02 Oct 2020 10:30:57 -0700 (PDT) Subject: Re: [PATCH] KVM: x86: VMX: Make smaller physical guest address space support user-configurable To: Naresh Kamboju Cc: Qian Cai , Mohammed Gamal , kvm list , open list , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Stephen Rothwell , Linux-Next Mailing List , Linus Torvalds , lkft-triage@lists.linaro.org References: <20200903141122.72908-1-mgamal@redhat.com> <1f42d8f084083cdf6933977eafbb31741080f7eb.camel@redhat.com> <2063b592f82f680edf61dad575f7c092d11d8ba3.camel@redhat.com> From: Paolo Bonzini Message-ID: <68a67f54-af5c-8b33-6b87-a67ccbbfc155@redhat.com> Date: Fri, 2 Oct 2020 19:30:56 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On 02/10/20 19:28, Naresh Kamboju wrote: >> >> commit 608e2791d7353e7d777bf32038ca3e7d548155a4 (HEAD -> kvm-master) >> Author: Paolo Bonzini >> Date: Tue Sep 29 08:31:32 2020 -0400 >> >> KVM: VMX: update PFEC_MASK/PFEC_MATCH together with PF intercept >> >> The PFEC_MASK and PFEC_MATCH fields in the VMCS reverse the meaning of >> the #PF intercept bit in the exception bitmap when they do not match. >> This means that, if PFEC_MASK and/or PFEC_MATCH are set, the >> hypervisor can get a vmexit for #PF exceptions even when the >> corresponding bit is clear in the exception bitmap. >> >> This is unexpected and is promptly reported as a WARN_ON_ONCE. >> To fix it, reset PFEC_MASK and PFEC_MATCH when the #PF intercept >> is disabled (as is common with enable_ept && !allow_smaller_maxphyaddr). > I have tested this patch on an x86_64 machine and the reported issue is gone. > Thanks, the issue with my disk is gone too so it'll get to Linus in time for rc8. Paolo