From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Aristeu Rozanski <aris@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/2] NMI watchdog: add support to enable and disable IOAPIC NMI
Date: Wed, 29 Oct 2008 19:47:06 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0810291941510.13373@ftp.linux-mips.org> (raw)
In-Reply-To: <20081029090532.cc9536d9.randy.dunlap@oracle.com>
On Wed, 29 Oct 2008, Randy Dunlap wrote:
> > This patch adds support to enable/disable IOAPIC NMI watchdog in runtime via
> > procfs.
>
> Some info on how to use this, what to write(?) to what file(?) in procfs
> would be Very Good to have.
I gather this is an extension to the existing interface already covering
the local APIC NMI watchdog, which surely ;) must have been documented at
the time it was added. If it wasn't, then we cannot require it now as a
prerequisite to accept this patch, although such documentation would be
desirable as a separate submission.
Maciej
next prev parent reply other threads:[~2008-10-29 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:42 [PATCH 0/2] IOAPIC NMI watchdog fixes Aristeu Rozanski
2008-10-27 16:42 ` [PATCH 1/2] NMI watchdog: add support to enable and disable IOAPIC NMI Aristeu Rozanski
2008-10-29 16:05 ` Randy Dunlap
2008-10-29 19:47 ` Maciej W. Rozycki [this message]
2008-10-29 20:39 ` Aristeu Rozanski
2008-10-30 0:50 ` Randy Dunlap
2008-10-27 16:42 ` [PATCH 2/2] NMI watchdog: disable NMIs on LVT0 in case NMI watchdog is not working Aristeu Rozanski
2008-10-27 16:58 ` [PATCH 0/2] IOAPIC NMI watchdog fixes Maciej W. Rozycki
2008-10-27 17:45 ` Ingo Molnar
2008-12-15 11:23 ` Aristeu Rozanski
2008-12-16 15:04 ` Maciej W. Rozycki
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=alpine.LFD.1.10.0810291941510.13373@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=aris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
/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®