public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 36222] kvm: 100% CPU usage after 3.0.0-rc1 guest shutdown
Date: Mon, 30 May 2011 12:26:20 GMT	[thread overview]
Message-ID: <201105301226.p4UCQKgV020940@demeter2.kernel.org> (raw)
In-Reply-To: <bug-36222-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=36222





--- Comment #12 from Török Edwin <edwintorok@gmail.com>  2011-05-30 12:26:19 ---
Bisection tells me this is the offending commit (see below), but I see you
found it too.

commit 349c004e3d31fda23ad225b61861be38047fff16
Author: Christoph Lameter <cl@linux.com>
Date:   Sat Mar 12 12:50:10 2011 +0100

    x86: A fast way to check capabilities of the current cpu

    Add this_cpu_has() which determines if the current cpu has a certain
    ability using a segment prefix and a bit test operation.

    For that we need to add bit operations to x86s percpu.h.

    Many uses of cpu_has use a pointer passed to a function to determine
    the current flags. That is no longer necessary after this patch.

    However, this patch only converts the straightforward cases where
    cpu_has is used with this_cpu_ptr. The rest is work for later.

    -tj: Rolled up patch to add x86_ prefix and use percpu_read() instead
         of percpu_read_stable().

    Signed-off-by: Christoph Lameter <cl@linux.com>
    Acked-by: Tejun Heo <tj@kernel.org>
    Signed-off-by: Tejun Heo <tj@kernel.org>

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2011-05-30 12:26 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
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 [this message]
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=201105301226.p4UCQKgV020940@demeter2.kernel.org \
    --to=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