From: Alexander Nyberg <alexn@telia.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] adjust x86-64 watchdog tick calculation
Date: Thu, 12 May 2005 12:00:08 +0200 [thread overview]
Message-ID: <1115892008.918.7.camel@localhost.localdomain> (raw)
In-Reply-To: <s2832159.057@emea1-mh.id2.novell.com>
tor 2005-05-12 klockan 10:27 +0200 skrev Jan Beulich:
> (Note: Patch also attached because the inline version is certain to get
> line wrapped.)
>
> Get the x86-64 watchdog tick calculation into a state where it can also
> be used with nmi_hz other than 1Hz. Also do not turn on the watchdog by
> default (as is already done on i386).
>
Why shouldn't the watchdog be turned on by default? It's an extremely
useful debugging aid and it's not like it fires NMIs often (the nmi_hz
is far from reality).
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
> diff -Npru linux-2.6.12-rc4.base/arch/x86_64/kernel/nmi.c linux-2.6.12-rc4/arch/x86_64/kernel/nmi.c
> --- linux-2.6.12-rc4.base/arch/x86_64/kernel/nmi.c 2005-05-11 17:27:54.848855552 +0200
> +++ linux-2.6.12-rc4/arch/x86_64/kernel/nmi.c 2005-05-11 17:50:36.257889920 +0200
> @@ -57,7 +57,7 @@ static unsigned int lapic_nmi_owner;
> int nmi_active; /* oprofile uses this */
> int panic_on_timeout;
>
> -unsigned int nmi_watchdog = NMI_DEFAULT;
> +unsigned int nmi_watchdog = NMI_NONE;
> static unsigned int nmi_hz = HZ;
> unsigned int nmi_perfctr_msr; /* the MSR to reset in NMI handler */
>
> @@ -325,7 +325,7 @@ static void setup_k7_watchdog(void)
> | K7_NMI_EVENT;
>
> wrmsr(MSR_K7_EVNTSEL0, evntsel, 0);
> - wrmsrl(MSR_K7_PERFCTR0, -((u64)cpu_khz*1000) / nmi_hz);
> + wrmsrl(MSR_K7_PERFCTR0, -((u64)cpu_khz * 1000 / nmi_hz));
> apic_write(APIC_LVTPC, APIC_DM_NMI);
> evntsel |= K7_EVNTSEL_ENABLE;
> wrmsr(MSR_K7_EVNTSEL0, evntsel, 0);
> @@ -404,7 +404,7 @@ void nmi_watchdog_tick (struct pt_regs *
> alert_counter[cpu] = 0;
> }
> if (nmi_perfctr_msr)
> - wrmsr(nmi_perfctr_msr, -(cpu_khz/nmi_hz*1000), -1);
> + wrmsrl(nmi_perfctr_msr, -((u64)cpu_khz * 1000 / nmi_hz));
> }
>
> static int dummy_nmi_callback(struct pt_regs * regs, int cpu)
>
>
next prev parent reply other threads:[~2005-05-12 10:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 8:27 [PATCH] adjust x86-64 watchdog tick calculation Jan Beulich
2005-05-12 10:00 ` Alexander Nyberg [this message]
2005-05-12 11:46 ` [discuss] " Andi Kleen
2005-05-12 14:29 ` Pavel Machek
2005-05-13 11:30 ` Andi Kleen
2005-05-13 19:52 ` Pavel Machek
2005-05-13 21:27 ` Lee Revell
2005-05-13 22:51 ` Pavel Machek
2005-05-13 22:56 ` Lee Revell
2005-05-13 23:21 ` Pavel Machek
2005-05-13 23:29 ` Dave Jones
2005-05-15 10:52 ` Andi Kleen
2005-05-15 10:36 ` Andi Kleen
2005-05-15 10:51 ` Pavel Machek
2005-05-15 10:54 ` Andi Kleen
[not found] <s2832159.056@emea1-mh.id2.novell.com>
2005-05-12 11:45 ` Andi Kleen
2005-05-12 12:48 Jan Beulich
[not found] <s2835ea9.090@emea1-mh.id2.novell.com>
2005-05-12 12:51 ` Andi Kleen
2005-05-12 12:52 Jan Beulich
[not found] <s2835f7d.038@emea1-mh.id2.novell.com>
2005-05-12 12:52 ` Andi Kleen
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=1115892008.918.7.camel@localhost.localdomain \
--to=alexn@telia.com \
--cc=JBeulich@novell.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).