All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [agx@sigxcpu.org: [PATCH]: swsusp on linux-2.6.9-rc3]
Date: Tue, 05 Oct 2004 09:18:33 +1000	[thread overview]
Message-ID: <1096931912.23141.107.camel@gaston> (raw)
In-Reply-To: <20041004151259.GC5637@bogon.ms20.nix>

On Tue, 2004-10-05 at 01:12, Guido Guenther wrote:
> On Tue, Oct 05, 2004 at 12:14:11AM +1000, Benjamin Herrenschmidt wrote:
> > A hack I wrote a while ago that allows to run the MacOS "ndrv" video
> > driver within a userland "shell" in linux. It works with old-style
> > 'ndrv's that ATI still uses but not with the newer nVidia 'fully native'
> > drivers and it can spy all IOs done by the driver

> Nice. Can you think of a way to monitor calls of MacOS X into the OF?

It has nothing to do with OF. We need to spy the IO accesses. Roughly
the same mecanism I use on linux but moved to kernel-land in OS X
would be possible but complicated: basically feeding the nvdia driver
with a non-mapped IO area and catching all faults, emulating the actual
accesses and logging them. But my knowledge of OS X low levels isn't
that good and I don't have time to work on that.

Ben.

  parent reply	other threads:[~2004-10-04 23:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 11:21 [agx@sigxcpu.org: [PATCH]: swsusp on linux-2.6.9-rc3] Guido Guenther
2004-10-04 13:39 ` Benjamin Herrenschmidt
2004-10-04 13:51   ` Guido Guenther
2004-10-04 14:14     ` Benjamin Herrenschmidt
2004-10-04 15:12       ` Guido Guenther
2004-10-04 19:57         ` Segher Boessenkool
2004-10-05  6:57           ` Guido Guenther
2004-10-05  7:24             ` Benjamin Herrenschmidt
2004-10-04 23:18         ` Benjamin Herrenschmidt [this message]
2004-10-05  6:58           ` Guido Guenther
2004-10-05  7:26             ` Benjamin Herrenschmidt
2004-10-04 22:07   ` John Steele Scott
2004-10-04 23:27     ` Benjamin Herrenschmidt
2004-10-05  8:12       ` John Steele Scott

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=1096931912.23141.107.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=agx@sigxcpu.org \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.