From: Keith Owens <kaos@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-arch@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: Replace i386/x86_64 nmi_callback RCU code with atomic notifier chain
Date: Thu, 18 May 2006 22:10:53 +1000 [thread overview]
Message-ID: <5851.1147954253@ocs3> (raw)
In-Reply-To: Your message of "Thu, 18 May 2006 12:15:27 +0200." <200605181215.28289.ak@suse.de>
Andi Kleen (on Thu, 18 May 2006 12:15:27 +0200) wrote:
>On Thursday 18 May 2006 08:17, Keith Owens wrote:
>> i386 and x86_64 have low level RCU code to handle dynamic registration
>> and unregistration of the NMI callback function. With the rewrite of
>> the general notifier chains, we can remove the low level RCU hacking
>> from these NMI handlers and replace them with an atomic notifier chain,
>> making the code much simpler. set_nmi_callback() gets replaced by yet
>> another notify chain. The only affected code outside the main NMI
>> handler is crash and oprofile. Any objections?
>
>It has been already done. Check -mm or firstfloor tree.
Where is this 'firstfloor' tree? The only google references are to
http://www.firstfloor.org/~andi which gives "You don't have permission
to access /~andi/ on this server". Google also lists ~andi/35,
~andi/softnet/, ~andi/numa.html, ~andi/mbind.html, but they all get 404
errors.
next prev parent reply other threads:[~2006-05-18 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 6:17 Replace i386/x86_64 nmi_callback RCU code with atomic notifier chain Keith Owens
2006-05-18 10:15 ` Andi Kleen
2006-05-18 12:10 ` Keith Owens [this message]
2006-05-18 12:23 ` 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=5851.1147954253@ocs3 \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=zwane@linuxpower.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.