[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <661586056.6758573.1429976563176.JavaMail.zimbra@redhat.com>
Date: Sat, 25 Apr 2015 11:42:43 -0400 (EDT)
From: Ulrich Obergfell <uobergfe@...hat.com>
To: Don Zickus <dzickus@...hat.com>
Cc: Chris Metcalf <cmetcalf@...hip.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrew Jones <drjones@...hat.com>,
chai wen <chaiw.fnst@...fujitsu.com>,
Fabian Frederick <fabf@...net.be>,
Aaron Tomlin <atomlin@...hat.com>,
Ben Zhang <benzh@...omium.org>,
Christoph Lameter <cl@...ux.com>,
Gilad Ben-Yossef <gilad@...yossef.com>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
linux-doc@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v9 2/3] watchdog: add watchdog_cpumask sysctl to assist
nohz
----- Original Message -----
From: "Don Zickus" <dzickus@...hat.com>
[...]
> On Tue, Apr 21, 2015 at 10:07:00AM -0400, Ulrich Obergfell wrote:
>>
>> Chris,
>>
[...]
>> I think the user should only be allowed to specify a mask that is a subset of
>> tick_nohz_full_mask as only those CPUs don't have a watchdog thread by default.
>> In other words, the user should not be able to interfere with housekeeping CPUs.
>
> Hi Uli,
>
> I am not sure that is necessary. This was supposed to be a debugging
> interface for nohz (and possibly other technologies). I think restricting
> it to just tick_nohz makes it difficult to try out new things or debug
> certain problems.
>
> Personally, I feel anyone who will use this sys interface will need to do so
> at their own risk.
>
>
> Cheers,
> Don
Don, o.k. - I understand.
Chris, please ignore my idea to add a plausibility check.
Regards,
Uli
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists