From: Dave Peterson <dsp@llnl.gov>
To: Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] NMI handler message passing / work deferral API
Date: Mon, 21 Mar 2005 11:03:56 -0800
User-Agent: KMail/1.5.3
Cc: oprofile-list@lists.sourceforge.net, bluesmoke-devel@lists.sourceforge.net,
       linux-kernel@vger.kernel.org, dave_peterson@pobox.com
References: <200503202056.02429.dave_peterson@pobox.com> <m1eke93ul3.fsf@muc.de>
In-Reply-To: <m1eke93ul3.fsf@muc.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503211103.56930.dsp@llnl.gov>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1183
Lines: 29

On Monday 21 March 2005 07:08 am, Andi Kleen wrote:
> Dave Peterson <dave_peterson@pobox.com> writes:
> > Below is an experimental 2.6.11.5 kernel patch that implements the
> > following:
> >
> >      - A generic mechanism for safely passing information from NMI
> > handlers to code that executes outside NMI context.
>
> See the machine check queueing implementation in
> arch/x86_64/kernel/mce.c. It does exactly that already.
>
> Several other architectures already have similar mechanisms.
>
> -Andi

Yes exactly.  That's one reason why I posted the patch.  Different
sybsystems that need this type of functionality shouldn't have to
individually reinvent the wheel.  With a single implementation, code
is more compact and easier to understand and maintain.  I would argue
that code maintenance is of particular concern to code such as NMI
and machine check handlers because bugs in this type of code can be
hard to track down.

Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/