From: Avi Kivity <avi@redhat.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 36222] kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown
Date: Mon, 30 May 2011 12:55:31 +0300 [thread overview]
Message-ID: <4DE36993.80602@redhat.com> (raw)
In-Reply-To: <201105300920.p4U9K71F020162@demeter1.kernel.org>
On 05/30/2011 12:20 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=36222
>
>
>
>
>
> --- Comment #3 from Török Edwin<edwintorok@gmail.com> 2011-05-30 09:20:06 ---
> Created an attachment (id=60042)
> --> (https://bugzilla.kernel.org/attachment.cgi?id=60042)
> trace-cmd record -e kvm; ^C; trace-cmd report
>
> (In reply to comment #1)
> > Please also post
> >
> > - kvm_stat output
> > - trace-cmd record -e kvm; trace-cmd report
>
> Doesn't seem to be part of mainline, are you refering to this trace-cmd?
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
>
Yes. Install udis86 and udis86-devel before building it, please.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-30 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 8:40 [Bug 36222] New: kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown bugzilla-daemon
2011-05-30 8:48 ` [Bug 36222] " bugzilla-daemon
2011-05-30 9:18 ` bugzilla-daemon
2011-05-30 9:20 ` bugzilla-daemon
2011-05-30 9:55 ` Avi Kivity [this message]
2011-05-30 9:26 ` bugzilla-daemon
2011-05-30 10:31 ` bugzilla-daemon
2011-05-30 10:55 ` bugzilla-daemon
2011-05-30 10:58 ` bugzilla-daemon
2011-05-30 11:01 ` bugzilla-daemon
2011-05-30 11:09 ` bugzilla-daemon
2011-05-30 11:38 ` bugzilla-daemon
2011-05-30 11:43 ` bugzilla-daemon
2011-05-30 12:26 ` bugzilla-daemon
2011-06-06 10:57 ` bugzilla-daemon
2012-06-13 15:07 ` bugzilla-daemon
2012-06-13 15:07 ` 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=4DE36993.80602@redhat.com \
--to=avi@redhat.com \
--cc=bugzilla-daemon@bugzilla.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