From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 218792] Guest call trace with mwait enabled
Date: Fri, 8 Aug 2025 15:59:28 -0700 [thread overview]
Message-ID: <aJaBUEjIFai02SxP@google.com> (raw)
In-Reply-To: <bug-218792-28872-bVH0MHGv7j@https.bugzilla.kernel.org/>
On Fri, Aug 08, 2025, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218792
>
> Len Brown (lenb@kernel.org) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |lenb@kernel.org
>
> --- Comment #6 from Len Brown (lenb@kernel.org) ---
> Re: intel_idle
>
> I agree that the SDM doesn't guarantee this MSR exists
> based on the presence of PC10.
>
> I'm not opposed to _safe().
>
> but...
>
> Why is this "platform" advertising PC10 (or any MWAIT C-states) to intel_idle
> in the first place?
Because letting the guest execute MONITOR/MWAIT natively, and thus get into deeper
sleep states, is advantageous for all the same reasons bare metal CPUs want to
get into deep sleep states, e.g. to let active cores hit higher turbo bins.
next prev parent reply other threads:[~2025-08-08 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 7:32 [Bug 218792] New: Guest call trace with mwait enabled bugzilla-daemon
2024-04-30 11:32 ` [Bug 218792] " bugzilla-daemon
2024-04-30 16:41 ` [Bug 218792] New: " Sean Christopherson
2025-07-31 8:59 ` Chenyi Qiang
2024-04-30 16:42 ` [Bug 218792] " bugzilla-daemon
2024-07-12 8:11 ` bugzilla-daemon
2024-07-12 8:40 ` bugzilla-daemon
2025-07-31 8:59 ` bugzilla-daemon
2025-08-08 21:05 ` bugzilla-daemon
2025-08-08 22:59 ` Sean Christopherson [this message]
2025-08-08 22:59 ` 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=aJaBUEjIFai02SxP@google.com \
--to=seanjc@google.com \
--cc=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