Re: Prioritizing SBP2 daemon

Subject: Re: Prioritizing SBP2 daemon
From: Mike Smith <email@hidden>
Date: Sun, 25 Sep 2005 12:48:19 -0700

On Sep 25, 2005, at 4:52 AM, <email@hidden> <email@hidden> wrote:

I have to go back to my original question- what exactly are you
trying to do? If your trying to prevent IOKit from doing something,
you really need to be in the kernel. Based on what you've posted so
far the technique your trying to use isn't going to work. The system
simply isn't designed to work that way.
--

I want to track the activities going on SBP2 disks right from beginning, when the disk comes up.

Any way to do it from Application or kernel level?

What "activities" are you most interested in? Do you want to see disk I/O transactions,

or FireWire transactions?

If you want to see disk I/O, you could match to IOMedia objects and check the device

tree upwards to see whether they are the root object exported by an SBP2 driver. You

just need to "win" the bidding for the device in this case.

If you want to watch firewire transactions, then you need to match to every firewire

SBP2 device more aggressively than the driver, and then publish another identical

interface.

In both cases, if the SBP2 device is the boot disk, your filter will be running a *long*

time before you can run any userland utility.

= Mike

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>RE: Prioritizing SBP2 daemon (From: <email@hidden>)

Prev by Date: Re: Corefoundation && Linux
Next by Date: Re: Corefoundation && Linux
Previous by thread: RE: Prioritizing SBP2 daemon
Next by thread: RE: Prioritizing SBP2 daemon
Index(es):
- Date
- Thread