Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 17 Jun 2023 15:27:25 -0400
From:   Hamza Mahfooz <someguy@effective-light.com>
Subject: Re: KVM page-fault on Kernel 6.3.8
To:     Sean Christopherson <seanjc@google.com>
Cc:     kvm@vger.kernel.org, regressions@lists.linux.dev,
        linux-kernel@vger.kernel.org
Message-Id: <PPWEWR.10XLY20A3VQ43@effective-light.com>
In-Reply-To: <ZIz3aPL3K6ZagyJ2@google.com>
References: <L2ZBWR.TERFR10NPZ281@effective-light.com>
        <ZIz3aPL3K6ZagyJ2@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Precedence: bulk


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.