From: Julian Sax <jsbc@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>, Julian Sax <jsbc@gmx.de>
Subject: Bisected regression: /proc/stat reports 0 steal time after commit x86/kvm: Move context tracking where it belongs
Date: Sun, 03 Jan 2021 22:20:25 +0100 [thread overview]
Message-ID: <87a6tp3eg6.fsf@chef> (raw)
Hello,
I know I am kind of late with this report, but I recently upgraded
from Kernel 5.8 to 5.10 and noticed that all my steal cpu time in htop
was gone, instead the time seems to be added to the sys counter. The
same thing happened in my own scripts, which source from /proc/stat.
After execution of "qemu-system-x86_64 -enable-kvm -m 1G" right after
bootup with no kvm used before this happens:
5.8, good
julian@chef:~$ cat /proc/stat | grep "cpu "
cpu 11235 3 7928 1309820 1360 0 64 0 508 0
# ^ steal
5.10, bad
julian@chef:~$ cat /proc/stat | grep "cpu "
cpu 420 0 1869 37801 746 0 7 0 0 0
# ^ steal
I did bisect the problem and ended up at
commit 87fa7f3e98a1310ef1ac1900e7ee7f9610a038bc
Author: Thomas Gleixner <tglx@linutronix.de>
Date: Wed Jul 8 21:51:54 2020 +0200
x86/kvm: Move context tracking where it belongs
This however does not revert at all on top of the current HEAD and I am
not familiar enough with the area to possibly guess what side effect
could have caused this.
This functionality was pretty nice, because it enabled me to see how the
guest was scheduling etc. It would be nice if that could be brought
back.
Or am I doing the wrong thing to begin with? But then again, htop
breaks in the same way.
Thanks!
Regards,
Julian
reply other threads:[~2021-01-03 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87a6tp3eg6.fsf@chef \
--to=jsbc@gmx.de \
--cc=alexandre.chartre@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).