From: Andrew Morton <akpm@osdl.org>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nmi_watchdog=2 and P4-HT
Date: Wed, 3 Mar 2004 21:30:33 -0800 [thread overview]
Message-ID: <20040303213033.6348a08b.akpm@osdl.org> (raw)
In-Reply-To: <20040304054215.GA683@zaniah>
Philippe Elie <phil.el@wanadoo.fr> wrote:
>
> Hi,
>
> Actually with nmi_watchdog=2 and a P4 ht box the nmi is reflected
> only on logical processor 0, it's better to get it on both.
What do you mean by "reflected"? That the NMi is delivered to both
siblings but only appears in /proc/interrupts as being delivered to the
zeroeth?
> Note, if you test this patch, than on all x86 SMP and nmi_watchdog=2
> nmi occurs at 1000 hz (if the cpu is loaded) not at the intended 1 hz
> rate but that's a distinct problem.
nmi_watchdog=2 is local apic, and nmi_watchdog=1 is I/O apic, is that
correct?
I am showing the current behaviour:
nmi_watchdog=1: 1000 NMI/second, accounted to both siblings
nmi_watchdog=2: one NMI/second, accounted to sibling 0 only.
with your patch:
nmi_watchdog=1: 1000 NMI/second, accounted to both siblings
nmi_watchdog=2: 1000 NMI/second, accounted to both siblings
All of these are wrong, aren't they? We'd like to see one NMI per second,
on all siblings. I gues that's not possible for the IO APIC?
>From the above it appears that you have a solution planned for the local
APIC at least, yes?
next prev parent reply other threads:[~2004-03-04 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 5:42 Philippe Elie
2004-03-04 5:30 ` Andrew Morton [this message]
2004-03-04 7:26 ` Philippe Elie
2004-03-04 6:32 ` Andrew Morton
2004-03-04 8:20 ` Philippe Elie
2004-03-05 5:42 ` [PATCH] set nmi_hz to 1 with nmi_watchdog=2 and SMP Philippe Elie
2004-03-04 8:04 ` [PATCH] nmi_watchdog=2 and P4-HT Philippe Elie
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=20040303213033.6348a08b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
/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®