mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, jbeulich@novell.com
Subject: Re: [PATCH] re-export genapic on i386
Date: 09 Sep 2005 05:53:04 +0200	[thread overview]
Message-ID: <p73u0gu3nj3.fsf@verdi.suse.de> (raw)
In-Reply-To: <20050908155011.GA12359@infradead.org>

Christoph Hellwig <hch@infradead.org> writes:

> On Thu, Sep 08, 2005 at 05:47:34PM +0200, Jan Beulich wrote:
> > (Note: Patch also attached because the inline version is certain to get
> > line wrapped.)
> > 
> > A change not too long ago made i386's genapic symbol no longer be
> > exported,
> > and thus certain low-level functions no longer be usable. Since
> > close-to-
> > the-hardware code may still be modular, this rectifies the situation.
> 
> Again, what code would use it, why and why can't it use a proper accessor.
> And a shitty thousands of lines out ot tree debugger ported from Novell's
> legacy OS is not the answer, btw.

Why not?  Most debuggers will always be out of tree for political
reasons, and because of that the normal "every hook must 
have an in tree user" rule cannot be strictly applied to them.

It's also not reasonable to ask these people to always 
carry big patchkits around - after all they just want
to debug core kernel code, and it is very ugly to apply
a big patchkit just for that.

So as long as the hooks for external modular debuggers 
are reasonable and _GPL I think they should be merged.

-Andi

  reply	other threads:[~2005-09-09  3:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 15:47 Jan Beulich
2005-09-08 15:50 ` Christoph Hellwig
2005-09-09  3:53   ` Andi Kleen [this message]
2005-09-08 17:09 ` Zwane Mwaikambo

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=p73u0gu3nj3.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=hch@infradead.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®