LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Christoph Hellwig" <hch@infradead.org>
Cc: "Pekka Paalanen" <pq@iki.fi>,
	linux-kernel@vger.kernel.org, jbeulich@novell.com,
	proski@gnu.org
Subject: Re: Replacement for page fault notifiers?
Date: Wed, 9 Jan 2008 08:13:05 +1000	[thread overview]
Message-ID: <21d7e9970801081413n307ab07aq462a9fff014143ae@mail.gmail.com> (raw)
In-Reply-To: <20080108203235.GA772@infradead.org>

On Jan 9, 2008 6:32 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Tue, Jan 08, 2008 at 09:06:38PM +0200, Pekka Paalanen wrote:
> > - Is there anything coming to replace register_page_fault_notifier()?
>
> no.
>
> > - Has someone found another way to accomplish the same without patching
> > the kernel?
>
> no.
>
> > - Should I start writing a patch to bring back the notifiers, based on
> > the commit that removed them?
>
> no.
>
> > People started to complain to me that mmio-trace does not compile for
> > 2.6.24. At least the Nouveau project is a regular user of mmio-trace
> > for reverse-engineering, and the tool should be easy to use. Therefore
> > I would prefer not to force casual contributors to patch their kernels
> > as it might be too much for some. I am hoping that 2.6.25, if not
> > 2.6.24, would contain a mechanism to accomplish what I need.
>
> Please make mmio tracing generic enough so it works for every device and
> submit it for inclusion as a config option.
>

Christoph,

it is generic code, it works by patching the module you load and is in
no way nvidia specific, I think we should revert your chance
as the notifiers have a valid user and one it has been planned to upstream..

Dave.

  reply	other threads:[~2008-01-08 22:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 19:06 Pekka Paalanen
2008-01-08 20:32 ` Christoph Hellwig
2008-01-08 22:13   ` Dave Airlie [this message]
2008-01-09  0:26     ` Benjamin Herrenschmidt
2008-01-09 18:18       ` Pavel Roskin
2008-01-09 18:21         ` Christoph Hellwig
2008-01-09 19:58           ` Benjamin Herrenschmidt
2008-01-09 20:22             ` Christoph Hellwig
2008-01-10  0:42               ` Arjan van de Ven
2008-01-10  0:47                 ` Andi Kleen
2008-01-10  0:55                   ` Arjan van de Ven
2008-01-10  0:58                     ` Benjamin Herrenschmidt
2008-01-10  1:01                     ` Andi Kleen
2008-01-10  0:56                 ` Benjamin Herrenschmidt
2008-01-10  2:03                 ` Matt Mackall
2008-01-10  2:21                   ` Pavel Roskin
2008-01-10  2:30                     ` Matt Mackall
2008-01-10 18:44               ` Pekka Paalanen
2008-01-09 20:24             ` Pavel Roskin
2008-01-09 20:26               ` Christoph Hellwig
2008-01-09 20:41                 ` Pavel Roskin
2008-01-09 20:44                 ` Valdis.Kletnieks

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=21d7e9970801081413n307ab07aq462a9fff014143ae@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=hch@infradead.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pq@iki.fi \
    --cc=proski@gnu.org \
    --subject='Re: Replacement for page fault notifiers?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).