public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] kill pointless perfmon abstractions
Date: Wed, 08 Oct 2003 19:37:56 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106564201225917@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106562954910433@msgid-missing>

On Wed, Oct 08, 2003 at 11:51:14AM -0700, Stephane Eranian wrote:

> Well, it is because you only know part of the story ;-< These abstractions
> are here to mask differences between the various kernels out there.

I'd suspected that it might be an issue with 2.4 kernels so I checked
against 2.4.22 - none of the removed macros even exist or are relevant.
I understand that it can be often be useful to allow easy merges with
2.4, but it doesn't seem to apply in this case.

> RH EL, and Suse SLES.

I must be missing something here. Why are vendor kernels at all relevant
to Linus's tree ? Vendor kernels are surely a vendor problem.

Even if they were: there's a much better way to do this. For example,
instead of pfm_irq_handler_t, simply use irqreturn_t in the source (so
it looks like 2.6 code). Then vendors can do :

#include "vendor.h"

or whatever that has
#define irqreturn_t void, #define IRQ_HANDLED /* nothing */, etc.

I believe this is general approach preferred by, for example, the net
drivers. It means that the Linus kernel tree looks sane, whilst not
sacrificing any merging ability with older trees.

Another obvious candidate here is pfm_do_munmap()

regards,
john

-- 
Khendon's Law:
If the same point is made twice by the same person, the thread is over.

      parent reply	other threads:[~2003-10-08 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 16:05 [PATCH] kill pointless perfmon abstractions John Levon
2003-10-08 18:51 ` Stephane Eranian
2003-10-08 19:37 ` John Levon [this message]

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=marc-linux-ia64-106564201225917@msgid-missing \
    --to=levon@movementarian.org \
    --cc=linux-ia64@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