There might be a better way but try something like this:
> ::devbindings -s bnx
DEVINFO MAJ REFCNT NODENAME NODESTATE
INST CIRCULAR BINDNAME STATE
THREAD FLAGS
ffffffff80265658 9 1 pci1028,2...@0 DS_READY
0 0 pci14e4,1639
<S_EVADD,S_NEED_RESET>
0 <>
ffffffff80265440 9 0 pci1028,2...@0,1 DS_INITIA
1 0 pci14e4,1639 <S_EVADD>
0 <>
ffffffff80265228 9 0 pci1028,2...@0 DS_INITIA
2 0 pci14e4,1639 <S_EVADD>
0 <>
ffffffff80265010 9 0 pci1028,2...@0,1 DS_INITIA
3 0 pci14e4,1639 <S_EVADD>
0 <>
Then get the driver data pointer from the devinfo:
> ffffffff80265658::print struct dev_info devi_driver_data
devi_driver_data = 0xffffffff93ce6000
For a majority of drivers that pointer will be what your looking for
yet you'll need to know some details of the internal driver:
> 0xffffffff93ce6000::print bnx`um_device_t
...snip...
Hope that helps,
- e
On Sun, Aug 8, 2010 at 8:27 PM, Shank <ctidb...@gmail.com> wrote:
> Hi,
> In mdb we can dump kernel data structures from memory for example
> 079ceb0::print -t 'struct scsi_pkt'
> similarly how can i dump a driver's internal data structure? one that is part
> of the driver code.
>
> Thanks,
> -Shank
> --
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
