From: Sean Christopherson <seanjc@google.com>
To: Yuan Yao <yuan.yao@linux.intel.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
Date: Tue, 7 Jun 2022 23:38:48 +0000 [thread overview]
Message-ID: <Yp/hiOxrOhEuIWj6@google.com> (raw)
In-Reply-To: <20220607233045.a3sz7v2u6cdeg3sb@yy-desk-7060>
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...
next prev parent reply other threads:[~2022-06-08 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 7:40 [PATCH 1/1] KVM: MMU: Fix VM entry failure and OOPS for shdaow page table Yuan Yao
2022-06-07 7:44 ` Kai Huang
2022-06-07 14:58 ` Sean Christopherson
2022-06-07 23:30 ` Yuan Yao
2022-06-07 23:38 ` Sean Christopherson [this message]
2022-06-08 0:37 ` Yuan Yao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yp/hiOxrOhEuIWj6@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=yuan.yao@intel.com \
--cc=yuan.yao@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox