public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Andi Kleen <ak@muc.de>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: [PATCH] NMI/CMOS RTC race fix for x86-64
Date: Mon, 07 Mar 2005 14:50:39 -0600	[thread overview]
Message-ID: <422CBE9F.1090906@acm.org> (raw)
In-Reply-To: <m1ll8zmfzc.fsf@muc.de>

Andi Kleen wrote:

>Corey Minyard <minyard@acm.org> writes:
>
>  
>
>>This patch fixes a race between the CMOS clock setting and the NMI
>>code.  The NMI code indiscriminatly sets index registers and values
>>in the same place the CMOS clock is set.  If you are setting the
>>CMOS clock and an NMI occurs, Bad values could be written to or
>>read from the CMOS RAM, or the NMI operation might not occur
>>correctly.
>>
>>    
>>
>
>In general you should send all x86-64 patches to me. I would have
>eventually merged it from i386 anyways if it was good.
>
>But in this case it isnt. Instead of all this complexity 
>just remove the NMI reassert code from the NMI handler.
>It is oudated and mostly useless on modern systems anyways.
>  
>
"mostly useless" and "completely useless" are two different things.

If you run with nmi_watchdog=0, then this code actually does something
useful, which is what I assume you mean by "mostly useless".  I'm all for
removing useless code, so I'd be fine with just removing the code.  But
something really needs to be done.

Do you want me to submit a patch that simply removes this?

-Corey

>Since the NMI watchdog runs regularly even if an NMI is missed
>it will be eventually handled. And even when it doesn't run
>it doesn't matter much because NMI does nothing essential.
>
>-Andi
>  
>


  reply	other threads:[~2005-03-07 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 18:48 [PATCH] NMI/CMOS RTC race fix for x86-64 Corey Minyard
2005-03-07 19:08 ` Andi Kleen
2005-03-07 20:50   ` Corey Minyard [this message]
2005-03-07 21:53     ` Andi Kleen
2005-03-07 23:33       ` Corey Minyard

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=422CBE9F.1090906@acm.org \
    --to=minyard@acm.org \
    --cc=ak@muc.de \
    --cc=akpm@osdl.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