public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luming Yu <luming.yu@gmail.com>
To: arnd@arndb.de, linux-kernel@vger.kernel.org
Cc: Luming Yu <luming.yu@gmail.com>, Luming Yu <luming.yu@intel.com>
Subject: [PATCH 02/13] HW-latency: Fix a lockdep warnning
Date: Sun,  4 Nov 2012 20:59:33 -0500	[thread overview]
Message-ID: <1352080784-30839-3-git-send-email-luming.yu@gmail.com> (raw)
In-Reply-To: <1352080784-30839-1-git-send-email-luming.yu@gmail.com>

[  150.733088] in_atomic(): 1, irqs_disabled(): 1, pid: 19, name: migration/2
[  150.735456] INFO: lockdep is turned off.
[  150.738903] irq event stamp: 28
[  150.741255] hardirqs last  enabled at (27): [<ffffffff816e6a80>] _raw_spin_unlock_irq+0x30/0x50
[  150.744884] hardirqs last disabled at (28): [<ffffffff816e616f>] _raw_spin_lock_irq+0x1f/0x90
[  150.748505] softirqs last  enabled at (24): [<ffffffff810724a7>] __do_softirq+0x167/0x3d0
[  150.752121] softirqs last disabled at (19): [<ffffffff816f143c>] call_softirq+0x1c/0x30
[  150.755709] Pid: 19, comm: migration/2 Tainted: G        W    3.7.0-rc2+ #2
[  150.759361] Call Trace:
[  150.762952]  [<ffffffff810d53e0>] ? print_irqtrace_events+0xd0/0xe0
[  150.766610]  [<ffffffff810a3b4c>] __might_sleep+0x18c/0x250
[  150.769140]  [<ffffffff816e2ab0>] mutex_lock_nested+0x40/0x390
[  150.772765]  [<ffffffff810d853d>] ? trace_hardirqs_on+0xd/0x10
[  150.776392]  [<ffffffff816e6a80>] ? _raw_spin_unlock_irq+0x30/0x50
[  150.778899]  [<ffffffff81021829>] ? read_tsc+0x9/0x20
[  150.782546]  [<ffffffffa05877e3>] get_freq_sample+0x33/0xd0 [hw_latency_test]
[  150.786249]  [<ffffffff810fac9b>] stop_machine_cpu_stop+0xab/0x110
[  150.789964]  [<ffffffff810fadd6>] cpu_stopper_thread+0xd6/0x1b0
[  150.792528]  [<ffffffff810fabf0>] ? cpu_stop_queue_work+0x80/0x80
[  150.795044]  [<ffffffff8115798e>] ? perf_event_alloc+0x5e/0x4a0
[  150.797572]  [<ffffffff816e4672>] ? __schedule+0x442/0xa00
[  150.800079]  [<ffffffff810fad00>] ? stop_machine_cpu_stop+0x110/0x110
[  150.802512]  [<ffffffff810938fd>] kthread+0xed/0x100
[  150.805825]  [<ffffffff81093810>] ? flush_kthread_worker+0x190/0x190
[  150.808051]  [<ffffffff816f00ec>] ret_from_fork+0x7c/0xb0
[  150.810161]  [<ffffffff81093810>] ? flush_kthread_worker+0x190/0x190

Signed-off-by: Luming Yu <luming.yu@intel.com>
---
 drivers/misc/hw_latency_test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/misc/hw_latency_test.c b/drivers/misc/hw_latency_test.c
index 2aa3a74..e970642 100644
--- a/drivers/misc/hw_latency_test.c
+++ b/drivers/misc/hw_latency_test.c
@@ -149,7 +149,7 @@ static int get_random_bytes_sample(void *unused)
 	u64	sample = 0;
 	int	ret = 1;
 
-	buffer = kzalloc(1024, GFP_KERNEL);
+	buffer = kzalloc(1024, GFP_ATOMIC);
 
 	start = ktime_get();
 	do {
-- 
1.7.12.1


  parent reply	other threads:[~2012-11-04 13:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05  1:59 [PATCH 00/13] A simple hardware detector for latency as well as throughtput ver 0.10 Luming Yu
2012-11-05  1:59 ` [PATCH 01/13] HW-latency: hardware latency test 0.10 Luming Yu
2012-11-04 21:07   ` Maarten Lankhorst
2012-11-05 12:14     ` Luming Yu
2012-11-04 21:23   ` John Kacur
2012-11-05 12:20     ` Luming Yu
2012-11-05  8:44   ` No recipient
2012-11-05  8:44   ` Ove Karlsen
2012-11-05  1:59 ` Luming Yu [this message]
2012-11-05  1:59 ` [PATCH 03/13] HW-latency: Use get_random_bytes_arch Luming Yu
2012-11-05  1:59 ` [PATCH 04/13] HW-latency: Differentiate three modes to use CPU carry out testing Luming Yu
2012-11-05  1:59 ` [PATCH 05/13] HW-latency: Add CPU field in sample output Luming Yu
2012-11-05  1:59 ` [PATCH 06/13] HW-latency: cycle through all online cpus to re-test cpufreq Luming Yu
2012-11-05  1:59 ` [PATCH 07/13] HW-latency: delete too many "Fast TSC calibration using PIT" in cpufreq sampling Luming Yu
2012-11-05  1:59 ` [PATCH 08/13] HW-latency: A stupid memory scanner for raw memory latency test Luming Yu
2012-11-05  1:59 ` [PATCH 09/13] HW-latency: Fix unwanted crash caused by write to dummy debugfs interface Luming Yu
2012-11-05  1:59 ` [PATCH 10/13] HW-latency: add address range for x86-32 Luming Yu
2012-11-05  1:59 ` [PATCH 11/13] HW-latency: fix a warnning in previous patch Luming Yu
2012-11-05  1:59 ` [PATCH 12/13] HW-latency: Add sample unit in sample data Luming Yu
2012-11-05  1:59 ` [PATCH 13/13] HW-latency: some sample data format change Luming Yu
2012-11-08 16:04 ` [PATCH 00/13] A simple hardware detector for latency as well as throughtput ver 0.10 Theodore Ts'o

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=1352080784-30839-3-git-send-email-luming.yu@gmail.com \
    --to=luming.yu@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@intel.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