public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [GIT PULL] scheduler changes for v4.3
Date: Tue, 1 Sep 2015 10:44:44 +0200	[thread overview]
Message-ID: <20150901084444.GB421@x4> (raw)
In-Reply-To: <20150901083856.GD25398@gmail.com>

On 2015.09.01 at 10:38 +0200, Ingo Molnar wrote:
> 
> * Markus Trippelsdorf <markus@trippelsdorf.de> wrote:
> 
> > Well, git show a1d8561172f369ba56d636df49a6b4d6d77e2123 :
> > 
> > commit a1d8561172f369ba56d636df49a6b4d6d77e2123
> > Merge: 3959df1dfb95 ff277d4250fe
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date:   Mon Aug 31 20:26:22 2015 -0700
> 
> > diff --cc kernel/cpu.c
> > index 3c91a3fdfce5,664ce5299334..82cf9dff4295
> > --- a/kernel/cpu.c
> > +++ b/kernel/cpu.c
> > @@@ -394,15 -392,10 +394,15 @@@ static int _cpu_down(unsigned int cpu, 
> >   	smpboot_park_threads(cpu);
> >   
> >   	/*
> >  -	 * So now all preempt/rcu users must observe !cpu_active().
> >  +	 * Prevent irq alloc/free while the dying cpu reorganizes the
> >  +	 * interrupt affinities.
> >   	 */
> >  +	irq_lock_sparse();
> >   
> >  +	/*
> >  +	 * So now all preempt/rcu users must observe !cpu_active().
> >  +	 */
> > - 	err = __stop_machine(take_cpu_down, &tcd_param, cpumask_of(cpu));
> > + 	err = stop_machine(take_cpu_down, &tcd_param, cpumask_of(cpu));
> >   	if (err) {
> >   		/* CPU didn't die: tell everyone.  Can't complain. */
> >   		cpu_notify_nofail(CPU_DOWN_FAILED | mod, hcpu);
> 
> So the irq_lock_sparse() change is from a commit that got merged in the last merge 
> window, which is part of v4.2:
> 
>   ce0d3c0a6fb1 ("genirq: Revert sparse irq locking around __cpu_up() and move it to x86 for now")
> 
> Could you please post the patch against Linus's latest that you have tested on 
> your system to make it boot fine?
> 
> The one you posted cannot possibly build, because access to __stop_machine() is 
> gone from cpu.c:

As I wrote in my other reply. The boot failure is nondeterministic (boot
succeeds roughly every sixth time). So the bisection and the patch is
just bogus (,but the boot failure is real).

Sorry.

-- 
Markus

  reply	other threads:[~2015-09-01  8:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 17:24 [GIT PULL] scheduler changes for v4.3 Ingo Molnar
2015-09-01  7:08 ` Markus Trippelsdorf
2015-09-01  7:27   ` Ingo Molnar
2015-09-01  7:44     ` Markus Trippelsdorf
2015-09-01  8:38       ` Ingo Molnar
2015-09-01  8:44         ` Markus Trippelsdorf [this message]
2015-09-01  8:56           ` Ingo Molnar
2015-09-01 10:04             ` commit 3c2e7f7de3 (KVM use NPT page attributes) causes boot failures Markus Trippelsdorf
2015-09-01 13:00               ` Xiao Guangrong
2015-09-01 13:56                 ` Markus Trippelsdorf
2015-09-01 22:31                   ` Xiao Guangrong
2015-09-02  3:50                     ` Markus Trippelsdorf
2015-09-02  9:17                       ` Xiao Guangrong
2015-09-02  9:38                         ` Markus Trippelsdorf
2015-09-02 10:27                           ` Xiao Guangrong
2015-09-02 10:54                             ` Markus Trippelsdorf
2015-09-02 10:57                               ` Xiao Guangrong
2015-09-01  8:50         ` [GIT PULL] scheduler changes for v4.3 Markus Trippelsdorf
2015-09-01  8:18     ` Markus Trippelsdorf
2015-09-01  8:39       ` Markus Trippelsdorf

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=20150901084444.GB421@x4 \
    --to=markus@trippelsdorf.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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