mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Need help with register_page_fault_notifier() replacement in 2.6.24
Date: Sun, 18 Nov 2007 14:17:41 -0800	[thread overview]
Message-ID: <20071118141741.28738bee@laptopd505.fenrus.org> (raw)
In-Reply-To: <1195407616.26789.15.camel@dv>

On Sun, 18 Nov 2007 12:40:16 -0500
Pavel Roskin <proski@gnu.org> wrote:

> Hello!
> 
> I'm trying to update a special tracing version of madwifi (driver for
> Atheros wireless cards) for Linux 2.6.24.  This version was created to
> help reverse engineering the non-free part of the driver (also known
> as HAL, hardware abstraction layer).
> 
> The problem is that functions register_page_fault_notifier() and
> unregister_page_fault_notifier() are gone in the current kernel git
> repository.
> 
> They are needed to intercept access to the card by causing page fault
> and intercepting it.
> 
> Those functions were removed on i386 platform because kprobes now
> registers the flat handler directly.  The log says that other callers
> are supposed to use kprobes now.
> 
> But what would be the right way to do it?  I can intercept
> do_page_fault() with kprobes, but that looks unsafe, since
> do_page_fault() is used by kprobes internally.
> 
> Or maybe I should install a fault handler with register_kprobe()?  The
> problem is, it is only called for faults in kp->pre_handler and
> kp->post_handler and for single-stepping.  I don't want to single-step
> anything, and moving all driver functionality in kp->pre_handler would
> be strange.
> 
> Perhaps I'm missing something obvious.  Any help will be appreciated.
> 

if it's just for a custom case (as it sounds like).. a simple small
change to the pagefault handler sounds like the easiest thing to do...
(eg just a direct function call to what would have been your notifier)

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2007-11-18 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 17:40 Pavel Roskin
2007-11-18 22:17 ` Arjan van de Ven [this message]
2007-11-19  5:29   ` Pavel Roskin
2007-11-19  5:42     ` Arjan van de Ven

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=20071118141741.28738bee@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.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®