public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: John Keller <jpk@sgi.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, steiner@sgi.com
Subject: Re: [PATCH] - x86_64-add-ioapic-nmi-support-fix-3
Date: Sat, 30 Jun 2007 07:44:40 -0700	[thread overview]
Message-ID: <46866C58.2090705@oracle.com> (raw)
In-Reply-To: <200706301429.l5UETMXk295940@fcbayern.americas.sgi.com>

John Keller wrote:
>> [adding Andi Kleen]
>>
>> John Keller wrote:
>>> Place all the IOACPI NMI support code under CONFIG_ACPI
>>> to clear up build errors with certain configs.
>>>
>>> Signed-off-by: John Keller <jpk@sgi.com>
>>> ---
>> Is there some architectural reason that IO APIC NMI support should
>> require ACPI?
> 
> OK, I guess standing alone this description was a bit misleading.
> The code referred to here is the new code supporting the ACPI NMI SRC
> structure that can be specified in the MADT. Without ACPI support this
> code is not relevant. All the code touched by this patch was introduced
> by eariler versions of this patchset.
> 
> This patch makes no changes to the workings of nmi_watchdog.

OK, thanks for the clarification.

> John
> 
> 
>> Is this a new requirement?  It seems like a step backwards to me.
>>
>>
>> Documentation/nmi_watchdog.txt doesn't say anything about ACPI being
>> needed.  It does say:
>>
>> "For x86-64, the needed APIC is always compiled in, and the NMI watchdog is
>> always enabled with I/O-APIC mode (nmi_watchdog=1). Currently, local APIC
>> mode (nmi_watchdog=2) does not work on x86-64.
>>
>> Using local APIC (nmi_watchdog=2) needs the first performance register, so
>> you can't use it for other purposes (such as high precision performance
>> profiling.) However, at least oprofile and the perfctr driver disable the
>> local APIC NMI watchdog automatically."


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2007-06-30 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 22:05 [PATCH] - x86_64-add-ioapic-nmi-support-fix-3 John Keller
2007-06-29 23:12 ` Randy Dunlap
2007-06-30 14:29   ` John Keller
2007-06-30 14:44     ` Randy Dunlap [this message]

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=46866C58.2090705@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jpk@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steiner@sgi.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