mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Don Zickus <dzickus@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Norbert Warmuth <nwarmuth@t-online.de>,
	Joseph Salisbury <joseph.salisbury@canonical.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RESEND][PATCH v3] watchdog: Fix disable/enable regression
Date: Wed, 19 Dec 2012 22:44:44 +0100	[thread overview]
Message-ID: <87zk1967jn.fsf@nemi.mork.no> (raw)
In-Reply-To: <874njh7nd5.fsf@nemi.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork"'s message of "Wed, 19 Dec 2012 22:17:42 +0100")

Bjørn Mork <bjorn@mork.no> writes:
> Don Zickus <dzickus@redhat.com> writes:
>
>> What about the opposite cases?  
>> nmi_watchdog=1
>> echo 1 > /sys/devices/system/cpu/cpu1/online
>
> I don't see why not. But verifying it would be nice.  I thought that it
> would be a simple thing to test using qemu-kvm, but it seems that the
> CPU hotplugging support there isn't quite ready. The guest just dies
> with "Assertion `bus->allow_hotplug' failed."
>
> I'll go digging for alternatives, but if anyone else could verify this
> then I'd appreciate it.

I just realized that you might not really want/need hotplugging, but
just booting with some cores initially offline?

That's easier to test at least:

qmitest:~# cat /proc/cmdline 
initrd=/initrd.img.test root=/dev/sda1 ro console=tty0 console=ttyS0,9600n8 maxcpus=1 BOOT_IMAGE=/vmlinuz.test 
qmitest:~#  grep . /sys/devices/system/cpu/o*line
/sys/devices/system/cpu/offline:1-3
/sys/devices/system/cpu/online:0
qmitest:~# grep . /sys/devices/system/cpu/cpu?/online 
/sys/devices/system/cpu/cpu1/online:0
/sys/devices/system/cpu/cpu2/online:0
/sys/devices/system/cpu/cpu3/online:0
qmitest:~# grep . /sys/devices/system/cpu/o*line
/sys/devices/system/cpu/offline:1-3
/sys/devices/system/cpu/online:0
qmitest:~# grep . /proc/sys/kernel/nmi_watchdog 
1


qmitest:~#  echo 1 > /sys/devices/system/cpu/cpu1/online
qmitest:~#  echo 1 > /sys/devices/system/cpu/cpu2/online
qmitest:~# grep . /sys/devices/system/cpu/cpu?/online 
/sys/devices/system/cpu/cpu1/online:1
/sys/devices/system/cpu/cpu2/online:1
/sys/devices/system/cpu/cpu3/online:0


No problem observed.  As expected.



Bjørn

  reply	other threads:[~2012-12-19 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14  9:33 Bisected oops regression between v3.7-rc8 and v3.7: nmi_watchdog Bjørn Mork
2012-12-14  9:34 ` [PATCH] Revert "watchdog: Fix CPU hotplug regression" Bjørn Mork
2012-12-14 13:44 ` [PATCH v2] watchdog: Fix disable/enable regression Bjørn Mork
2012-12-16 19:41 ` Bisected oops regression between v3.7-rc8 and v3.7: nmi_watchdog Maciej Rutecki
2012-12-18  8:13 ` [regression][PATCH v3] watchdog: Fix disable/enable regression Bjørn Mork
2012-12-19 19:51 ` [RESEND][PATCH " Bjørn Mork
2012-12-19 20:13   ` Don Zickus
2012-12-19 21:17     ` Bjørn Mork
2012-12-19 21:44       ` Bjørn Mork [this message]
2012-12-20 19:17         ` Don Zickus

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=87zk1967jn.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nwarmuth@t-online.de \
    --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

all inboxes | Powered by JetHome®