mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: richardj_moore@uk.ibm.com, Paul Jakma <paulj@itg.ie>,
	Michael Rothwell <rothwell@holly-springs.nc.us>,
	Christoph Rohland <cr@sap.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)
Date: Fri, 10 Nov 2000 17:54:05 +0100	[thread overview]
Message-ID: <20001110175405.A14799@gruyere.muc.suse.de> (raw)
In-Reply-To: <80256993.0047077C.00@d06mta06.portsmouth.uk.ibm.com> <200011101624.LAA22004@tsx-prime.MIT.EDU>
In-Reply-To: <200011101624.LAA22004@tsx-prime.MIT.EDU>; from tytso@MIT.EDU on Fri, Nov 10, 2000 at 11:24:28AM -0500

On Fri, Nov 10, 2000 at 11:24:28AM -0500, Theodore Y. Ts'o wrote:
> Right.  So what you're saying is that GKHI is adding complexity to the
> kernel to make it easier for peopel to put in non-standard patches which
> exposes non-standard interfaces which will lead to kernels not supported
> by the Linux Kernel Development Community.  Right?

My understanding is that GKHI does not change the kernel at all, except
for the three hooks needed for dprobes. All GKHI hooks are implemented 
as dynamic probes, which are just like debugger breakpoints. 
A dynamic probes breakpoint does not require any source
changes, but you have to check the assembly to find the right point for
them (at least in the current version, I don't know if IBM is planning 
to support source level dprobes using the debugging information) 

IMHO GKHI does not make mainteance of additional modules any easier, because
you always have to recheck the assembly if the dynamic probe still fits
(which may in some cases even be more work than reporting source patches,
it is also harder when you want to cover multiple architectures) 

It will just help some people who have a unrational aversion against kernel
recompiles and believe in vendor blessed binaries.


-Andi

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

  parent reply	other threads:[~2000-11-10 16:54 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 11:41 richardj_moore
2000-11-10 16:24 ` Theodore Y. Ts'o
2000-11-10 16:37   ` Christoph Rohland
2000-11-10 18:36     ` Matt D. Robinson
2000-11-11  0:12       ` Theodore Y. Ts'o
2000-11-11  3:29         ` Matt D. Robinson
2000-11-11  4:57           ` Keith Owens
2000-11-11 17:58         ` tytso
2000-11-13 10:30           ` Daniel Phillips
2000-11-11 21:48         ` Lars Marowsky-Bree
2000-11-11 22:12           ` Michael Rothwell
2000-11-10 16:54   ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15 15:24 richardj_moore
2000-11-15 18:20 ` Matt D. Robinson
2000-11-15 15:22 richardj_moore
2000-11-14  1:34 richardj_moore
2000-11-13  5:52 richardj_moore
2000-11-12 23:27 richardj_moore
2000-11-13 10:38 ` Andi Kleen
2000-11-14  3:17   ` Andrea Arcangeli
2000-11-10 19:31 richardj_moore
2000-11-10 18:42 richardj_moore
2000-11-10 16:08 richardj_moore
2000-11-10 11:17 richardj_moore
2000-11-10 10:57 richardj_moore
2000-11-10 10:57 richardj_moore
2000-11-10 10:57 richardj_moore
2000-11-10 13:45 ` Alexander Viro
2000-11-10 13:51   ` Michael Rothwell
2000-11-10 14:00     ` Alexander Viro
2000-11-10 14:37   ` David Lang
2000-11-09 14:02 Jesse Pollard
2000-11-09  7:43 richardj_moore
2000-11-09 11:24 ` Christoph Rohland
2000-11-09 12:25   ` Michael Rothwell
2000-11-09 12:30     ` Lars Marowsky-Bree
2000-11-09 12:46       ` Michael Rothwell
2000-11-09 13:35         ` Alan Cox
2000-11-09 13:43           ` Michael Rothwell
2000-11-09 14:23             ` Theodore Y. Ts'o
2000-11-09 12:50     ` Paul Jakma
2000-11-09 12:53       ` Michael Rothwell
2000-11-09 13:39         ` Paul Jakma
2000-11-09 14:06           ` Marco Colombo
2000-11-09 14:14           ` Theodore Y. Ts'o
2000-11-09 14:26             ` Alan Cox
2000-11-09 14:37               ` Jeff Garzik
2000-11-09 20:24               ` Theodore Y. Ts'o
2000-11-09 13:31     ` Alan Cox
2000-11-08 20:31 richardj_moore
2000-11-08 21:35 ` Michael Rothwell
2000-11-09  7:44   ` Christoph Rohland
2000-11-09  7:53     ` Larry McVoy
2000-11-09  8:08       ` Andre Hedrick
2000-11-09  8:43       ` Christoph Rohland
2000-11-09 12:20         ` Michael Rothwell
2000-11-09 12:31           ` Lars Marowsky-Bree
2000-11-09 12:40           ` Alexander Viro
2000-11-09 13:02             ` Michael Rothwell
2000-11-09 13:30               ` Alexander Viro
2000-11-09 13:39                 ` Michael Rothwell
2000-11-09 17:19                 ` Mike Coleman
2000-11-09 17:27                   ` Alexander Viro
2000-11-10 11:42                     ` Martin Dalecki
2000-11-09 13:40               ` Marco Colombo
2000-11-10  8:44           ` Christoph Rohland
2000-11-09 12:50       ` Tigran Aivazian
2000-11-09 16:03       ` Ingo Molnar
2000-11-10  8:42         ` Christoph Rohland
2000-11-09 14:28   ` Theodore Y. Ts'o
2000-11-10 15:07   ` Matti Aarnio
2000-11-10 15:24     ` Michael Rothwell

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=20001110175405.A14799@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulj@itg.ie \
    --cc=richardj_moore@uk.ibm.com \
    --cc=rothwell@holly-springs.nc.us \
    --cc=tytso@MIT.EDU \
    /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

all inboxes | Powered by JetHome®