From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220019] Host call trace and crash after boot guest with perf kvm stat record
Date: Thu, 17 Apr 2025 03:15:05 +0000 [thread overview]
Message-ID: <bug-220019-28872-ULANU6Xwlx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220019-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220019
--- Comment #3 from Chen, Fan (farrah.chen@intel.com) ---
And we found the fix patch has been posted already
https://lore.kernel.org/lkml/20250415131446.GN5600@noisy.programming.kicks-ass.net/,
verified this patch, it fixed the issue indeed.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-04-17 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 8:49 [Bug 220019] New: Host call trace and crash after boot guest with perf kvm stat record bugzilla-daemon
2025-04-16 14:30 ` [Bug 220019] " bugzilla-daemon
2025-04-17 3:13 ` bugzilla-daemon
2025-04-17 3:15 ` bugzilla-daemon [this message]
2025-11-03 9:21 ` bugzilla-daemon
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=bug-220019-28872-ULANU6Xwlx@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).