From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: x86: missing FRED #PF event data?
Date: Mon, 10 Aug 2026 19:40:15 +0900 [thread overview]
Message-ID: <anmpv_7_YN2Fyj5J@google.com> (raw)
In-Reply-To: <20260810110624.06a86a74@pumpkin>
On (26/08/10 11:06), David Laight wrote:
[..]
> > > Can you reproduce on real hardware? I mean, you were babbling about pKVM
> > > (whatever that is), so I'm thinking you're on some dodgy virt thing.
> > >
> > > Not that I have any actual FRED hardware to test anything on :/
> >
> > It's an actual H/W, a laptop (Intel(R) Core(TM) Ultra 7 355 powered),
> > I was babbling about pKVM because it seems that the best way to
> > reproduce is to launch a VM, yet the crash is happening on the host
> > side.
> >
>
> Is the same fault processed correctly from userspace?
> If not it might be easier to test.
I'll look into it. So far I'm aware of crashes when people run VMs,
and somehow it's always that page-crossing csum load. There might
be other crashes, but I'm only aware of that one.
next prev parent reply other threads:[~2026-08-10 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 6:49 x86: missing FRED #PF event data? Sergey Senozhatsky
2026-08-10 7:38 ` Sergey Senozhatsky
2026-08-10 8:58 ` Sergey Senozhatsky
2026-08-10 9:03 ` Peter Zijlstra
2026-08-10 9:09 ` Sergey Senozhatsky
2026-08-10 9:23 ` Peter Zijlstra
2026-08-10 13:51 ` Sean Christopherson
2026-08-10 14:47 ` Sergey Senozhatsky
2026-08-10 10:06 ` David Laight
2026-08-10 10:40 ` Sergey Senozhatsky [this message]
2026-08-10 15:40 ` H. Peter Anvin
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=anmpv_7_YN2Fyj5J@google.com \
--to=senozhatsky@chromium.org \
--cc=david.laight.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
/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