From: Sean Christopherson <seanjc@google.com>
To: "Y.G Kumar" <ygkumar17@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Cpu steal
Date: Tue, 28 May 2024 10:45:17 -0700 [thread overview]
Message-ID: <ZlYYLRW_3Hv36So3@google.com> (raw)
In-Reply-To: <CAD4ZjH0oAfUDfbipQk2YHXwV3zKdNyGwpCyybA=y8_6g3LON0g@mail.gmail.com>
On Thu, May 23, 2024, Y.G Kumar wrote:
> Hi,
>
> Is there a way of measuring cpu steal time of a guest from the
> hypervisor ? Does it give accurate information ? What are some of the
> effective ways to find out the steal time from outside the vm
Yes and no. KVM's PV steal time information isn't exposed anywhere, but only
because it's simply a reflection of the task's run_delay that's reported in
/proc/PID/schedstat (second column).
I assume there are tools that translate schedstat into human-readable information,
and/or do analysis on the info, but I don't have personal experience with any such
tools. If you need more help, I recommend pinging sched folks, as this is really
a scheduler question, not a KVM question.
next prev parent reply other threads:[~2024-05-28 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 14:47 Cpu steal Y.G Kumar
2024-05-28 17:45 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-23 11:02 Y.G Kumar
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=ZlYYLRW_3Hv36So3@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=ygkumar17@gmail.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