All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org,
	Dipankar Sarma <dipankar@in.ibm.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [Bisected] qemu hangs on current git
Date: Wed, 22 Jan 2014 11:24:35 +0100	[thread overview]
Message-ID: <20140122102435.GH31570@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140122093755.GA388@x4>

On Wed, Jan 22, 2014 at 10:37:55AM +0100, Markus Trippelsdorf wrote:
> git bisect points to:
> 
> commit 8cb75e0c4ec9786b81439761eac1d18d4a931af3
> Author: Peter Zijlstra <peterz@infradead.org>
> Date:   Wed Nov 20 12:22:37 2013 +0100
> 
>     sched/preempt: Fix up missed PREEMPT_NEED_RESCHED folding
> 

No idea why kvm would go funny on that, real hardware runs fine.

You're running a !PREEMPT kernel, right? Does the below make any
difference?

---
 include/linux/preempt.h | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/include/linux/preempt.h b/include/linux/preempt.h
index 59749fc48328..de83b4eb1642 100644
--- a/include/linux/preempt.h
+++ b/include/linux/preempt.h
@@ -134,7 +134,6 @@ do { \
 #undef preempt_check_resched
 #endif
 
-#ifdef CONFIG_PREEMPT
 #define preempt_set_need_resched() \
 do { \
 	set_preempt_need_resched(); \
@@ -144,10 +143,6 @@ do { \
 	if (tif_need_resched()) \
 		set_preempt_need_resched(); \
 } while (0)
-#else
-#define preempt_set_need_resched() do { } while (0)
-#define preempt_fold_need_resched() do { } while (0)
-#endif
 
 #ifdef CONFIG_PREEMPT_NOTIFIERS
 

  reply	other threads:[~2014-01-22 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 21:51 qemu hangs on current git Markus Trippelsdorf
2014-01-22  8:50 ` Markus Trippelsdorf
2014-01-22  9:37   ` [Bisected] " Markus Trippelsdorf
2014-01-22 10:24     ` Peter Zijlstra [this message]
2014-01-22 11:44       ` Markus Trippelsdorf
2014-01-22 11:54         ` Peter Zijlstra
2014-01-23 16:46       ` [tip:sched/urgent] sched/preempt/x86: Fix voluntary preempt for x86 tip-bot for Peter Zijlstra

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=20140122102435.GH31570@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 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.