[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220608003747.zge6mfe75cnk4n57@yy-desk-7060>
Date: Wed, 8 Jun 2022 08:37:48 +0800
From: Yuan Yao <yuan.yao@...ux.intel.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Yuan Yao <yuan.yao@...el.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, Kai Huang <kai.huang@...el.com>
Subject: Re: [PATCH 1/1] KVM: MMU: Fix VM entry failure and OOPS for shdaow
page table
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
Powered by blists - more mailing lists