From: Corey Minyard <cminyard@mvista.com>
To: Zwane Mwaikambo <zwane@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NMI handling rework
Date: Thu, 14 Nov 2002 22:50:21 -0600 [thread overview]
Message-ID: <3DD47D0D.7080801@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211142311160.2750-100000@montezuma.mastecende.com
Zwane Mwaikambo wrote:
>On Thu, 14 Nov 2002, Corey Minyard wrote:
>
>
>
>>I haven't received much feedback on getting this included into the
>>kernel. I think it's a good idea since the nmi handler was starting to
>>get messy, especially when you add kdb, NMI watchdogs, etc.
>>
>>
>
>What protects the handler list from traversal in NMI context whilst we
>update the list?
>
> Zwane
>
>
RCU does. Basically, the code pulls it from the list atomically wrt to
the NMI handler, and uses RCU to schedule the actual free of the data to
be done after all CPUs have gone to idle or returned from interrupts.
It's subtle, you have to think about it a little. But it does work.
-Corey
next prev parent reply other threads:[~2002-11-15 4:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 15:26 NMI handling rework Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-11-15 3:45 ` Corey Minyard
2002-11-15 4:12 ` Zwane Mwaikambo
2002-11-15 4:50 ` Corey Minyard [this message]
2002-11-15 5:12 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 15:00 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-11-08 20:30 ` Zwane Mwaikambo
2002-11-07 6:44 Corey Minyard
2002-11-07 6:20 ` Zwane Mwaikambo
2002-11-07 16:51 ` Corey Minyard
2002-11-07 15:59 ` Maciej W. Rozycki
2002-11-07 16:38 ` Zwane Mwaikambo
2002-11-07 16:59 ` Richard B. Johnson
2002-11-07 19:58 ` Corey Minyard
2002-11-08 15:34 ` Alan Cox
2002-11-07 17:05 ` John Levon
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=3DD47D0D.7080801@mvista.com \
--to=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@holomorphy.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