From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42755] KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane
Date: Sun, 12 Feb 2012 10:40:56 GMT [thread overview]
Message-ID: <201202121040.q1CAeu2q022846@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42755-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42755
--- Comment #14 from Rosen <sandikata@yandex.ru> 2012-02-12 10:40:56 ---
(In reply to comment #13)
> (In reply to comment #12)
> > Allready mounted. Bu this directory doesn't exist, i have those dirs:
> >
> > /sys/kernel/debug
> > acpi bdi dri hid ieee80211 kvm mce suspend_stats usb virtio-ports
> > wakeup_sources x86
>
> Is this ancient kernel? Or have you disabled tracing during kernel compile? If
> later you will have to rebuild the kernel with tracing enabled. This is the
> only way to see what is happening.
Its my kernel not default ARCH kernel.
zgrep TRACE /proc/config.gz
CONFIG_STACKTRACE_SUPPORT=y
# CONFIG_RCU_TRACE is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_HAVE_ARCH_TRACEHOOK=y
# CONFIG_TRACE_SINK is not set
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
# CONFIG_FTRACE is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
i'm not sure which option need to be enabled?!
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-02-12 10:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 8:03 [Bug 42755] New: KVM is being extremely slow on AMD Athlon64 4000+ Dual Core 2.1GHz Brisbane bugzilla-daemon
2012-02-10 8:06 ` [Bug 42755] " bugzilla-daemon
2012-02-10 9:18 ` bugzilla-daemon
2012-02-10 9:36 ` bugzilla-daemon
2012-02-11 10:50 ` bugzilla-daemon
2012-02-12 8:27 ` bugzilla-daemon
2012-02-12 9:52 ` bugzilla-daemon
2012-02-12 10:10 ` bugzilla-daemon
2012-02-12 10:13 ` bugzilla-daemon
2012-02-12 10:16 ` bugzilla-daemon
2012-02-12 10:16 ` bugzilla-daemon
2012-02-12 10:18 ` bugzilla-daemon
2012-02-12 10:21 ` bugzilla-daemon
2012-02-12 10:30 ` bugzilla-daemon
2012-02-12 10:40 ` bugzilla-daemon [this message]
2012-02-12 10:41 ` bugzilla-daemon
2012-02-12 10:49 ` bugzilla-daemon
2012-02-12 14:49 ` bugzilla-daemon
2012-02-12 14:55 ` bugzilla-daemon
2012-02-12 15:09 ` bugzilla-daemon
2012-02-12 16:14 ` bugzilla-daemon
2012-02-13 8:53 ` bugzilla-daemon
2012-02-13 13:19 ` bugzilla-daemon
2012-02-13 13:30 ` bugzilla-daemon
2012-02-13 13:43 ` bugzilla-daemon
2012-02-13 14:14 ` bugzilla-daemon
2012-02-13 14:24 ` bugzilla-daemon
2012-02-13 14:37 ` bugzilla-daemon
2012-02-14 14:47 ` bugzilla-daemon
2012-02-15 7:49 ` bugzilla-daemon
2012-02-15 9:28 ` bugzilla-daemon
2012-02-21 8:55 ` bugzilla-daemon
2012-02-21 9:10 ` bugzilla-daemon
2012-02-21 11:53 ` bugzilla-daemon
2012-02-21 12:45 ` bugzilla-daemon
2012-02-26 9:53 ` 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=201202121040.q1CAeu2q022846@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.