Re: [PATCH] kernel/watchdog.c: Do not hardcode CPU 0 as the initial thread

2017-01-05 Thread Don Zickus
(cc'ing Andrew) On Tue, Jan 03, 2017 at 04:19:50PM -0500, Prarit Bhargava wrote: > > > On 12/01/2016 03:06 PM, Don Zickus wrote: > > On Tue, Nov 29, 2016 at 08:15:21AM -0500, Prarit Bhargava wrote: > >> When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the > >> boot cpu can be

Re: [PATCH] kernel/watchdog.c: Do not hardcode CPU 0 as the initial thread

2017-01-03 Thread Prarit Bhargava
On 12/01/2016 03:06 PM, Don Zickus wrote: > On Tue, Nov 29, 2016 at 08:15:21AM -0500, Prarit Bhargava wrote: >> When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the >> boot cpu can be replaced. During the hot add event, the message >> >> NMI watchdog: enabled on all CPUs, per

Re: [PATCH] kernel/watchdog.c: Do not hardcode CPU 0 as the initial thread

2016-12-01 Thread Don Zickus
On Tue, Nov 29, 2016 at 08:15:21AM -0500, Prarit Bhargava wrote: > When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the > boot cpu can be replaced. During the hot add event, the message > > NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. > > is out

Re: [PATCH] kernel/watchdog.c: Do not hardcode CPU 0 as the initial thread

2016-11-29 Thread Don Zickus
On Tue, Nov 29, 2016 at 08:15:21AM -0500, Prarit Bhargava wrote: > When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the > boot cpu can be replaced. During the hot add event, the message > > NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. > > is out

[PATCH] kernel/watchdog.c: Do not hardcode CPU 0 as the initial thread

2016-11-29 Thread Prarit Bhargava
When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the boot cpu can be replaced. During the hot add event, the message NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. is output implying that the NMI watchdog was disabled at some point. This is not t