public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Dave Peterson <dsp@llnl.gov>
Cc: oprofile-list@lists.sourceforge.net,
	bluesmoke-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, dave_peterson@pobox.com
Subject: Re: [PATCH] NMI handler message passing / work deferral API
Date: 21 Mar 2005 20:07:41 +0100
Date: Mon, 21 Mar 2005 20:07:41 +0100	[thread overview]
Message-ID: <20050321190741.GA98750@muc.de> (raw)
In-Reply-To: <200503211103.56930.dsp@llnl.gov>

On Mon, Mar 21, 2005 at 11:03:56AM -0800, Dave Peterson wrote:
> 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

More compact? Sorry, but even all existing implementations together
are still far less code than your really complicated subsystem which
seems quite overengineered for this simple task for me.

Also lockless programming is tricky and I would feel quite uneasy
about auditing so much code.

> 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.

Yeah, that is why we use simple, not complex, code in there.

-Andi

  reply	other threads:[~2005-03-21 19:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21  4:56 [PATCH] NMI handler message passing / work deferral API Dave Peterson
2005-03-21  7:35 ` Dave Peterson
2005-03-21 15:08 ` Andi Kleen
2005-03-21 19:03   ` Dave Peterson
2005-03-21 19:07     ` Andi Kleen [this message]
2005-03-21 19:51       ` Dave Peterson

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=20050321190741.GA98750@muc.de \
    --to=ak@muc.de \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=dave_peterson@pobox.com \
    --cc=dsp@llnl.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    /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