Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Wed, 8 Jun 2022 08:37:48 +0800
From:   Yuan Yao <yuan.yao@linux.intel.com>
To:     Sean Christopherson <seanjc@google.com>
Cc:     Yuan Yao <yuan.yao@intel.com>, kvm@vger.kernel.org,
        linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
        Vitaly Kuznetsov <vkuznets@redhat.com>,
        Wanpeng Li <wanpengli@tencent.com>,
        Jim Mattson <jmattson@google.com>,
        Joerg Roedel <joro@8bytes.org>, Kai Huang <kai.huang@intel.com>
Subject: Re: [PATCH 1/1] KVM: MMU: Fix VM entry failure and OOPS for shdaow
 page table
Message-ID: <20220608003747.zge6mfe75cnk4n57@yy-desk-7060>
References: <20220607074034.7109-1-yuan.yao@intel.com>
 <Yp9nsbNzoIEyJeDv@google.com>
 <20220607233045.a3sz7v2u6cdeg3sb@yy-desk-7060>
 <Yp/hiOxrOhEuIWj6@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Yp/hiOxrOhEuIWj6@google.com>
User-Agent: NeoMutt/20171215
Precedence: bulk

On Tue, Jun 07, 2022 at 11:38:48PM +0000, Sean Christopherson wrote:
> On Wed, Jun 08, 2022, Yuan Yao wrote:
> > On Tue, Jun 07, 2022 at 02:58:57PM +0000, Sean Christopherson wrote:
> > > Everything below here can be dropped as it's not relevant to the original bug.
> > >
> > > E.g. the entire trace can be trimmed to:
> >
> > Ah, I thought that the original trace carries most information
> > which maybe useful to other people. Let me trim them as you
> > suggested in V2, thanks.
>
> For bug reports, it's helpful to have the raw trace as the context is useful for
> debug.  But for changelogs, the goal is only to document the failure signature,
> e.g. so that reviewers understand what broke, users that encounter a similar splat
> can find a possible fix, etc...

I got it, I will send a new v1 patch with new subject for this:
KVM: x86/mmu: Set memory encryption "value", not "mask", in shadow PDPTRs