From: Hamza Mahfooz <someguy@effective-light.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, regressions@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: KVM page-fault on Kernel 6.3.8
Date: Sat, 17 Jun 2023 15:27:25 -0400 [thread overview]
Message-ID: <PPWEWR.10XLY20A3VQ43@effective-light.com> (raw)
In-Reply-To: <ZIz3aPL3K6ZagyJ2@google.com>
On Fri, Jun 16 2023 at 04:59:36 PM -07:00:00, Sean Christopherson
<seanjc@google.com> wrote:
> What makes you think this is KVM related? I don't see anything KVM
> related in
Well, it corresponds a QEMU crash.
> the splat. The !PRESENT #PF is coming from aio_read(), not from KVM.
> The
> ?kvm_arch_vcpu_put line is just mispeculation from the unwinder.
prev parent reply other threads:[~2023-06-17 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 5:25 KVM page-fault on Kernel 6.3.8 Hamza Mahfooz
2023-06-16 12:49 ` Bagas Sanjaya
2023-06-16 13:30 ` Hamza Mahfooz
2023-06-16 23:59 ` Sean Christopherson
2023-06-17 19:27 ` Hamza Mahfooz [this message]
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=PPWEWR.10XLY20A3VQ43@effective-light.com \
--to=someguy@effective-light.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=seanjc@google.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