mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Bahi" <dbahi@novell.com>
To: <ak@suse.de>
Cc: <mingo@elte.hu>, <arjan@infradead.org>, <tglx@linutronix.de>,
	<akpm@linux-foundation.org>,
	"Gregory Haskins" <GHaskins@novell.com>,
	<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: nmi_watchdog fix for x86_64 to be more like i386
Date: Fri, 05 Oct 2007 10:01:12 -0600	[thread overview]
Message-ID: <47060B680200006C00019B7B@sinclair.provo.novell.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

On Mon, 2007-10-01 at 23:41 +0200, Andi Kleen wrote:
> > IRQ_NOBALANCING is not preventing cpu unplug. It moves the affinity to the
> > next CPU, but the check in NMI watchdog for CPU == 0 would not longer
> > work.
> 
> That cannot happen right now because cpu_disable() on both i386/x86-64
> reject CPU #0. So just setting IRQ_NOBALANCING is sufficient and both
> do that already. I was wrong earlier in being concerned about this.
> 
> >  int tick_do_broadcast(cpumask_t mask)
> > @@ -137,6 +147,7 @@ int tick_do_broadcast(cpumask_t mask)
> >  		cpu_clear(cpu, mask);
> >  		td = &per_cpu(tick_cpu_device, cpu);
> >  		td->evtdev->event_handler(td->evtdev);
> > +		tick_broadcast_account(cpu);
> 
> That would not handle the case with a single CPU running only
> irq  0 but not broadcasting I think.
> 
> I believe ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/fix-watchdog
> is the correct fix
> 
> -Andi

Andi, 

If it's agreed that this is the fix - can you submit a proper [PATCH] so
all users of watchdog_use_timer_and_hpet_on_x86_64.patch can be removed,
and replaced with yours.

Thank you very much



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

             reply	other threads:[~2007-10-05 16:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 16:01 David Bahi [this message]
2007-10-05 16:03 ` Andi Kleen
2007-10-05 17:38   ` Peter W. Morreale
2007-10-05 18:00     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2007-09-26 18:03 David Bahi
2007-10-01 17:36 ` Andi Kleen
2007-10-01 18:54   ` Thomas Gleixner
2007-10-01 19:16     ` Andi Kleen
2007-10-01 19:27       ` Thomas Gleixner
2007-10-01 19:56         ` Arjan van de Ven
2007-10-01 20:10           ` Dave Jones
2007-10-01 20:11           ` Paul E. McKenney
2007-10-01 21:17           ` Thomas Gleixner
2007-10-01 21:41             ` Andi Kleen
2007-10-01 21:58               ` Thomas Gleixner
2007-10-01 22:07                 ` Andi Kleen
2007-10-01 22:47                   ` Thomas Gleixner
2007-10-01 22:52                     ` Arjan van de Ven
2007-10-02  4:56                     ` Mika Penttilä
2007-10-02  5:00                       ` Arjan van de Ven
2007-10-02  5:51                     ` Andi Kleen
2007-10-02  6:18                       ` Thomas Gleixner
2007-10-05  4:37                         ` Pallipadi, Venkatesh
2007-10-05 20:37                           ` Thomas Gleixner

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=47060B680200006C00019B7B@sinclair.provo.novell.com \
    --to=dbahi@novell.com \
    --cc=GHaskins@novell.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome